[CANNOT REPRODUCE, MISSING TRACK] Lost ability to change radar range

[450Devil]

During a flight today on a MP server I was unable to change the radar range in either A2A or A2G modes. Fixed the issue when I landed and selected a new F18.

 

Screenshot attached.

Edited June 22, 2020 by 450Devil

[Charlie-1]

During a flight today on a MP server I was unable to change the radar range in either A2A or A2G modes. Fixed the issue when I landed and selected a new F18.

 

Screenshot attached.

 

I've had that quite a lot...I presumed I'd gone into a different mode or something as has come back, but without really knowing how.

 

I've also lost the ground radar elevation adjustment without knowing how?

[Wesjet]

I was able to reproduce this, with a TGP.

Any time I has a TGP designation point, I was unable to change the range scale of the radar in A/A or A/G mode. In all cases, undesignating with the pod and then going to the radar page solved.

 

Screenshot attached showing missing OSB markers on the right side of the DDI, as would normally be there. I am currently flying right now so a track is not available yet.

 

Edit:

 

Video link.

 

Edit 2:

 

Link to track, 80mb.

https://1drv.ms/u/s!Au6nuN4_FUp2grU1kH_qnXkD6kat-Q?e=mBYKRo

Edited June 23, 2020 by Tiburtius
Youtube video

[450Devil]

Tiburtius - I think you have nailed the issue. I had been using the TPG with AGM-65Es prior to the radar range issue emerging. Why the TPG should adversely impact the ability to change ranges on the radar is a question that needs fixing.

[VirusAM]

I was able to reproduce this, with a TGP.

Any time I has a TGP designation point, I was unable to change the range scale of the radar in A/A or A/G mode. In all cases, undesignating with the pod and then going to the radar page solved.

 

Screenshot attached showing missing OSB markers on the right side of the DDI, as would normally be there. I am currently flying right now so a track is not available yet.

 

Edit:

 

Video link.

 

Edit 2:

 

Link to track, 80mb.

https://1drv.ms/u/s!Au6nuN4_FUp2grU1kH_qnXkD6kat-Q?e=mBYKRo

 

This is not a bug....

when you have a target point it is shared between the Hornet sensors (similar to the SPI concept in the A-10C).

So locking a target with the TPOD will create a designate point also on the AG Radar.

If you undesignate it, you will be able to "point" the sensors (radar, TGP) where you wish.

So it is normal.

Now this should not happen in the AA radar mode (Ag target should not affect AA radar).

If you post the steps to reproduce or a short track (sorry but your 80MB one is too long to nail this) it will be possible to see what happens

[fmedges]

I was able to reproduce this, with a TGP.

Any time I has a TGP designation point, I was unable to change the range scale of the radar in A/A or A/G mode. In all cases, undesignating with the pod and then going to the radar page solved.

 

Screenshot attached showing missing OSB markers on the right side of the DDI, as would normally be there. I am currently flying right now so a track is not available yet.

 

Edit:

 

Video link.

 

Edit 2:

 

Link to track, 80mb.

https://1drv.ms/u/s!Au6nuN4_FUp2grU1kH_qnXkD6kat-Q?e=mBYKRo

 

I’ve seen this as well. Is this behavior intended?

[Thallios]

Observed this behavior today, after switching to CAP from CAS loadout. Even when TGP was removed after rearming this issue occured. Undesignate didn't change anything. I didn't try undesignate in A/G Mode though

[Wesjet]

This is not a bug....

when you have a target point it is shared between the Hornet sensors (similar to the SPI concept in the A-10C).

So locking a target with the TPOD will create a designate point also on the AG Radar.

If you undesignate it, you will be able to "point" the sensors (radar, TGP) where you wish.

So it is normal.

Now this should not happen in the AA radar mode (Ag target should not affect AA radar).

If you post the steps to reproduce or a short track (sorry but your 80MB one is too long to nail this) it will be possible to see what happens

 

I figured that this likely would not entirely fall into the bug category, and that there should be some link capability between the sensors.

 

You are correct in that switching to the A/A radar mode does return the radar to normal function including range scaling. It is when you not in either master mode, or in A/G mode but go to the A/A radar page that this occurs. I would have though there some indication that the radar is "not available" for A/A scanning due to the designation. At first glance, it appears to be "broken" until you realize what is going on. We don't always jump to A/A mode to check the radar scope (perhaps we should be?).

 

Apologies for not getting back to this sooner, I haven't spent time at my computer lately.

I figured this would be easily reproducible from the conditions and video.

 

Attach are the requested shorter track and mission file, which also shows the return to correct behavior under A/A master mode.

TGP-Radar-Test.miz

TGP-Radar-Test.trk