Refresh Counters 'broken'

OK, all force pools use the same png image. This has not happened before beta 7. Basically during the refresh counters all pieces within their various force pools (8 in total) got transferred to the first force pool (the Chinese). See attached pic. Now I’ve got to separate them all and reload them into their correct force pools. But, I would be extremely loathe to do anymore refresh counters.

May we have the module? What steps do we need to take reproduce this?

Yes, definitely, just jump back to the backup you made before using a beta version and let us know where to find the module.

Thanks.

Worked out it is WiF and managed to reproduce the issue. Looking into it.

1 Like

So, should I try this version?
https://vassalengine.org/builds/build/119345448
Or wait for further development?

Await further development - Brent hasn’t posted a PR to fix your problem yet. (But I know he has dug in and diagnosed the core issue)

1 Like

At vassalengine.org/builds, please try the relevant-to-your-OS one of these builds (c9c252c) and let us know if it works correctly for your module now.

|VASSAL-3.6.0-SNAPSHOT-c9c252c-windows-x86_64.exe|2021-11-28 16:07:49|
|VASSAL-3.6.0-SNAPSHOT-c9c252c-windows-x86_32.exe|2021-11-28 16:07:49|
|VASSAL-3.6.0-SNAPSHOT-c9c252c-windows-aarch64.exe|2021-11-28 16:07:49|
|VASSAL-3.6.0-SNAPSHOT-c9c252c-other.zip|2021-11-28 16:07:49|
|VASSAL-3.6.0-SNAPSHOT-c9c252c-macos-x86_64.dmg|2021-11-28 16:07:49|
|VASSAL-3.6.0-SNAPSHOT-c9c252c-macos-aarch64.dmg|2021-11-28 16:07:49|
|VASSAL-3.6.0-SNAPSHOT-c9c252c-linux.tar.bz2|2021-11-28 16:07:49|
|VASSAL-3.6.0-SNAPSHOT-c9c252c.sha256|2021-11-28 16:07:49|

@palad0n Checking in, hoping you’ll have a chance to verify the fix works?

Love to. Being away for a few days. Do subsequent iterations count or just the 1 you’ve linked to.

Any recent build with “master” in the name would include the fix.

However in this case Joel has already started the release process for 3.6.0, so if you head to Releases · vassalengine/vassal · GitHub you can just try the 3.6.0 build. I think Brent already tested with whatever version of your module he had, but it would be great if you gave it a check.

Brian

Have not detected any issues with 3.6.0. All good.

1 Like