Page 1 of 1
A Mutiny
Posted: Sat Aug 01, 2009 10:25 pm
by Bullwinkle58
Playing Aleutians scenario, June 7, 1943 as Allies, full-screen, versus AI. USS Nevada is reported in the Ships list as being in Paramushiro Jima with 13 system damage. The Japanese still own that island. She still has North Pacific as an HQ. I can't access her to move her, there is no icon on the map for an Allied ship there. I didn't move her there. She's in some kind of database limbo.
I saw a post about the CVE in this scenario disappearing in someone's game as well. Maybe there's a database bug causing both problems.
RE: A Mutiny
Posted: Sat Aug 01, 2009 11:37 pm
by Bullwinkle58
Replying to myself:
I loaded up the save game from the Japanese side. USS Nevada is not in an IJN base. They list her as sunk by torpedo near Kiska.
As Allies, I do not list her as sunk, or even damaged very much. I didn't recieve any sunk message on her. She was in the starting TF with the other BBs and CAs. USS Idaho took a lot of damage and I moved her into port in Dutch Harbor. She's still there. I moved that TF around some, did a few bombarment missions, etc. Never detatched Nevada.
So, is this some sort of uber-FOW where the Japanese are right and I think my own ship is sitting in a port she can't be? Or is it a DB glitch? Or something else?
RE: A Mutiny
Posted: Sun Aug 02, 2009 1:49 am
by treespider
ORIGINAL: Bullwinkle58
Replying to myself:
I loaded up the save game from the Japanese side. USS Nevada is not in an IJN base. They list her as sunk by torpedo near Kiska.
As Allies, I do not list her as sunk, or even damaged very much. I didn't recieve any sunk message on her. She was in the starting TF with the other BBs and CAs. USS Idaho took a lot of damage and I moved her into port in Dutch Harbor. She's still there. I moved that TF around some, did a few bombarment missions, etc. Never detatched Nevada.
So, is this some sort of uber-FOW where the Japanese are right and I think my own ship is sitting in a port she can't be? Or is it a DB glitch? Or something else?
So Nevada was still in your TF when you disbanded the TF?
RE: A Mutiny
Posted: Sun Aug 02, 2009 3:17 am
by Bullwinkle58
ORIGINAL: treespider
ORIGINAL: Bullwinkle58
Replying to myself:
I loaded up the save game from the Japanese side. USS Nevada is not in an IJN base. They list her as sunk by torpedo near Kiska.
As Allies, I do not list her as sunk, or even damaged very much. I didn't recieve any sunk message on her. She was in the starting TF with the other BBs and CAs. USS Idaho took a lot of damage and I moved her into port in Dutch Harbor. She's still there. I moved that TF around some, did a few bombarment missions, etc. Never detatched Nevada.
So, is this some sort of uber-FOW where the Japanese are right and I think my own ship is sitting in a port she can't be? Or is it a DB glitch? Or something else?
So Nevada was still in your TF when you disbanded the TF?
As far as I recall, I never disbanded it. I added some DDs into it, but the only ships that left were Idaho with major damage (left as an Escort group and was still repairing in Dutch Harbor at the end of the scenario.) At some point I just looked at my big Surface TF, with the BBs and CAs, and some DDs, and Nevada was gone. I went looking and found her in a Japanese base, not accessible to TF orders.
More strangeness. I forgot to post in my second one that, playing Allies, even when she was listed as being in P. Jima, I could go to the repair screen and shift her from Readiness to Pierside and change the repair priority. But I couldn't execute any other orders. This was at the same time the Japanese side listed her as sunk.
Also, when I finished the scenario tonight, she still listed as being in P. Jima to the Allied side. When I did the "examine map" thing and looked at the Japanese bases, she no longer was in their sunk list, or at P. Jima, or repairing, or anything. I assume that the Ships Sunk list after the scenario ends has no FOW in it, and the two looked like they matched (didn't run them against each other.) But whatever put Navada into an enemy base at pierside survived the end of the scenario and the removal of FOW from the Allied POV.
I have a save on June 7, 1943 after I noticed her in P. Jima. I could send it to anyone who wants it. (The Japanese Sunk list says she went down on May 20, 1943.)
RE: A Mutiny
Posted: Sun Aug 02, 2009 7:59 am
by Cmdrcain
On damage, ships WILL automatic detach if damaged enough and go into an escort TF that sets sail to a base...
Possiable it did that and ended up sunk but with fog of war on... maybe confusion in allies.
For sure

I had the CA Houston hit bad... a turn later I found it in Port and set it up again in a TF and tried move it elsewhere...
Had in the operations log a message about the houston being sunk was in error
AE has a deeper fog of war... perhaps your seeing a sunk Ghost ship..
RE: A Mutiny
Posted: Sun Aug 02, 2009 12:22 pm
by Don Bowen
ORIGINAL: Bullwinkle58
I have a save on June 7, 1943 after I noticed her in P. Jima. I could send it to anyone who wants it. (The Japanese Sunk list says she went down on May 20, 1943.)
Please post your save as an attachment to this thread.
RE: A Mutiny
Posted: Sun Aug 02, 2009 3:51 pm
by Bullwinkle58
ORIGINAL: Don Bowen
ORIGINAL: Bullwinkle58
I have a save on June 7, 1943 after I noticed her in P. Jima. I could send it to anyone who wants it. (The Japanese Sunk list says she went down on May 20, 1943.)
Please post your save as an attachment to this thread.
Just looked in the Saves folder for the first time. WOW! Lots of text files.
I think this is the correct file. I have it in Slot 3. If it's not, let me know.
RE: A Mutiny
Posted: Sun Aug 02, 2009 3:55 pm
by Bullwinkle58
ORIGINAL: Don Bowen
ORIGINAL: Bullwinkle58
I have a save on June 7, 1943 after I noticed her in P. Jima. I could send it to anyone who wants it. (The Japanese Sunk list says she went down on May 20, 1943.)
Please post your save as an attachment to this thread.
Since it's there, this is (I think) the combat report from May 20, 1943 when I believe the Japanese thought they sank Nevada.
RE: A Mutiny
Posted: Sun Aug 02, 2009 3:58 pm
by Bullwinkle58
ORIGINAL: Cmdrcain
On damage, ships WILL automatic detach if damaged enough and go into an escort TF that sets sail to a base...
Possiable it did that and ended up sunk but with fog of war on... maybe confusion in allies.
For sure

I had the CA Houston hit bad... a turn later I found it in Port and set it up again in a TF and tried move it elsewhere...
Had in the operations log a message about the houston being sunk was in error
AE has a deeper fog of war... perhaps your seeing a sunk Ghost ship..
All that makes sense, except that, after the scenario ends and FOW isn't a factor, neither side lists her as sunk, but from the Allied POV she's sitting pierside in a Japanese base, trying to repair 13 system damage, while from the Japanese POV she's nowhere to be seen.
RE: A Mutiny
Posted: Sun Aug 02, 2009 7:51 pm
by Don Bowen
Got the save, thanks. Will take a look (probably tomorrow).
RE: A Mutiny
Posted: Mon Aug 03, 2009 11:17 am
by Don Bowen
ORIGINAL: Bullwinkle58
All that makes sense, except that, after the scenario ends and FOW isn't a factor, neither side lists her as sunk, but from the Allied POV she's sitting pierside in a Japanese base, trying to repair 13 system damage, while from the Japanese POV she's nowhere to be seen.
See the problem in the save, but no clues (yet) as to why. Fog of War was involved but should obviously not have docked an Allied ship at a Japanese base.
Do you have an earlier save? Something closer to May 20, 1943.
RE: A Mutiny
Posted: Mon Aug 03, 2009 4:08 pm
by Bullwinkle58
ORIGINAL: Don Bowen
ORIGINAL: Bullwinkle58
All that makes sense, except that, after the scenario ends and FOW isn't a factor, neither side lists her as sunk, but from the Allied POV she's sitting pierside in a Japanese base, trying to repair 13 system damage, while from the Japanese POV she's nowhere to be seen.
See the problem in the save, but no clues (yet) as to why. Fog of War was involved but should obviously not have docked an Allied ship at a Japanese base.
Do you have an earlier save? Something closer to May 20, 1943.
Unfortunately, no. Slot 4 is my current game, the Guad. scenario, and the autosave slot relates to that. I usually don't have multiple saves of a current game. Maybe stupid of me.
RE: A Mutiny
Posted: Mon Aug 03, 2009 4:36 pm
by Don Bowen
ORIGINAL: Bullwinkle58
ORIGINAL: Don Bowen
Do you have an earlier save? Something closer to May 20, 1943.
Unfortunately, no. Slot 4 is my current game, the Guad. scenario, and the autosave slot relates to that. I usually don't have multiple saves of a current game. Maybe stupid of me.
No worries. When I get a chance I'll glance over code and see if anything jumps out at me. If you happen to see it again, just send a save.
RE: A Mutiny
Posted: Mon Aug 03, 2009 4:51 pm
by Rainer
Just a tip for later:
I use the slot number which corresponds with the date.
Meaning: Save after "Orders Given" on, say January 21, will go into Slot #21. Next into #22 and so on.
The only catch: there is no slot #1, so you have to use slot #2 for day 1 and day 2.
This way you can go back a full month if needed or to any other day within the last four weeks.
Helps a lot with identifying issues.