Radar trouble

[Hydrox]

Why am I not getting any readings with radar?

See attached pictures.

 

:joystick:

[Ironhand]

Are they above or below your scan zone? Or hidden in the terrain?

[Hydrox]

Not behind any terrain and you can see the radar zone pointing right forward. Tried with all different scan modes, yet this game keeps doing that every now and then. So I'm wondering if I am doing something wrong afterall.

[cardboard_man]

The radar on the su27 points the center of the scan cone towards the point in the sky you set and holds it there. The distance ahead of you is set with the number at the bottom of the HUD in Km. The altitude above or below you is set with the number in thousands on the right of the HUD. e.g. if you set to 25.0 and 3 it will center the scan cone and hold it on the point 25km ahead of you and 3000m up. I should also say that the set range will not stop the radar from detecting targets that are further away than the range you set.

 

In your case Lower the scan cone by 1 as they they look like they are about 1000 below you and increase the scan range by 50 as you know the range to them is around 50km. In situations where you don't know the range i like to set just the range to 30km and keep it there while just changing the relative altitude.

 

Are they flying towards, away or perpendicularly to you? I cant really tell from the screen shots but it looks like the a10's are flying close to perpendicular so they may be hard to detect you might find them with med PRF.

[Ironhand]

Not behind any terrain and you can see the radar zone pointing right forward. Tried with all different scan modes, yet this game keeps doing that every now and then. So I'm wondering if I am doing something wrong afterall.

Assuming it's not a terrain issue (either masking or ground clutter interference), then the next likely suspects are altitude differential and aspect. With you radar set to the "10" km expected target range, simply try scanning +1 and -1 expected target elevation. Since you know (from the labels) how far away from you the targets actually are, one of those setting should pick them up, if altitude differential is the issue. +2 and -2 are about the most you would need to change the elevation if the range closes more.

 

If it's an aspect issue--crossing target--you might have a hard time picking them up until the range closes considerably or, if they are beam on, you might not pick them up at all.

[Hydrox]

Actually I think I found the issue here, kinda stupid of me, my display range is too much, they simply don't fit the HUD, if they were say.. 90kms away, then I'd see them at lower half of the HUD. So I should have 20 display range to see them on HUD.

 

Good that I ask the questions, otherwise I'd never answer myself....

[Chrinik]

Yeah guys, that´s all fun and games and good explaination, but that was not the issue, considering one of the contacts shows up on the HDD and still doesn´t appear on the HUD. Something is going on there.

 

I would say lower the display range, I never use 200 clicks for anything.

Edited March 7, 2016 by Chrinik

[Hydrox]

I only have it when I put AWACS, so can see the enemy on display screen to get heading if it's very far away. And well this time.... apparently.

[cardboard_man]

I'm not sure what you mean. In the su27 Even if your display range was 500 it would still show the targets on the bottom of the HUD and if the display range was too short they would be shown at the top.

 

Also the The target on the hdd is a data link target. You can tell because it has an open triangle on the back rather than a closed one.

 

edit: Sorry i did not see your post before i posted this maybe because i had not refreshed the page in a while. Anyway if you set up the radar range and altitude properly you should be able to see at least the f16 as it seems to be coming towards you. As said before the a10s will be hard to see till you get closer as they are close to flying perpendicular to you

Edited March 7, 2016 by cardboard_man

[holimoli]

Actually I think I found the issue here, kinda stupid of me, my display range is too much, they simply don't fit the HUD, if they were say.. 90kms away, then I'd see them at lower half of the HUD. So I should have 20 display range to see them on HUD.

 

Good that I ask the questions, otherwise I'd never answer myself....

 

Was it rly the HUD range? It looks more like the contacts are below/right to you and thats why u don't pick them up.

 

edit: just checked the pics..it really looks like they are just below and right to you...and trying to pick up a F16 90km away in MED PRF most probably ain't gonna happen ;)

Edited March 7, 2016 by holimoli

[Hydrox]

Comment about AWACS didn't relate to this issue, I just said reason for using larger display range.

And yes, changing display range leaves enemies on HUD in any range if they were there at the beginning.

 

 

"and trying to pick up a F16 90km away in MED PRF most probably ain't gonna happen"

 

You can probably see that I went through all different modes. Also I scanned earlier a lot with low as far as -8 also left, right etc. and didn't see them.

 

Point is enemies are at my nose, radar is scanning forward +30/-30 is it? It really doesn't pick them up that's what I wonder.

Edited March 7, 2016 by Hydrox

[Chrinik]

Sometimes there are other factors at play.

 

Just from the pictures alone I cannot determine what´s going on to replicate it.

[holimoli]

Comment about AWACS didn't relate to this issue, I just said reason for using larger display range.

And yes, changing display range leaves enemies on HUD in any range if they were there at the beginning.

 

 

"and trying to pick up a F16 90km away in MED PRF most probably ain't gonna happen"

 

You can probably see that I went through all different modes. Also I scanned earlier a lot with low as far as -8 also left, right etc. and didn't see them.

 

Point is enemies are at my nose, radar is scanning forward +30/-30 is it? It really doesn't pick them up that's what I wonder.

 

 

yes, changing the HUD range/scale does not affect your radar. It only changes how information is displayed on the HUD and HDD...

 

you can pick up F16 up to ~110km away in HI PRF if they are hot actually.

 

I know what's your point is and I kindly suggest to try it again. Go through different PRF settings and manipulate the radar in elevation/azimuth and always wait 2-3 sec everytime you change something.

[Hydrox]

Yes, will do - it's not like it's happening all the time. just occasionally gets me wondering whether it's bug free or am I bugged.

[cardboard_man]

I don't believe the elevation scan is 60 degrees. You might be thinking of the maximum antenna tilt, they are different things.

The elevation scan coverage changes depending on the set range and altitude (At least with the real radar it might be simplified in the sim.) and is probably closer to 10 degrees.

Edited March 7, 2016 by cardboard_man

[Hydrox]

This is pretty much how I see it. A-10s... hmmm, but F-16 is stealth?

[Ironhand]

Hydrox,

 

Hadn't noticed the datalinked contact in the HDD last night. My apologies. Interesting that the A-10 doesn't show up as a datalink at all.

 

But that F-15 is well below your altitude, at least at the start. He was down around 2000 or so meters and just under your scan zone given your altitude. You would need to be at -1 to see him. Assuming he wasn't rising to meet you, you would have to drop to -2 to see him once the range closed to 35 km or so.

 

EDIT: BTW, I noticed you pointing your nose down in some of those images. Just want to make sure you realize that doesn't lower your radar scan. It continues scanning where you told it to unless you change your pitch so much that it is forced to scan further down because of the gimbal limits.

Edited March 7, 2016 by Ironhand

[Hydrox]

VVI should give you a hint, F-16 is right in FRONT of me. if the radar isn't pointing forwards like the HUD says, where is it pointing?

[Ironhand]

VVI should give you a hint, F-16 is right in FRONT of me. if the radar isn't pointing forwards like the HUD says, where is it pointing?

If this statement is directed at me, the radar is pointing forward but it's scanning the the same section of sky. The scan doesn't lower with your nose. That's what I'm referring to. If you check the HUD reference lines on vertical scale, you'll see that you are still scanning the same piece of the sky (elevations) you were scanning in level flight.

Edited March 7, 2016 by Ironhand
Change last statement from "at the start" to "in level flight"

[holimoli]

VVI should give you a hint, F-16 is right in FRONT of me. if the radar isn't pointing forwards like the HUD says, where is it pointing?

 

whats the altitude of the contacts?

 

edit: Most probably the F16 is below 5300m ;=)

Edited March 7, 2016 by holimoli

[holimoli]

I don't believe the elevation scan is 60 degrees. You might be thinking of the maximum antenna tilt, they are different things.

The elevation scan coverage changes depending on the set range and altitude (At least with the real radar it might be simplified in the sim.) and is probably closer to 10 degrees.

 

what do you mean?... u can scan 60° up and -35° down in elevation. The radar cone is 10° in heigth and 60° in width....and no the scan coverage doesn't change at all. Regardless of your settings. The radar beam cannot be changed. You can only manipulate the antenna/radar up-down and left-right

[Hydrox]

A-10s should be around 6700m MSL - <1500 mountains and F-16 headed my way, I'd say 6000+. hard to say, can't see the my exact aoa to calculate the F16s alt.

Edited March 7, 2016 by Hydrox

[holimoli]

can u not just check on f10 ? :P

[Hydrox]

Should have taken .trk, but didn't..

[holimoli]

however...the F16 is mostly likely below your scan area...so you have to lower your antenna/radar beam by atleast 1. The right number should be "-1" and you should see the F16 then.