
Naval move crash
Moderator: Shannon V. OKeets
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
Naval move crash
Moved one ship.


- Attachments
-
- navalbug.jpg (685.75 KiB) Viewed 239 times
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
Here's the save. Move the French transport in Marseilles out to sea and it crashes the game. Reloaded from start of naval movement phase, skipped the Russian and CW naval moves, same thing happened again. One more game I'll never be able to complete (still haven't finished a single game, btw...)
- Attachments
-
- NavalMovement.zip
- (1.57 MiB) Downloaded 6 times
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
Got the same bug while trying to set up convoys at the start of a global war game. Can't even *start* a game with this patch.
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
here's the screenshot from the convoy setup. Tried reloading and setting up the convoys differently, same thing happened again.
For the love of all that is holy, please don't go another 5 weeks without patching this.

For the love of all that is holy, please don't go another 5 weeks without patching this.

- Attachments
-
- setup.jpg (519.01 KiB) Viewed 239 times
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
RE: Naval move crash
I assume that you are using the latest 1.1.8.1 public beta?
You have found a regression problem it looks like. I am sure Steve will look into this rightaway coming morning in Hawai,
This is why we have a public beta nowadays, I was happy that the first reaction was positive (4 hours play without problems using hot seat I read). Yours is troubling - given the first positive reaction we will probably have to look in the optionals to find this regression,
You have found a regression problem it looks like. I am sure Steve will look into this rightaway coming morning in Hawai,
This is why we have a public beta nowadays, I was happy that the first reaction was positive (4 hours play without problems using hot seat I read). Yours is troubling - given the first positive reaction we will probably have to look in the optionals to find this regression,
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
1.1.8.0 is so far as I can tell, the most recent. We don't have 1.1.8.1
Mine popped up within the first 10 minutes of playing. The first instance came in a game that was created under the previous version. I started a brand new game hoping that it was just a version compatibility issue, and that's when it happened in the convoy setup. The optional rules were not 100% identical, but close.
Mine popped up within the first 10 minutes of playing. The first instance came in a game that was created under the previous version. I started a brand new game hoping that it was just a version compatibility issue, and that's when it happened in the convoy setup. The optional rules were not 100% identical, but close.
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
RE: Naval move crash
ORIGINAL: Zartacla
1.1.8.0 is so far as I can tell, the most recent. We don't have 1.1.8.1
Mine popped up within the first 10 minutes of playing. The first instance came in a game that was created under the previous version. I started a brand new game hoping that it was just a version compatibility issue, and that's when it happened in the convoy setup. The optional rules were not 100% identical, but close.
Sorry, my mistake. I have 1.1.8.1 which is the same with the debug tools.
Again, I am sure Steve will look at this as soon as he checks his mail or checks this or the beta forum. I have made sure of that.
- Erik Rutins
- Posts: 39761
- Joined: Tue Mar 28, 2000 4:00 pm
- Location: Vermont, USA
- Contact:
RE: Naval move crash
Each week, any game-stopping bugs remain a priority alongside each functional area. I'm sorry for the frustration, but this is a good example of why we are doing public betas before official releases. Thank you for your help finding and catching this one.
Erik Rutins
CEO, Matrix Games LLC

For official support, please use our Help Desk: http://www.matrixgames.com/helpdesk/
Freedom is not Free.
CEO, Matrix Games LLC

For official support, please use our Help Desk: http://www.matrixgames.com/helpdesk/
Freedom is not Free.
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
Each week? We're down to less than one patch per *month*. Since this bug prevents an existing game from progressing a single turn and prevents new games from starting, one week is an unacceptably long time and one month is unthinkable.
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
Still getting an error message (or a debug message, I guess) but at least it's not crashing the game now.
edited to add - the message that comes up now is [TSectionForm.LoadButClick] C.
edited to add - the message that comes up now is [TSectionForm.LoadButClick] C.
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
RE: Naval move crash
ORIGINAL: Zartacla
Still getting an error message (or a debug message, I guess) but at least it's not crashing the game now.
edited to add - the message that comes up now is [TSectionForm.LoadButClick] C.
I have not seen this message yet at my side. Thanks for the edit to add. Not sure if it is necessary, but could you make a screenshot as well next time? I am triggered more visually. [8D]
How's the rest of the supply situation at your side in 1.1.8.2? We have a report of Territorials still being supply-buggy, which has been placed on the fix-list. Also the Yug HQ seems to ignore one of its own troops when there is an Italian Territorial next to it.
I also expect from you to find one or two last items.
RE: Naval move crash
Zartacla, I got the same message when loading a TRS arriving in a sea box. It does not results in problems indeed.


- Attachments
-
- 2014_04_26..d_France.jpg (32.63 KiB) Viewed 239 times
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
ORIGINAL: AxelNL
How's the rest of the supply situation at your side in 1.1.8.2? We have a report of Territorials still being supply-buggy, which has been placed on the fix-list. Also the Yug HQ seems to ignore one of its own troops when there is an Italian Territorial next to it.
I also expect from you to find one or two last items.
Have barely had a chance to play under 8.2. 8.0 was entirely unplayable for me. So far, I haven't found any supply issues and it's been a relief not to have to reload the game multiple times per turn in China. I haven't seen much action yet with territorials, and in my current game the plan is to attack - not align - Yugoslavia. So I won't be playing much with Pr Paul.
But so far, so good. Once lend lease is working and sunk convoys stop transporting goods, I would say the game is about ready for release
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
RE: Naval move crash
ORIGINAL: AxelNL
Zartacla, I got the same message when loading a TRS arriving in a sea box. It does not results in problems indeed.
![]()
I just discovered that after this message there can be a problem with loading savegames from the Main Form. It could give errors that the savegame cannot be loaded, which leads you to believe the savegame is corrupt (this is not always). These problems are not appearing when closing the game and restarting it again.
For the moment: when you have seen this message - do not reload autosaves or savegames from the Main Form menu. Close the game and reload from the splash screen.
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
That's been true for a while. Randomly (or seemingly randomly) saved games would give you that error when doing a save/reload but not when doing it from the splash screen. I don't think it's related to this specific bug.
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
RE: Naval move crash
ORIGINAL: Zartacla
That's been true for a while. Randomly (or seemingly randomly) saved games would give you that error when doing a save/reload but not when doing it from the splash screen. I don't think it's related to this specific bug.
You could be right, although I have not seen it that much myself - it was happening to two gamesaves, including an autosave which I did not touch, while experimenting with the strange message. It is probably memory which lingers on and not cleared when not closing the game. I think this is the reason why you cannot load more than three times from the Main Form.
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
Just found another lingering supply bug. Saved game won't help, because saving/reloading fixes the bug. In this case, German air ground struck a French unit then panzers moved in and cut its supply lines. The unit did not show as being out of supply. During land combat declaration, the unit was still not out of supply so I saved and reloaded the game, at which point it finally realized it was out of supply.
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
RE: Naval move crash
ORIGINAL: Zartacla
Just found another lingering supply bug. Saved game won't help, because saving/reloading fixes the bug. In this case, German air ground struck a French unit then panzers moved in and cut its supply lines. The unit did not show as being out of supply. During land combat declaration, the unit was still not out of supply so I saved and reloaded the game, at which point it finally realized it was out of supply.
We need the auto gamesave from starting the land move. Hope you have not done a next impulse yet.
I have been hunting these occurrences (almost became a personal vendetta), and have not been running into this one. I will try to recreate this if you don't have the autosave anymore.
I knew you would find one! You have not let me down [8D]
-
joshuamnave
- Posts: 967
- Joined: Wed Jan 08, 2014 3:51 am
- Contact:
RE: Naval move crash
Sorry, don't have the save anymore. Wouldn't think it's that hard to reproduce. It happened in the mtn hex just west of the southernmost maginot hex. I groundstruck the unit sitting in the hex then moved around it zoc'ing the supply line from Lyons. Saving and reloading it updated the French supply status.
Head Geek in Charge at politigeek.net - the intersection of politics and all things geeky
RE: Naval move crash
ORIGINAL: Zartacla
Sorry, don't have the save anymore. Wouldn't think it's that hard to reproduce. It happened in the mtn hex just west of the southernmost maginot hex. I groundstruck the unit sitting in the hex then moved around it zoc'ing the supply line from Lyons. Saving and reloading it updated the French supply status.
No worries - will reconstruct using the debug tool tomorrow. If you do run into the second one please post or mail me the autosave from the start of the land move phase ( I do expect you to find a second, but hopefully not more).

