Post by sloanjh on Aug 18, 2019 10:04:06 GMT -6
v1.07 (started as 1.05b), Admiral, manual legacy, VLarge, hacked file when switching to 1.07 to have positive air experience no greater than 39, France.
Severity: Not critical - clicking "ok" didn't seem to have bad effects.
Situation: I had a battle (cruiser action I think). BC main force, plus 3xCV in 2 divisions. Had spotted a CL contact, readied planes, and just hit the "launch" button for a 1 DB squadron strike, when weather worsened and air operations were shut down. I checked the squadron info tab, though, and the squadron was progressing through the launch sequence, and a while later I saw 20 DB flying around so I'm pretty sure it went ahead and launched the strike. (Note that during this process (I think before it launched) I saw at least one message about a CAP squadron returning due to weather).
So far so good; the 20 DB never found the enemy and the bad weather lasted about 9 hours. The weather eventually cleared, however, so I got ready to launch an air search (it would be REALLY nice to have a "launch search pattern" button to do this) with a few scouts. When I pulled up the strike menu, however, and tried to move to my second squadron's screen, I got the "SetupStrike SetTarget" error. I suspect the weather delay confused the state somewhere. Possibly related: I think I had only clicked on the "Target" button, not the "Location" button. I suspect one or a combination of three things:
1) My DB squadron that launched in the middle of a storm.
2) Clicking OK does put me in the other division's screen; one of the CVs has a group of F in "Ready > Flying" state.
3) I (possibly) only clicked on a target and not a location, so that was unset.
Note that the error went both ways in terms of switching between divisions - it didn't favor one or the other.
I just tried launching the recon sweep by hand (and ended up sending 18 DB to a single point - I'll log a separate issue for that) and it seems to be working in terms of putting the planes in "Unready>Flying" mode. That also cleared the error, possibly because I clicked location for that. Attaching a save file although I suspect it won't exhibit the error.
Severity: Not critical - clicking "ok" didn't seem to have bad effects.
Situation: I had a battle (cruiser action I think). BC main force, plus 3xCV in 2 divisions. Had spotted a CL contact, readied planes, and just hit the "launch" button for a 1 DB squadron strike, when weather worsened and air operations were shut down. I checked the squadron info tab, though, and the squadron was progressing through the launch sequence, and a while later I saw 20 DB flying around so I'm pretty sure it went ahead and launched the strike. (Note that during this process (I think before it launched) I saw at least one message about a CAP squadron returning due to weather).
So far so good; the 20 DB never found the enemy and the bad weather lasted about 9 hours. The weather eventually cleared, however, so I got ready to launch an air search (it would be REALLY nice to have a "launch search pattern" button to do this) with a few scouts. When I pulled up the strike menu, however, and tried to move to my second squadron's screen, I got the "SetupStrike SetTarget" error. I suspect the weather delay confused the state somewhere. Possibly related: I think I had only clicked on the "Target" button, not the "Location" button. I suspect one or a combination of three things:
1) My DB squadron that launched in the middle of a storm.
2) Clicking OK does put me in the other division's screen; one of the CVs has a group of F in "Ready > Flying" state.
3) I (possibly) only clicked on a target and not a location, so that was unset.
Note that the error went both ways in terms of switching between divisions - it didn't favor one or the other.
I just tried launching the recon sweep by hand (and ended up sending 18 DB to a single point - I'll log a separate issue for that) and it seems to be working in terms of putting the planes in "Unready>Flying" mode. That also cleared the error, possibly because I clicked location for that. Attaching a save file although I suspect it won't exhibit the error.
