In 3.2.7 when playing back Vassal logs, deck counters do not update and some pieces change position, out of decks and to other boards and other coordinates.
These errors do not occur during normal play, they only occur during log playback.
The only current workaround for PBEM play is to send vsav files for other players to play from along with vlog files for other players to view.
Not knowing any exact causes I can only speculate, but it seems that any cards in a deck that gets shuffled, or any cards in a deck that has a card sent to it by a ‘return to deck’ command lose their position in that deck and get sent all over a bunch of random locations, but only during log playback. To reiterate: During log creation these errors do not happen, i.e. aren’t visible to the user - the decks get shuffled normally, deck counters update normally and cards get returned normally. Only when playing back the log do things go crazy.
I’m sorry if this is considered reposting an old report, but the issue started in 3.2.6, remains in 3.2.7 and is the same problem I described here: viewtopic.php?f=3&t=6378
No such problem existed in 3.2.5
Thus spake Benkyo:
In 3.2.7 when playing back Vassal logs, deck counters do not update and
some pieces change position, out of decks and to other boards and other
coordinates.
These errors do not occur during normal play, they only occur during log
playback.
The only current workaround for PBEM play is to send vsav files for
other players to play from along with vlog files for other players to
view.
Not knowing any exact causes I can only speculate, but it seems that any
cards in a deck that gets shuffled, or any cards in a deck that has a
card sent to it by a ‘return to deck’ command lose their position in
that deck and get sent all over a bunch of random locations, but only
during log playback. To reiterate: During log creation these errors do
not happen, i.e. aren’t visible to the user - the decks get shuffled
normally, deck counters update normally and cards get returned normally.
Only when playing back the log do things go crazy.
I’m sorry if this is considered reposting an old report, but the issue
started in 3.2.6, remains in 3.2.7 and is the same problem I described
here: viewtopic.php?f=6&t=6388[1] and here: viewtopic.php?f=3&t=6378[2]
No such problem existed in 3.2.5
Are you able to reproduce the problem with the current dev build,
3.2.8-svn8784, available here?
vassalengine.sourceforge.net/builds/
–
J.
Try 3.2.8-snv8788: vassalengine.sourceforge.net/builds/
This reverts commit 8691, which should solve your problem. Unfortunately, it also reintroduces Bug 2714.