ILS Conflicts In Viper

[Whippet41]

Just in case the Dev Team is unaware of the conflicts with the ILS beacons for the CW Map.  I've noticed that when on the Ramp at Hahn AB the Spandehlem ILS Localizer is received (108.10) as this is the default Freq for the Viper on initial startup.  In troubleshooting, this also occurs for Air Starts between Hahn and Frankfurt.  This also occur if the Bitburg ILS (111.90) is tuned.  My guess is the localization radio is set for a wide area transmission rather than a localized beam signal.  

Currently, Hahn's ILS is programmed to 112.30 for Rwy 03 and 112.00 for Rwy 21.  These are invalid ILS system radio frequencies. The ILS system typically operates between 108 to 111.95 in 5 Mhz increments. In fairness, I'm not familiar with Eastern Block Aircraft where the frequency range may be different.  

I'm not sure if this is a Map issue or a F-16C module issue.  I have asked others about this occurrence and received the same results.

[grim_reaper68]

Hi take a look here,  I've made some correction of the original file. Tested with F-16, A-10CII and Mirage F1. Any bug or information for more accuracy welcome.

Hope it will help you. But as told in the related post, DON'T FORGET TO BACKUP THE ORIGINAL FILE!

 

[Whippet41]

On 9/4/2025 at 3:18 PM, grim_reaper68 said:

Hi take a look here,  I've made some correction of the original file. Tested with F-16, A-10CII and Mirage F1. Any bug or information for more accuracy welcome.

Hope it will help you. But as told in the related post, DON'T FORGET TO BACKUP THE ORIGINAL FILE!

 

Thanks,