Jump to content

Same Situation


Recommended Posts

I've ran through 10 scenarios, Jester has refused to lock the contact in 9 of them, optimal acquisition conditions. This is what I am experiencing, I'm getting same performance from turn rates as before the patch. I'm not trashing the module, I was only sharing my feedback. When I try reviewing a track that involves the Tomcat, it doesn't repeat the flight that I did. But I know this is with the strange behavior of the track replay tool, it does weird stuff with a lot of the modules. I'm working on numbers and clips to share from in game and TV. I'll remove the previous post until I get them ready to upload.


Edited by rwbishUP
postpone previous until add supporting data

Hebrews 13:2

 

“Be not forgetful to entertain strangers: for thereby some have entertained angels unawares.”

Link to post
Share on other sites
6 minutes ago, rwbishUP said:

No luck on Aim-54 tracking, all three variants, engagement within 25nm. Blue and Red both approx. FL270, even with AI set to no reaction to threat.

 

Was able to get Aim-7mh to track well enough for a kill, but only in head on engagement, within 6nm and closing, no evasive maneuvers by target, around 300ft v seperation, between 14 and 15 thousand msl.

 

Jester refuses to lock 99% of BVR contacts, and flight model seems to be the same as before update.



Thank you for the feedback. For the first it would be good to see/know more, maybe you can share the mission, so we can try the exact same thing.

"The Jester refuses and flight model seems same", is impossible though. Jester locks for me 7/10, after the patch. The flight model did change, clearly, back to what it was, and has been tested and confirmed by numerous others. Please do not base such statements on "impressions" but compare the numbers.


Edited by IronMike
  • Like 1

Heatblur Simulations

 

Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage.

 

http://www.heatblur.com/

 

https://www.facebook.com/heatblur/

Link to post
Share on other sites

What bind are you using to STT? I've found Jester does not like the "Lock Hostile target ahead" command unless he himself has IFFed the target even if you have AWACS Datalink telling you its a hostile. I find either "Lock target ahead" or primary "Choose specific target" to be the best option for using Sparrows in STT. 


Edited by Southernbear
Link to post
Share on other sites
8 minutes ago, Southernbear said:

What bind are you using to STT? I've found Jester does not like the "Lock Hostile target ahead" command unless he himself has IFFed the target even if you have AWACS Datalink telling you its a hostile. I find either "Lock target ahead" or primary "Choose specific target" to be the best option for using Sparrows in STT. 

 

 

 

Indeed, this is also very important to consider. Bandit is considered as bandit by Jester only, if he IFFed him. If not, target ahead works for example, because it doesnt rely on IFF.

  • Like 1

Heatblur Simulations

 

Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage.

 

http://www.heatblur.com/

 

https://www.facebook.com/heatblur/

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...