Jump to content

Head on contacts don’t appear on radar after patch


alexej21

Recommended Posts

Hi,

I tested a simple mission after last OB patch - start from Cyprus, heading west to 4 MiG 21 in 35K. Head on situation in the similar altitude both on afterburn. I have datalink contact from more than 100miles distance. I can’t get contact on radar from Jester. I tried changing elevation, switching radar modes - no contact till we merged. 
I changed MiG21 by MiG29 and same results. I just managed to get contact for a few second to one 29.

 

I suspect the closure rate as the reason. If it is the case then we have a huge problem with F14 against other fighters.

[sIGPIC][/sIGPIC]

.....Vladimir, let's go to Sukhoi.......

Link to comment
Share on other sites

Yes. It seems like the issue.  I consider this as a huge problem because it happend to me in my first mission with F14 after patch. No special setup.  I am even afraid to open MP.. 

[sIGPIC][/sIGPIC]

.....Vladimir, let's go to Sukhoi.......

Link to comment
Share on other sites

In SP the workaround for now is to just jump to the RIO seat and change it. We hope we can implement this for Jester asap. In MP it shouldnt be much of a problem, because you shouldnt exceed such a closure rate anyway in BVR, you only put yourself at a disadvantage. If the other guy flies super fast, bad for him, slow down, let him fly into the missile. This is more or less how you should do it with or without the switch anyway. 🙂

But indeed it is an oversight and something that we want to fix asap. Unfortunately I dont think we will manage it before the hotfix. Adding Jester commands is a very difficult task, as easy as it sounds. Thank you for your kind patience!


Edited by IronMike
  • Like 2

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 comment
Share on other sites

Hi,

I tried again the same mission but I switched to the nose position in the beginning. - Radar worked fine. 

 

I understand that it is a not easy task to integrate the change to Jester menu. Can't you just hardcode default switch position to nose ? This should be an easy task possible for HotFix.

 

Thank you,

 

 

 

[sIGPIC][/sIGPIC]

.....Vladimir, let's go to Sukhoi.......

Link to comment
Share on other sites

16 hours ago, IronMike said:

In SP the workaround for now is to just jump to the RIO seat and change it. We hope we can implement this for Jester asap. In MP it shouldnt be much of a problem, because you shouldnt exceed such a closure rate anyway in BVR, you only put yourself at a disadvantage. If the other guy flies super fast, bad for him, slow down, let him fly into the missile. This is more or less how you should do it with or without the switch anyway. 🙂

But indeed it is an oversight and something that we want to fix asap. Unfortunately I dont think we will manage it before the hotfix. Adding Jester commands is a very difficult task, as easy as it sounds. Thank you for your kind patience!

 

What would be the unintended consequence of resolving this temporarily by making nose-on the default setting?

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache

Link to comment
Share on other sites

1 hour ago, captain_dalan said:

What would be the unintended consequence of resolving this temporarily by making nose-on the default setting?

 

Nothing, and we already did. We also added the Jester command to change it, it was quicker than I thought. 🙂

  • Like 1
  • Thanks 2

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 comment
Share on other sites

3 hours ago, Kula66 said:

Good news IM. Is this likely to be out next week as a hotfix, or are we looking at a months time?

 

I don't think we'll be able to squeeze it in, since cutoff was already before we finished it. We will try, but in about 3 weeks time the next patch should be ready. Sorry for the wait. Maybe we can ask for a hotfix in between, but not sure.

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 comment
Share on other sites

10 hours ago, alexej21 said:

Hi,

I tried again the same mission but I switched to the nose position in the beginning. - Radar worked fine. 

 

I understand that it is a not easy task to integrate the change to Jester menu. Can't you just hardcode default switch position to nose ? This should be an easy task possible for HotFix.

 

Thank you,

 

 

 

 

Both done and will be in the next patch 🙂

  • Like 1
  • Thanks 2

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 comment
Share on other sites

Sorry, perfect would have been (a) this switch change was introduced with a corresponding jester extension, or (b) a hot fix is out now. 
 

These issues just increase the perception that the 14 is full of issues/bugs 😞

Link to comment
Share on other sites

1 minute ago, Kula66 said:

Sorry, perfect would have been (a) this switch change was introduced with a corresponding jester extension, or (b) a hot fix is out now. 
 

These issues just increase the perception that the 14 is full of issues/bugs 😞

 

You are right, we should have caught that, but unfortunately during testing did not encounter situations exceeding the closure rates and did not think of the implications it could have.

Please accept our apologies for that. It is definitely an oversight that should not have happened. As for the hotfix, unfortunately we cannot define or significantly push cutoff dates, and it was impossible to fix it beforehand. Our apologies for that, too.

  • 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 comment
Share on other sites

There is already a community solution as a stop gap measure. I don't know who did it and if it is allowed to be spread, but there is a keyboard default.lua out there which put the aspect switch into the pilots "switchology" setup thingy.  The switch is bindable and works in VA, if setup there.

 

Not sure if worth the hassle while a hot fix seems to be around the corner.

Link to comment
Share on other sites

48 minutes ago, Skysurfer said:

Also, can you include the closure gates for each aspect position of said switch in the manual for reference? 

It's from the online manual:

Quote

The ASPECT switch (21) controls two different things depending on radar mode. In the pulse doppler search modes it controls the rate processing windows of the radar, NOSE sets 600 knots opening to 1,800 knots closing, BEAM sets 1,200 knots closing to 1,200 knots opening and TAIL sets 1,800 knots opening to 600 knots closing.

 

  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX3060   🥽 Rift S   🕹️ T16000M  TWCS  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

On 6/20/2021 at 4:52 PM, IronMike said:

 

Nothing, and we already did. We also added the Jester command to change it, it was quicker than I thought. 🙂

Damn....now that's how you spoil your customers! Should have went with the "If i push her any harder, she'll blow up captain"! 😉

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache

Link to comment
Share on other sites

3 minutes ago, Skysurfer said:

So TLDR leaving the aspect switch in NOSE for pretty much all intercept scenarios should be the way to go? Unless someone is literally in a hard notch/beam and/or running cold?

Afaik it will be new default settings at least for Jester. Hard to imagine someone running away from Tomcat with more than 600kts opening rate.

🖥️ Win10  i7-10700KF  32GB  RTX3060   🥽 Rift S   🕹️ T16000M  TWCS  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

24 minutes ago, draconus said:

Afaik it will be new default settings at least for Jester. Hard to imagine someone running away from Tomcat with more than 600kts opening rate.

 

yeah exactly and that gate should even deal with beaming targets rather well, in theory.

Link to comment
Share on other sites

Ideally, somewhere down the line, HB could teach Jester to automatically pick the most appropriate aspect setting for a given tactical situation. "Aspect auto" if you will. I'd rather like to focus on flying that thing than micromanage Jester some more. 🤷‍♂️

  • Like 3
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...