Threat Axis control in 3.8

[Shemar]

If this has been discussed before or if this is not the right place for it, please point me to the appropriate spot, as I am totally new to this forum.

Since I upgraded to version 3.8 (from 3.7) the user interface part for setting the Threat Axis in the Formation Editor has grown completely disobedient. It will either completely ignore my change and revert back to where it was, it will only accept my change partially, or sometimes it will do something completely different than what I am telling it to. It was working perfectly in 3.7. Needless to say I have the AI management of Threat Axis permanently off.

So I have a two-fold question:
a. Am I missing a setting somewhere? And if not, is there a work around? Some way to 'trick' the Threat Axis into obeying me?
b. Is there a list of fixes from 3.7 to 3.8? (Yes I do want to see if I should go back to using 3.7)

[R8J]

I am having the same problem.
 
Hopefully we'll get an answer.

[Shemar]

After some experimentation, it seems that the problem also exists in 3.7. It seems to be a lot more intense with wider therat axis settings and a lot more obedient (but still quite flaky) when the threat axis is narrow.

[Bucks]

Gents,

I might have a suggestion to ease this issue. I've seen the same thing and yeah it's annoying. I have also seen lots of other weirdness that is really user created.

When I set up formation air patrols, I set a course for the group. Simply selecting the ships and grouping them and having them all heading north (top of the map), I set a course by hitting F3, plot the couse and then cancel it by double clicking F3 again. I set my patrol zones and then use Edit -> Units -> Move Unit on the group. I zoom right in on the map and move the group say 1nm. I then return to the Formation editor and my ships will have assumed their formation patrol stations.

This allows me to check as I go, so to speak and I can then make any adjustments as required. It's not so much that the game is behaving strangely, more that it needs to be fully checked before you commit anything to a final save. I've been rebuilding scenarios and the amount of work and double checking required to allow for release is amazing. I'll say that this has in many ways allowed me to see exactly how H3ANW wants me to tell it what to do.

Cheers

Darren

[Shemar]

Bucks,
 
Thanks for the reply.
 
However I am not referring to the scenario editor but to the game itself. I am not creating a scenario I am trying to play one.
 
To reproduce my problem one would:
 
- Start any scenario in single player mode that includes a naval group.
- Go to the formation editor for any naval group
- Try to define the AAW threat axis for that group to point NE (45 degrees) and be about 160 degrees wide.
 
What you will experiense is that although you can drag both the edges (for width) and the tip (for heading) of the threat axis, to where you want them, as soon as you release the mouse button they will either jump back to their original position, or do something completely random and on very very few occasions they will actually obey.
 
Again, to avoid confusion I am not referring to setting patrol zones, I am referring to the step before that, which is to define the threat axis for a group. Not while designing a scenario, but while playing it.
 
Interestingly enough the ASW threat axis does not seem to suffer from this (although you can only manipulate its width not its heading since it always matches the groups PIM).
 
The only solution I have so far is to forget about the whole threat axis functionality and just use the ASW threat axis to deploy a fleet based on the path of movement rather than threat axis. Or to make my threat axis pretty narrow (under 45 degrees) which seems to help its 'obedience factor' a lot, and only use the directional aspect of the functionality and not the width (so I can't have my fleet's assets spread out automatically if the threat axis widens or concentrate if it narrows).

[Bucks]

Shemar,
Yes you're correct it doesn't seem to behave itself. I noticed this as well in scenedit. I think you're explanation of exactly how it's working is right. I'll take a further look as it may be related to an issue I had been keeping an eye on in regard to group vs single unit navigation.

I'll attempt to get a full explanation for you from the Devs and get back here with some "rules" for threat axis positioning ASAP.

Cheers

Darren

[Shemar]

That's great news. Thanks for taking the time to look into this. [:)]

I am doing some software development myself and I understand that a key to finding and fixing a bug is being able to reproduce it. I am glad I could help.

[Bucks]

I've brought this to the attention of the Devs and they are looking at it now. No promises or guarantees, although it is being looked at.

Cheers

Darren