Jump to content

Radar Not Displaying Contacts


Horns

Recommended Posts

I’ve often had hostile contacts directly in front of me and physically visible but not present on the radar screen at 4 bar scan, +- 60 degrees azimuth, PPI or B-Scope, low, high or interleaved PRF and within 20 nm with scan range at 40 nm. Is this a known bug?

 

I did find some older posts about a B-Scope specific bug that made targets disappear after showing up. Does anyone know if there is a B-Scope bug like that in effect now?


Edited by Horns
Added mention of PRF

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis] [NTTR] [PG] [SC]

Intel i7-12700F, Nvidia GTX 3080, MSI MPG Z690 Carbon WiFi, 32GB DDR4 @ 1600 MHz, SteelSeries Apex Pro, Razer Basilisk 3

VKB Gunfighter 3 w/ F-14 grip, Thrustmaster Warthog throttle, Thrustmaster MFD Cougars x2, MFG Crosswind,

DSD Flight Series button controller, XK-24, Oculus Rift (HM-A)

Link to comment
Share on other sites

I’ve often had hostile contacts directly in front of me and physically visible but not present on the radar screen at 4 bar scan, +- 60 degrees azimuth, PPI or B-Scope, low, high or interleaved PRF and within 20 nm with scan range at 40 nm. Is this a known bug?

 

I did find some older posts about a B-Scope specific bug that made targets disappear after showing up. Does anyone know if there is a B-Scope bug like that in effect now?

 

The best thing the next time it happens would be to record the track and share it.

There were some complains but to my knowledge no bug confirmed.

Mirage fanatic !

I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2.

Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi

Link to comment
Share on other sites

The best thing the next time it happens would be to record the track and share it.

There were some complains but to my knowledge no bug confirmed.

 

Will do, I was kicking myself for not thinking to post about this before deleting my tacview files too.

 

Might be incorrect radar elevation.

 

That might have been the case for some, but several showed in tacview as being within 1k feet of my altitude at a range of up to 20 nms, so I'm not sure antenna elevation could be the cause of those...

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis] [NTTR] [PG] [SC]

Intel i7-12700F, Nvidia GTX 3080, MSI MPG Z690 Carbon WiFi, 32GB DDR4 @ 1600 MHz, SteelSeries Apex Pro, Razer Basilisk 3

VKB Gunfighter 3 w/ F-14 grip, Thrustmaster Warthog throttle, Thrustmaster MFD Cougars x2, MFG Crosswind,

DSD Flight Series button controller, XK-24, Oculus Rift (HM-A)

Link to comment
Share on other sites

Target aspect (hot/ cold) also has an effect.

 

Ta. I know at least some of the time it was hot because they flew right past me (or into me on one occasion), but I will stay mindful of that.

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis] [NTTR] [PG] [SC]

Intel i7-12700F, Nvidia GTX 3080, MSI MPG Z690 Carbon WiFi, 32GB DDR4 @ 1600 MHz, SteelSeries Apex Pro, Razer Basilisk 3

VKB Gunfighter 3 w/ F-14 grip, Thrustmaster Warthog throttle, Thrustmaster MFD Cougars x2, MFG Crosswind,

DSD Flight Series button controller, XK-24, Oculus Rift (HM-A)

Link to comment
Share on other sites

I asked if this was bugged so I wouldn't waste time trying to figure out something that was just working wrong. Since there's no known issue I'll let this rest here and go back to trying to find a technique that works :)

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis] [NTTR] [PG] [SC]

Intel i7-12700F, Nvidia GTX 3080, MSI MPG Z690 Carbon WiFi, 32GB DDR4 @ 1600 MHz, SteelSeries Apex Pro, Razer Basilisk 3

VKB Gunfighter 3 w/ F-14 grip, Thrustmaster Warthog throttle, Thrustmaster MFD Cougars x2, MFG Crosswind,

DSD Flight Series button controller, XK-24, Oculus Rift (HM-A)

Link to comment
Share on other sites

SP, I haven't been into MP at all so I don't know if it happens there...

 

It is most common in the instant action missions "Missile Combat" and "Constant PEG II", but then that's mostly what I play so that might be coincidence.

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis] [NTTR] [PG] [SC]

Intel i7-12700F, Nvidia GTX 3080, MSI MPG Z690 Carbon WiFi, 32GB DDR4 @ 1600 MHz, SteelSeries Apex Pro, Razer Basilisk 3

VKB Gunfighter 3 w/ F-14 grip, Thrustmaster Warthog throttle, Thrustmaster MFD Cougars x2, MFG Crosswind,

DSD Flight Series button controller, XK-24, Oculus Rift (HM-A)

Link to comment
Share on other sites

I ran the same mission again but this time with my Mirage 180 feet off the deck; only picking them up at 30 Nm again. My flight got nails but I didn't (maybe because I'm further left of them). So I don't know if you are right or not about this not being a bug. It seems to be 30 Nm every time, no matter if I'm higher or lower than them, and with no terrain in the way. I would say these are pretty much best conditions no?

 

At 180 feet you get ground clutter so it's not better. Try 20 kft co-alt, you should see better results.

 

Nail is like spike IIRC, it does not means your flight have them on radar.

 

Again, from what I see, no bugs here. And 180 ft is NOT best condition at all.

Helljumper - M2000C Guru

 

Helljumper's Youtube

https://www.youtube.com/channel/UCK3rTjezLUxPbWHvJJ3W2fA

Link to comment
Share on other sites

I picked him up at 50 Nm this time with both of us at 20,000 feet. So maybe it's just because they are so low. Looks like you are correct from what I can tell now. Thanks!

 

"Also, low flying threats will be much more

difficult to find." - Page 233 Manual

 

Happy to help :)

Helljumper - M2000C Guru

 

Helljumper's Youtube

https://www.youtube.com/channel/UCK3rTjezLUxPbWHvJJ3W2fA

Link to comment
Share on other sites

I realize now that I worded the OP badly. The question I should have asked was "is contact detection expected to get easier, or can I solve this through improving my application of it alone? In other words, I should have been clear in acknowledging that this behavior may be due to a faithful recreation of the RL radar rather than a bug needing to be squashed.

 

Edit: To be clearer still (not my strong suit): “do Razbam intend to mitigate this from their side, or do I need to find my own answer?”


Edited by Horns
Added further clarification

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis] [NTTR] [PG] [SC]

Intel i7-12700F, Nvidia GTX 3080, MSI MPG Z690 Carbon WiFi, 32GB DDR4 @ 1600 MHz, SteelSeries Apex Pro, Razer Basilisk 3

VKB Gunfighter 3 w/ F-14 grip, Thrustmaster Warthog throttle, Thrustmaster MFD Cougars x2, MFG Crosswind,

DSD Flight Series button controller, XK-24, Oculus Rift (HM-A)

Link to comment
Share on other sites

  • Recently Browsing   0 members

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