Not a Known ANW Issue? #02 - Ferry Mission fails to Launch

[Bucks]

Ferry Mission fails to launch

Ferry Mission that executed properly in 3.9.0 fails to launch in 3.9.3

Herman, I checked this, little concerned about missions with missing targets, anyway I always change your Time Compression. So this may be related to TC rather than missions.

I slowed it to 30 secs to 1 sec and when within a couple of mins to the hour elapsing and the mission commencing I went 5secs to 1sec. Mission launched, no issue. Suggest testing over range of TC, the Engine may be having an issue launching at highest TC as set in your save. I have screens of launched aircraft if required and I did not rebuild the scenario.

Also with the Posture Settings

Blue -> Hostile to Red
Red -> Friendly to Blue?

Just wondering about them both being on the one comm network as far as Red is concerned. Red couldn't declare hostile so would have to kill missile type weapons to survive? I mean the Skyraiders armed with Iron Bombs could attack unmolested?

Had to double take when I switched sides [X(]

Darren

[hermanhum]

That issue was already resolved with Patch 3.9.4 and is already posted to the List of Known ANW issues [resolved] as such.

[Bucks]

Yeah I know just touching on reporting and what you'd be prepared to help with?

Report notes were:

Ferry Mission fails to launch

[indent]Ferry Mission that executed properly in 3.9.0 fails to launch in 3.9.3[/indent]

1. Run [PDb] Ferry Mission fails to launch (3.9.3).scn in SE
2. Ferry mission assigned to AI side for Hangar will not launch.
3. Mission launched with no problem in 3.9.0

Would you be prepared to expand this a little for active (non resolved issues?)

[hermanhum]

Wow, I was under the impression that was one of my better/more succinct reports.  It kept the important details to a minimum and stayed on point, IMO.

However, if you would like additional detail, perhaps you could re-write it and suggest what else you think that I might need to add.  I didn't have any idea what might be causing it, but thought that seeing the problem would be the easiest way of knowing the problem. 

IIRC, the test file attached was as simple as possible, too.  It wasn't part of a huge scenario and was custom-built to show the behaviour.