• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Realm Works Bug Fix Beta Release (Build 255)

S

SteveT

Administrator
Staff member
We have a new bug fix release of Realm Works available (build 255) to fix the import validation error people were encountering with export files exported with build 254 (specifically, "Encountered validation error for the import XML: The 'format_version' attribute is invalid - The value '4' is invalid").

We are releasing this as a beta release initially, so you may continue using build 254 if you prefer. However if you encountered this issue, please give the new build a try and verify that it resolves the issue.

Even if you didn't previously encounter the issue, we encourage you to install the new build as we'd like as many people as possible to do so in order to acquire more reputation for our new code signing certificate which I explain below.

Release Notes:

  • Fixed a specific validation error which prevented export files exported with build 254 from successfully importing.

PLEASE NOTE: We recently renewed our digital code signing certificate, and since this is the first public release to use the new certificate, it has not yet acquired enough reputation with anti-virus software such as Windows Defender or Avast to avoid being flagged as potentially harmful to your computer, even though it is perfectly safe. We need more people to install the software in order to acquire reputation for the certificate :) So from Windows Defender you may receive a message along the lines of "Windows Defender SmartScreen prevented an unrecognized app from starting". If you click "Show Info" or "Show More" it should reveal a button labeled "Run anyway" that you can click to bypass the warning. Similarly, other anti-virus software might initially sandbox the installer or the new version of Realm Works itself. However, this is nothing to worry about. You can either let the sandboxing run its course or manually abort it and you should be able to install/use the new version of Realm Works afterwards.

NEW BETA BUILD: The new build can be downloaded from this link: https://www.wolflair.com/download/rw/RealmWorks_255_install.exe

Note that in the unlikely event that you run into any new problems with the new build, you can safely revert to build 254. To do so just close Realm Works and run the installer for build 254 available here: https://www.wolflair.com/download/rw/RealmWorks_254_install.exe

If you choose to revert to build 254 after installing 255, you will receive a warning message about the older version possibly not working with the newer database. However you can ignore this warning in this particular case as there are no changes to the database between these two versions, so it is safe to revert.
 
Last edited:
Thank you very much for releasing a fix. I am very happy that we are not forgotten and some soul in the lair is working on RW even if on maintenance releases. Let’s hope the spring bring more to it. :)
 
Did a Custom/Partial export, then an import to another realm and hit an exception.

Went through the process of reporting the issue via the UI.
 
Not sure this is related to the new version -- doing more testing.

There used to be a way to drop the exception to a text file, but I don't seem to see that anymore. Am I missing something?

Alternatively, is there anyway to get more detailed error info? For example, if a topic is triggering the error, it would be very helpful to know which one it was.

I know it's doubtful to get new debugging instrumentation implemented, but I'm kind of pipe dreaming that a hidden switch would already be present...

Later.
 
Resolved... there were some odd artifacts in the realm I was trying to import into. Starting from a clean realm worked fine.

Take care

-=Janrith
 
Any word on the update? It's 6 months since this was posted. I still can't export my realms and I don't want to download the beta due to some people losing their realms. I don't have months of work to lose I have years.
 
Sevrick said:
Any word on the update? It's 6 months since this was posted. I still can't export my realms and I don't want to download the beta due to some people losing their realms. I don't have months of work to lose I have years.
Click to expand...

You can manually backup the database file, and then try version 255. If you have to revert back to 253 you should be able to also revert the database file.
 
Realms are not lost (afaik) but import functionality is not working on 255.
I have no way of reverting to 253 on my own I suppose. Maybe it works with server access which I still have to check.
 
Acenoid said:
Realms are not lost (afaik) but import functionality is not working on 255.
I have no way of reverting to 253 on my own I suppose. Maybe it works with server access which I still have to check.
Click to expand...

I was able to:

  1. uninstall
  2. wipe the %AppData% Realm Works folder (%AppData%\LWD Technology, Inc\Realm Works)
  3. then re-install 253
  4. sync all down from the cloud

Then was able to create new export files from my source realms and import to my target realms.

I think you should be good to revert.
 
Sevrick said:
Any word on the update? It's 6 months since this was posted. I still can't export my realms and I don't want to download the beta due to some people losing their realms. I don't have months of work to lose I have years.
Click to expand...

I opened a case detailing the issues on January 10th. I asked for an update later and received an update on February 12.

10 days ago, June 16th, I asked for another update and have not received a response.
 
Raise a ticket in the HLO forums. At least that way they might read it. I'm willing to bet it's been 6 months since a developer popped there head in here with any intent of helping us.
 
I recently put in a support ticket to ask about fixing the import/export bug and about the broken HL integration.

I was informed that because of the current high demand on LW resources from developing HLO and keeping up with the release schedule of PF2 material they don't have the manpower right now to track down and fix these bugs in RW.

And daplunk is correct - I've brought up RW and HLC issues in the HLO thread and gotten some response and information. Part of that information was that Rob is really only monitoring the HLO forums. And it's been a minute since he chimed in there as well.
 
You must log in or register to reply here.
Back
Top