Whippet41

Unfortunately, this didn't fix the issue of receiving the ILS for Spang while sitting in a parking spot at Hahn. The file does fix the issue with the Hahn ILS frequencies.

Thanks,

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.

With the recent update the Bullseye data when enabled shows up fuzzy on the FCR and clear on the HSD. I noticed the same condition when swapping the FCR from left to the right MFD.

Hello Ugra Media Dev Team There are a number of taxi and runway lights either in the taxi way or in the middle of the entrance to the Runway. See attached as example. Perhaps this can be added to your update list.

Thanks- I was running admin for both the shortcut and the.exe file. Removing the admin property from the shortcut and DCS.EXE (bin-mt) fixed the issue.

Hello All- I have similar issues with the system freezing within the ME and systems stuttering.

Okay. Thanks for the update. Understood that its just an sound file. I also heard back from ED regarding the Comm issue. They are working an a solutions. We can consider this resolved. Thank you again.

Thanks for the reply- So I'm restarted the entire campaign. In mission 1 after the intro, previously there was a radio call from "Ashland to Track Line we're airborne" as the flight circles the airfield, then Track line would eventually come back Track Line to Ashland the bombers are airborne you can proceed to the rendezvous point. Correct, I am not referering to the Wingman control under the comm menu - just the radio calls out from Lead that you create for the mission immersion. I don't have any unofficial mods. I did run a repair (long) hoping that might resolve the issue on my end. I also hoped that yesterday's update may have fixed the issue. Please note, that I also noted to ED that the after the update and repair "Easy Communications" does not work for me. In my troubleshooting effort for the Easy Communications I removed and reinstalled the The Channel / Normandy maps. Perhaps its an issue with the P-47 Mod itself. Thanks again.

It appears that the default audio messaging in the mission are not working. Has anyone else noticed this issue or has something changed since the recent DCS update?

Perhaps you've been able to correct this issue. I had the same problem with various aircraft, trim was too sensitive in all directions. I read a post elsewhere regarding the Force feedback switch found in the misc. menu settings. By default, this is checked, I unchecked this setting and all my issue disappeared. I only bring this up now as I'm new to DCS (this year) and just found the discussion under the A-10 forum as I was having the same issue trying to figure out why the A-10 would bounce up and down/ left and right. Again, if this is resolved for you, please excuse the interruption. If not, perhaps you can give it a try. Perhaps you've been able to correct this issue. I had the same problem with various aircraft, trim was too sensitive in all directions for the P-47/A-10/Spitfire. I read a post elsewhere regarding the Force feedback switch found in the misc. menu settings. By default, this is checked, apparently, this is active regardless of whether a force feedback device is attached. I unchecked this setting and all my issue disappeared. I only bring this up now as I'm new to DCS (this year) and just found the discussion under the A-10 forum as I was having the same issue trying to figure out why the A-10 would bounce up and down/ left and right. Again, if this is resolved for you, please excuse the interruption. If not, perhaps you can give it a try.

Hello All- David here (Whippet41). I live on the east coast of Florida. I'm somewhat new to DCS. I've been working on the P-47D and the 56th Fighter Group Campaigns. My Dad flew with the 56th Fighter Group out of Boxted, England from August '44 till the end of WWII. I was assigned to the 56th Fighter Group 61st Sq when it was at MacDill AFB, hence the patch. At that time the Sq was converting from F-4's to the F-16. Typically, fly in mornings to mid-afternoons. I also explore MSFS 2020 and the PMDG 737. Currently, working with the A-10C platform learning the basic systems. Next steps will be to learn more about mission planning and exploring the multi-player arena. Out...