• 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

Major Realm Works Update Arrives!

Sorry for not being clear. You will need to revert to the backup WITH THE UPCOMING BUG FIX RELEASE. The current version corrupts the statblocks. Until we get the fix out, you can revert to the backup all you want, but you'll continue to get the same - wrong - results.

We do NOT want to release a bug fix update that fails to fix ALL of the problems with data conversion. Granted, there's only a few of them, but one of them is nasty. We're still trying to sort that one out.
 
Nikmal said:
The problem is I NEED to be able to use this tonight. Which is rather unfortunate. Now I will not be able to do so. :(
Click to expand...
If you don't need any additions from the last day or two, you could go back to version 200 and a backup of your database from 200. You won't be able to keep any changes, but I doubt you're worried about that at this point.

Make sure you rename your Master Database folder before uninstalling 202 so you can put it back afterwards.
 
rob said:
Depends on your timezone. If we can, we'll get some of this stuff sorted out in a release this evening. But that's not for certain, just our goal. We have to get a list of stuff sorted for the next bug fix release so that there is only one time where users have to revert to their backups (such as with the statblock corruption).
Click to expand...

We're still working on a fix to one of the other bugs that were uncovered, so we weren't able to put out the release tonight. Sorry about that. :(

We're working our tails off on this end, but we need to make sure bugs are fixed properly and tested before we release anything. Thank you for persevering. :)
 
Rob, being I did use my back up and it got corrupted... will it matter if it did or not or am I going to loose all the work I did from the last back up on the 3 of October? (10 days passed since that back-up and the one I used and it got corrupted (the backup from the major update)).

I entered about 100 topics since the 3rd of October and I would hate to loose those topics?

Thanks for working so hard to get the updates out though. I know you guys are trying. :)
 
Well my desktop (Win7 Pro) updated, launched and synced my realms successfully. :-)

My laptop is also Win7, but it's home version. I can't remember what "pro sauce" they put in the pro version, but it seems something in Win7 Home causes the app to crash.

Looking forward to the bug fix!
 
Nikmal said:
Rob, being I did use my back up and it got corrupted... will it matter if it did or not or am I going to loose all the work I did from the last back up on the 3 of October? (10 days passed since that back-up and the one I used and it got corrupted (the backup from the major update)).

I entered about 100 topics since the 3rd of October and I would hate to loose those topics?

Thanks for working so hard to get the updates out though. I know you guys are trying. :)
Click to expand...

Unless you've done something unusual - and outside of Realm Works - your backup should be fine. Here's what's happening...

1. You restore the backup
2. You load things up and Realm Works upgrades your database contents
3. The upgrade process has a bug that is incorrectly converting your statblocks

Note that the backup itself is not being modified, unless you're doing something to compromise it that is completely outside of Realm Works. That's doubtful, so your backup should still be perfectly fine. :)

When we get this bug fix release out, you'll again go through the above steps, only this time the upgrade process will correctly convert your statblocks. Then you should be good to go.
 
trechriron said:
Well my desktop (Win7 Pro) updated, launched and synced my realms successfully. :-)

My laptop is also Win7, but it's home version. I can't remember what "pro sauce" they put in the pro version, but it seems something in Win7 Home causes the app to crash.

Looking forward to the bug fix!
Click to expand...

Whatever the crash is, make sure that you submit the crash report to us! That's the only way to be sure that we're aware of that particular bug, which is the only way it will get fixed. :)
 
rob said:
Unless you've done something unusual - and outside of Realm Works - your backup should be fine. Here's what's happening...

1. You restore the backup
2. You load things up and Realm Works upgrades your database contents
3. The upgrade process has a bug that is incorrectly converting your statblocks

Note that the backup itself is not being modified, unless you're doing something to compromise it that is completely outside of Realm Works. That's doubtful, so your backup should still be perfectly fine. :)

When we get this bug fix release out, you'll again go through the above steps, only this time the upgrade process will correctly convert your statblocks. Then you should be good to go.
Click to expand...

God that would be so COOL if that was the case!! :)
 
Thanks to the Evil Real Life stuff going on with me, I haven't been able to work on my game much in last several weeks but this looks like a pretty awesome release. Thanks LWD!

I am guessing my inability to sync with friends' realms is due to their not having upgraded yet?

Keep up the good work and g'luck on the bugs.
 
rob said:
Whatever the crash is, make sure that you submit the crash report to us! That's the only way to be sure that we're aware of that particular bug, which is the only way it will get fixed. :)
Click to expand...

I absolutely do. As a professional QA person, I love your crash reporting tool. Very well done!
 
I don't think why I am crashing is caused by XP or Windows 7 since I am using Windows 10. Could be a different bug though.
 
Do we have an idea when a bug correcting version will be published? My RW crashes all the time and it is not easy to prepare my sunday session with this.

Just asking, not complaining ;)
 
No definitive answer at this time. We know they want to nail all of the bugs that have hit since 202 went live (heh, it just occurred to me that build 202 is sort of half of 404, no wonder there were problems...), and indications are that good progress is being made, so we might see an update soon, but I wouldn't bet on it (close to weekend releases are bad, but this is in the nature of an emergency, so normal release protocols might not apply).

Assume no RW this weekend, but if the fixes are available consider it a bonus.
 
We're doing everything we can to get a bug fix release out today so that those who are stuck will be operational again by the weekend.

I'd say the odds of a release today are high, but in the immortal words of Curly: "Day ain't over yet."
 
I notice the update instructions for recovering the corrupted data doesn't address users with installations on multiple machines.

The safest path, I think, would be delete (or re-name) the Master.REALM file on each secondary machine after the primary has been updated correctly, and after installing the new client on the secondary machine, then re-syncing the correct data down from the server to each secondary machine after updating the client there.

Second safest would be to be re-sync your secondary machines with the server after the primary is fixed and the server data corrected, expect to be warned of a conflict, and choose to keep the server version this time (the opposite of the choice of the primary machine).

Is there a better method, or other suggestion, we should keep in mind?
 
Last edited:
If you have multiple computers, here are the steps to follow. They are almost identical to the steps when you first applied the big upgrade.

1. Restore the backup on the computer where you FIRST did the upgrade to the earlier version. That's where the auto-created backup will reside.

2. Complete the upgrade on that computer, then sync up to the server, following the steps outlined in the release notes.

3. On all other computers, sync down the latest version from the server.

That's all there is to it. Once the first computer is restored and synced up to the server, the other computers are no different from any other time. Just grab the latest from the server, and you're good to go. :)
 
Thanks, Rob.

I am also seeing a discrepancy from what the instructions mentioned.
After restoring the backup and re-starting, there is a dialog warning that the database is out of sync with the server, and recommending syncing immediately. There is only one confirmation option, "Yes, I understand the implications".

Following that, on syncing, there is no option presented to keep either the server or the local version.. the sync just proceeds. At this point, I can't be sure whether old data was copied down from the server, or the newly converted data from the backup was synced up.

I'll add a bug report as well, but thought it best to raise it here for other users in case.
 
[Cross-posted from http://forums.wolflair.com/showthread.php?t=54087]

Well, we screwed up. I don't know how else to say it, so there it is. :(

It turns out that the restore process isn't behaving the way we thought it was. And our various pre-release tests inadvertently masked the problem, so it looked like it was all working correctly. :(

We are working on a fix right now for the restore process. Until we get this fix out, NONE of the fixes are being retained for any realms that were upgraded to build 201/202 and sync to the server. The correct fixes are being applied, but then the old (wrong) data is being pulled down from the server and overwriting those changes for a net no improvement.

Anyone who upgraded to build 203 and restored from a build 201/202 backup will need to repeat the process again with the forthcoming build 204. Sorry for the headaches on all of this. We're working through the weekend to fix this as quickly as possible.
 
You must log in or register to reply here.
Back
Top