[FIXED] [1487] WRA Automatic Firing Range issue

[TBLackey]

v1.07 Build 1487

My Spanish Eurofighters have Meteor WRA automatic firing range set to 50% of max (in the 'Air Superority' patrol mission), but as you can see they still fire at maximum firing range. Am I doing something wrong?

[Kushan04]

Logged #16395

[turmoil]

I've had this happen often, I have to go into the WRA options and specifically select 50% (not just leaving it at 50% automatic). I'm not sure it's still an issue with build 1500 though, I've gone in manually and changed anything that can hit air targets.

[blu3s]

I've had this happen often, I have to go into the WRA options and specifically select 50% (not just leaving it at 50% automatic). I'm not sure it's still an issue with build 1500 though, I've gone in manually and changed anything that can hit air targets.

Can you please clarify a little?

Is the value of 50ofmax already given by default in the scenario?

[turmoil]

I've had this happen often, I have to go into the WRA options and specifically select 50% (not just leaving it at 50% automatic). I'm not sure it's still an issue with build 1500 though, I've gone in manually and changed anything that can hit air targets.

Can you please clarify a little?

Is the value of 50ofmax already given by default in the scenario?

So in most scenarios they have "System default, 50% of max" and I found this wasn't being respected, at least by aircraft, but it was when I changed it to "50% of max (XXnm)" or anything else.

I just tried in the AAW 4 tutorial and the F-15Is fired the AIM120-C7 at ~60nm, even though the WRA says "System default, 50% of max" and once I change it to "50% of max (32nm)" they fire at the correct distance.

Edit: this is in build 1500 to clarify

[Tcao]

I guess this bug is related to scenario rebuilt. setting the WRA to 50% during the scenario rebuilt will change the WRA setting but the game won't read the correct distance.

[Swant]

This issue was marked as fixed but it never was

https://www.matrixgames.com/forums/view ... 0&t=396781

[mikerohan]

This issue was marked as fixed but it never was

https://www.matrixgames.com/forums/view ... 0&t=396781

or it is a regression bug...

[Swant]

This issue was marked as fixed but it never was

https://www.matrixgames.com/forums/view ... 0&t=396781

or it is a regression bug...

True, but the bug has been there for almost a year. Since v1.06 1328.12 at least

[mikerohan]

Hi,

any news on this issue? Or has anybody found a workaround?

I know I can change manually my WRA, but what about the "other side"? that is, without changing sides and spoiling some of the fun

Thanks!

[blu3s]

We didn't forget about it, it has just caught up with other changes/fixes in the doctrine so it is being a little bit more complicated but hopefully we will have a fix ready soon...

[mikerohan]

Thanks for the heads up!

[rosarioed]

Hello, this turned out to be a multi part issue and took a bit to identify and fix properly.

That said, it is now fixed and will no longer be present in the next CMO hotfix or release.

[mikerohan]

Great news! and thanks!

[jason oates]

Hi, While i get the setting for 50% of range, the Meteor is slightly different in that it has an on board engine not a rocket motor so it can fly to 100% at full speed with less drop in speed/performance.

[Klahn]

Hi, While i get the setting for 50% of range, the Meteor is slightly different in that it has an on board engine not a rocket motor so it can fly to 100% at full speed with less drop in speed/performance.

You can set up WRA on a per weapon and per target basis. So you can set the Meteor to fire at a longer range against slower and less maneuverable targets. Remember that you can also set the WRA to match the NEZ.