SWPixivyle

I had a CTD yesterday after trying to input a dot alone (".") into the radios via the UFC. Log and video with reproduction attached. dcs.log-20230730-114143.zip

idk if i'm the only one who has this issue, but after a fresh update to 2.8.7.42583 and mod installation i can't play anymore. i get an error upon starting the game and i don't get past the splash screen. i think it happens with more files, not just the one in the attached image.

As someone who flies aircraft with mirrors and multi-function displays such as the F/A-18, AV-8B, and soon the F-15E, I would like to suggest something. In the settings, you have "Res. of Cockpit Displays", which controls the resolution of the MFDs' image quality and cockpit mirrors. Personally, even though it decreases performance, I like to use my mirrors, but if I want to reduce the MFD resolution to have a more realistic LITENING image, my mirrors will also have their resolution halved. Since it's something simple and the F-15E is very close, I think it'd be a good idea to make a setting "Res. of Cockpit Mirrors" and change "Res. of Cockpit Displays" to only affect the MFDs.

now that i think of it 2000s is way too late yeah, and i'm not surprised things don't match with this particular module due to it being low fidelity. agreed on the radar thing too

I don't have a lot of knowledge regarding the Eagle, and I was curious about the age of our F-15C. I didn't see it in the documentation. Considering the age of the module itself and what it looks like I'd assume early 2000s. If someone knows, I'd like to read it.

here, i was going to post it but i just forgot. dcs.log-20220519-203637.zip

Me and another DCS player have noticed that several HARM targets appear as U for Unknown in the HARM WPN page, when they should be recognised with their associated RWR designation. Some have been in Unknown for a while and we're not sure if that's intentional, but the SA-5 Gammon and its Tin Shield radar are two that could be incorrectly designated, as not only do they have their own RWR designation, they used to appear with it (5 and TS respectively) before the latest update. Here is a list of all the radars we found to not have their RWR designated in the HARM WPN page: 126 2 SA2 127 7 HQ7 129 5 SA5 407 40 Tarawa 128 HQ HQ7 206 HK Hawk 409 MR Destroyer.... 410 HN Destroyer.... 209 NS NASAMS 408 PS Amphibious transport dock.... 411 MR Frigate... 124 RP Rapier 125 RT Rapier 403 SS CVN 71 404 SS CVN 72 405 SS CVN 73 320 SW Kuz 406 SS Stennis 413 SS Truman 130 TS SA5 I don't know if some of these are intentional, but considering the SA5 and Tin Shield used to have their RWR designation, I think maybe it was changed by accident, somehow. According to one of the users that tested this with me, it is possible to fire at the radar the introduced HARM code is associated to, but if this was changed by mistake, it'd be good to have it fixed.

In the F-16C, the game crashes when you try to enter HARM codes that do not associate to a radar. Three users tried it (including me), and the game crashed for everyone. I also tested it without third party mods and it would still crash. I tried it with a cold start and with the aircraft already in the air, still crashed. Desktop 2022.05.19 - 21.46.08.05.DVR_Trim_Trim.mp4

you could add an option to show the server name instead of the mission, since most of the times multiplayer missions look like "pve_2022_syria..." and it looks cooler to have the server's name :)