Trouble finding radar targets since 1.5.5

[Raven434th]

Since 1.5.5 I'm having difficulty finding targets on radar where I didn't have any trouble before,and I have no idea why.I'm not seeing them until around 10-12 miles when they're practically on top of me.I'm scanning vertically,setting expected range,switching rpf but still not getting contacts where I normally would before the patch 1.5.5.Has anyone else noticed this??

 

:cry:

[feefifofum]

@ Raven what airframe?

 

I've been spotting targets at the expected distances in the F-15C and M-2000C in 1.5 recently.

 

Fighters 20-30 ish miles flanking, 60-80 hot depending on size.

 

Keep in mind vertical scan is an auto-aquisition mode that will only lock targets at close ranges.

Edited November 20, 2016 by feefifofum

[Raven434th]

vertical scanning as in manually adjusting the radar in the vertical in bvr mode.As for airframe I mostly fly the russian birds,but I've had the same problem in the f-15 as well.

[AtaliaA1]

vertical scanning as in manually adjusting the radar in the vertical in bvr mode.As for airframe I mostly fly the russian birds,but I've had the same problem in the f-15 as well.

 

 

Running the Sim. on that System is pretty good.

 

 

You have to set to low graphics?

 

Do you get stuttering?

[Raven434th]

My settings are medium to high,and yes I get the occasional stutter but its only when switching from one view to another.But this isn't the problem I'm concerned about...its the inability to find radar targets in the HUD where I had no problem before.They are simply not showing up until well under where they used to be.The really wierd thing is I can find targets in EOS FURTHER OUT than It used to be or so it seems.But I only discovered this last night and on a modded aircraft (Su-30sm mod) I was able to lock a headon aspest fighter at 90 km in EOS. That surprised me.Will do more testing and maybe get a trk file loaded.

 

Question...what effect does trying to locate an enemy fighter AT SAME ALTITUDE have??? Should it be harder or easier?? And about when should I expect a contact distance wise to become visible on radar(in my hud on a russian bird)? This might be the problem.(doesn't explain why I had no trouble before 1.5.5 though)

Edited November 21, 2016 by Raven434th

[feefifofum]

It's less about relative altitude and more to do with the what is behind the aircraft you're trying to acquire.

 

You'll have the easiest time detecting aircraft of any type against an open sky. If your target has arranged themselves so that they are below the horizon relative to your aircraft, you'll have a much more difficult time finding them.

 

For a head-on target, you can expect to detect them around 70 miles out against an open sky, give or take a few depending on the size of the target in question. You'll want to be sure you're scanning with a 30deg azimuth (SCAN ZONE DECREASE keyboard command) and that your PRF is set to high.

 

For a target that's flanking or cold, or one that's very close to you, medium PRF will produce the best results. You can expect to find a fighter-sized target at this aspect somewhere between 20 and 30 miles, again depending on target size.

 

For the Russian birds, your RADAR configuration will affect what you see on the HUD but targets will appear as soon as they're detected regardless of your settings.

To elaborate:

 

You have a control called "expected range" in the Flanker. You'll see this reflected in the bottom of the HUD. A target beyond the maximum expected range will still be visible on the HUD (provided you have detected it with the methods described above); the expected range simply affects how the HUD is displayed. For example, if you detect a target at 60km but your expected range is set to 10km, the target will display at the very top of the HUD.

 

Conversely, if your expected range was set to 120km, your 60km target would appear in the center of the HUD. Expected range will also affect your antenna elevation (the -1/+1 etc. number on the right side.) Using our example from before, if we're at 5000 meters and our target is at 60km at 4000km;

We'd set the expected range to 60km and the antenna elevation to -1 (-1000 meters relative altitude)

 

Make sense?

Edited November 26, 2016 by feefifofum

[Ironhand]

...

 

You have a control called "expected range" in the Flanker. You'll see this reflected in the bottom of the HUD. A target beyond the maximum expected range will still be visible on the HUD (provided you have detected it with the methods described above); the expected range simply affects how the HUD is displayed. For example, if you detect a target at 60km but your expected range is set to 10km, the target will display at the very top of the HUD.

 

Conversely, if your expected range was set to 120km, your 60km target would appear in the center of the HUD. Expected range will also affect your antenna elevation (the -1/+1 etc. number on the right side.) Using our example from before, if we're at 5000 meters and our target is at 60km at 4000km;

We'd set the expected range to 60km and the antenna elevation to -1 (-1000 meters relative altitude)...

Unfortunately this is incorrect. Expected Target Range has nothing to do with how high on the HUD a return is displayed. That is controlled by the range scale ("=" and "-") keys. Expected Target Range does, however, as you note, control how far above or below your nose the radar is pointing as you move the scan through the vertical. It's there to help you center your antenna on a known target (as in your example). Other than that, there's little benefit to changing it in a general search.

 

As for the OP, nothing was changed in terms of how far you should be able to see targets. So something must have gotten screwed up when up updated.

Edited November 26, 2016 by Ironhand

[feefifofum]

Thanks, Ironhand. Learn something new every day!

Now I have to find room for expected range on my HOTAS, I've just been scaling the HUD and thought that was the thing!

 

If I may prod further, where is expected range visually indicated in the cockpit?

 

Serves me right chiming in on a Flanker thread. :lol:

[Ironhand]

...

 

If I may prod further, where is expected range visually indicated in the cockpit?

 

...

Other than on the HUD? Since none of the buttons/dials in the pit are functional, I've never worried about which switch did what.

[feefifofum]

I see where I got tangled up now.

 

Correctly thought the indicator on the HUD showed expected range.

 

Mistook the = and - keystroke to adjust said HUD indicator, rather than the HSD (I have both functions bound to other controllers) so I was thinking then that I had a whole other set of controls I hadn't mapped...

 

Haven't been bungling too badly on my few Flanker excursions!

 

Thanks for clearing the cobwebs. :thumbup: