Test Release v3.2.0

[viresanimi]

CoreRPG: I've noticed, that after the last update, it seems like the placement of story elements in various categories has been reset and keeps resetting. So if you resort all your stuff into the right category, it will all just be in the "all" category and nowhere else the next time you load it up.

Vires Animi

[Moon Wizard]

Are you talking about module data (i.e. data loaded from modules that started in a category), or campaign data (i.e. records created specific to a campaign, and placed into a category)?

I'll play around to see if I can recreate. Any specific steps to recreate would be helpful.

EDIT: Nevermind, I found the issue.

Regards,
JPG

[Moon Wizard]

Updates

• Category information being forgotten when loading. Fixed.
• [CoreRPG+] Scaling improved for image record Resize to Original Size menu option when image smaller than minimum window width or height.

Regards,
JPG

[Mortar]

[Savage Worlds] If I close all the modules that are currently open when I load in, other modules will wont display when opened until I reload.

Attachment 14360

Edit 1 Deleted the campaign and cleared the cache, started a new campaign and now it appears I can't open any modules now at all.

Attachment 14361

Edit 2 Same issue Castles and Crusades

[Moon Wizard]

Updates

• Lists not being updated when module data loaded during session. Fixed.

JPG

[spite]

Tried to update to test version from live version, all modules and rulesets purchased were removed.
Set back to live version and it all redownloaded again. Repeatable and recreatable every time.
Also of note, the version didnt change from 3.1.7 when I did it, but the updater does say 3.2.0

[dulux-oz]

Tried to update to test version from live version, all modules and rulesets purchased were removed.
Set back to live version and it all redownloaded again. Repeatable and recreatable every time.
Also of note, the version didnt change from 3.1.7 when I did it, but the updater does say 3.2.0

I've noticed this as well

[spite]

I've noticed this as well

Whew it's not just me then

[Moon Wizard]

This seems to be a challenge with switching update modes back and forth. When downgrading then upgrading again, the new manifest files only used by the new updater do not get updated by the old updater. Thus, the new updater thinks that the files don't need to be updated when going back to v3.2.0. For now, you'll need to delete the vault directory when upgrading back to v3.2.0 again.

Regards,
JPG

[spite]

Cool thanks for that Moon Wizard, that's worked perfectly.