Page 1 of 1
3.1.0.1 - Can't send -ONE- TRS/AMPH out to sea
Posted: Sun Jan 05, 2020 4:50 pm
by Gar-Dog
Started a new Global War game. Seems in both Osaka and Fukuoka, I cannot send all TRS/AMPH out to sea. I can't even select them to move from either interface. Kind of kills the game for the Japanese...
Whether using the flyout interface or the Naval Review interface, once I load all 3 units in both Fukuoka and Osaka, one of the loaded ships cannot sail. After more testing, this seems to be the case even if they're unloaded. They just can't move.
Japan has taken a combined, but I backed up and the same issue appears with a naval move. FWIW, with 2 data points (Fukuoka and Osaka) it seems to consistently be the lowest-numbered TRS/AMPH (also shows up lowest in the interface screen). Tried a bunch of different loading & unloaded permutations; it seems to be the same ship that can't be selected or moved regardless of load. In Fukuoka, it's TRS 4446; in Osaka it's AMPH 4435.
Saw this with 3.0.5.0 first, tried the upgrade & did more testing - it's an issue in both.
RE: 3.1.0.1 - Can't send -ONE- TRS/AMPH out to sea
Posted: Sun Jan 05, 2020 5:00 pm
by Gar-Dog
ORIGINAL: Gar-Dog
Whether using the flyout interface or the Naval Review interface, once I load all 3 units in both Fukuoka and Osaka, one of the loaded ships cannot sail. After more testing, this seems to be the case even if they're unloaded. They just can't move.
FYI: Seems Italy doesn't have the same problem. I can select any TRS in the stack in Genoa.
RE: 3.1.0.1 - Can't send -ONE- TRS/AMPH out to sea
Posted: Mon Jan 06, 2020 2:55 pm
by Centuur
Strange in any gamesaves I've got for my own games, I don't get this bug. But in your game that bug is present.
RE: 3.1.0.1 - Can't send -ONE- TRS/AMPH out to sea
Posted: Mon Jan 06, 2020 5:37 pm
by paulderynck
When I tested, there's one TRS in Osaka, unit #4443 and one TRS in Fukuoka, unit #4447. Only after moving all the units out of Osaka, could I see Amph #4435 there. It shows in the Flyout but not if I CTRL-left click on the port (my usual method of moving one or multiple ships out of a port - which I tried first). The same applies to TRS #4446 in Fukuoka. The NRD dialog is like the Flyout wherein they can be seen but not selected.
If I use CTRL-U and filter on JP TRS and AMPH, I can see all 4, but of course you can't select units from that form.
Since they show in the Flyout and NRD but not after a CTRL-left click on their ports, it would seem the game file is damaged in some way.
RE: 3.1.0.1 - Can't send -ONE- TRS/AMPH out to sea
Posted: Mon Jan 06, 2020 8:55 pm
by Gar-Dog
ORIGINAL: paulderynck
...it would seem the game file is damaged in some way.
I have been known to hack things to change status, move units, and create units in the past, but I didn't ever touch this one. Strange... First turn after setup.
RE: 3.1.0.1 - Can't send -ONE- TRS/AMPH out to sea
Posted: Sun Feb 23, 2020 10:25 pm
by Shannon V. OKeets
ORIGINAL: Gar-Dog
ORIGINAL: paulderynck
...it would seem the game file is damaged in some way.
I have been known to hack things to change status, move units, and create units in the past, but I didn't ever touch this one. Strange... First turn after setup.
It took me a few hours but I determined that the data file was damaged. The units in question are marked as having moved in the impulse (and the turn) in the data file. They should have the ability to Undo the move, and the # of remaining/available naval moves should be zero (instead of 2).
My best guess is that you moved the units, undid the moves and then saved the game. When you then restored it, the data for those units was incorrect.
This is the first time I have seen this problem reported.
Attached is a corrected GAM file. I simply Disorganized the units and then Reorganized them - using the Debug ability available to the Beta Testers. That resets the Moved in Impulse data to False instead of True.
RE: 3.1.0.1 - Can't send -ONE- TRS/AMPH out to sea
Posted: Wed Mar 04, 2020 1:59 am
by Gar-Dog
Many thanks Shannon!
FYI, It looks like the savegame is set for a newer Beta Tester version. I edited it to my version and *at first glance* the savegame format appears to have loaded without error... Hopefully it's compatible (3.1.0.1). I'll check it out; I've been paused for a couple months anyway while real life intruded!