reported earlier Radar range is not saved for each master mode

[LanceCrown]

I noticed this behaviour initially with the Dogfight switch, which i dont think is normal.

 

I am using the steam version, current stable (2.5.something). No mods. only module i own is the viper.

 

I think everyone can reproduce it by performing the following steps:

 

Start plane in air. Check your Radar, it should be in FCR Mode and with 40nm range displayed. It stays in 40nm range even if you switch into A-A mode, or into missile override mode.

 

Set switch to Dogfight position: Radar changes to ACM mode and range is lowered to 10 miles in the radar. That is all working as it should.

 

Go out of dogfight mode (doesnt matter if back in nav mode, or A-A mode or into missile override): Radar changes back into FCR mode, as it should. But range stays in 10nm.

 

Shouldnt the range switch back to 40nm, or whatever was used previously set up?

 

What i read about the master modes of the viper, every master mode should have its own settings. Like i could set different radar ranges for the different master modes and quickly switch between them.

 

I tested this further and it seems that no master mode saves the displayed radar range. If i set the radar from the defaul 40 to 80nm in Nav mode, it carries over to every other master mode. Except for Dogfight, which then overrides it with 10nm. Switching to any other master mode just uses the radar range from the previous mode, which is the only 10nm.

 

I am no expert, but from what i read my understanding is that a pilot can set up every master mode individually. Forcing the radar range down to 10nm after using dogfight mode seems counterintuitive to the "set up each master mode individualy"-approach.

 

Thank you

[BIGNEWY]

Hi,

 

welcome to the forum.

 

We do already have this reported, dogfight settings are not saved, as early access progresses we will be addressing these issues. 

 

Thank you