MickyG

I think I can send those files to you Arcc ? Is that okay @BIGNEWY? (because of rights of those files)

Dear Christian, The icon files are stored in the DCS folder in C:\Program Files\Eagle Dynamics\DCS World\DemoMods\aircraft. The Icon files for those modules were removed by Eagle Dynamics since the last update. Luckily I had a backup from my drive with the previous version of DCS with those Icon files and I copied them to my actual DCS folder. That solved it and the icons show up now like before.

Problem is solved. (Have a look at this topic in winwing) Icons were removed by DCS since the last update. Luckily I still had them in a backup and copied them to my actual installation.

Well as I said I own those modules and have them installed. Just found the icons and Copied them to my actual installation. problem solved. thanks!!

@BIGNEWY I own all those modules and they are installed. Still not showing up in SimappPro. What is a solution to solve this? below the screenshots before and after the last DCS update: also DCS.log: === Log opened UTC 2025-07-28 11:37:36 2025-07-28 11:37:37.636 INFO EDCORE (Main): Platform Timer Resolution: 15.44ms 2025-07-28 11:37:38.112 INFO EDCORE (Main): Created boot pool: n:16 2025-07-28 11:37:38.113 INFO APP (Main): Command line: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin/DCS.exe" 2025-07-28 11:37:38.113 INFO APP (Main): DCS/2.9.18.12722 (x86_64; MT; Windows NT 10.0.22631) 2025-07-28 11:37:38.113 INFO APP (Main): Application revision: 252722 2025-07-28 11:37:38.113 INFO APP (Main): Renderer revision: 26305 2025-07-28 11:37:38.113 INFO APP (Main): Terrain revision: 26363 2025-07-28 11:37:38.113 INFO APP (Main): Build number: 364 2025-07-28 11:37:38.113 INFO APP (Main): CPU cores: 24, threads: 32, System RAM: 130902 MB, Pagefile: 8192 MB 2025-07-28 11:37:38.113 INFO APP (Main): CPU info: system affinity mask: 11111111111111111111111111111111 process affinity mask: 1111111111111111 CPU: Intel(R) Core(TM) i9-14900KF [1x L3 caches] CPU has uniform cache size 36 MB (per cache) all CPU cores have the same efficiency class 1 CPU cores have different performance classes: [1-2] logical cores with performance class 2: {8, 9, 10, 11} logical cores with performance class 1: {0, 1, 2, 3, 4, 5, 6, 7, 12, 13, 14, 15} common cores: {4, 5, 6, 7, 12, 13, 14, 15} render cores: {8, 9, 10, 11, 0, 1, 2, 3} IO cores: {} unavailable cores: {16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31} pause10: 0.029546 us (std dev: 0.023914) pause10: 932 cycles (std dev: 654.3) 2025-07-28 11:37:38.132 WARNING APP (Main): ProcessLasso is running 2025-07-28 11:37:38.267 INFO EDCORE (Main): Loaded C:/Program Files/Eagle Dynamics/DCS World OpenBeta/bin/edWebViewBrowser.dll 2025-07-28 11:37:39.969 INFO ASYNCNET (5652): Login success. 2025-07-28 11:37:44.385 ERROR ASYNCNET (Main): HTTP request dcs:authdata failed with error 99: Unrecoverable error in select/poll 2025-07-28 11:37:44.385 ERROR ASYNCNET (Main): Auth failed with code -99. === Log closed. null

I just noticed that the plane Icons in SimmappPro under "Game Peripheral Display" /MFD for M-2000C, AV8BNR, F-15E and F-15E_WSO disappeared and are replaced by placeholders. I just found out that after setting back my backup everthing is okay, but then after updating DCS the icons disappeared again!? So that problem is related to DCS and hopefully a bug that is gonna be fixed by DCS. So Please fix this DCS, I really don't like it with those placeholders.

I just found out that after setting back my backup everthing is okay, but then after updating DCS the icons disappeared again!? So that problem is related to DCS and hopefully a bug that is gonna be fixed by DCS.

I just noticed that the plane Icons in SimmappPro under "Game Peripheral Display" /MFD for M-2000C, AV8BNR, F-15E and F-15E_WSO disappeared and are replaced by placeholders. Why is this? Is it a bug? I really don't like this, please let me know how to fix this! (I suppose it has something to do with the RazBam issue? But I still want this fixed!)

I solved this issue on my side. problem started after flashing my motherboard bios to the latest version. (I remembered everything worked fine the day before) after flashing it back to the previous version everything went back to normal. no more long closing times for DCS and microstutter disappeared.

same "problem" here.

Thanks LucShep!

as the title already says, I am looking for user experiences with the rtx 5090. What is the gain/advantage compared to a 4090? Thanks in advance for your help and reply.

thanks so much!

I see a lot of comments stating that the release is in to weeks? is this true? I Can't find it anywhere on the site or in the forums. apart from that I will buy it anyway.

thanks for your answer.

"Is there an option to turn the LED's Back on on the Throttle with a Button inside DCS when using a plane that is not supported or when it's not needed to have them turned off? I would like such an option." is there any progress with this?

Is there a way to prevent DCS changing the resolution to 4096x1440 with winwing mfd's? when I'm using VR or set the resolution automatically to 2560 when using VR? I want to keep it at 2560 when using VR because of performance reasons and it messes up when using my quest and I can't access certain screen areas in VR when set to 4096. in other words: is it possible to set the resolution to 2560 automatically when playing in VR?

yes, of course! Here it is: it seems to work now but the console output is a lot larger now and I don't know if it is ok like this? (because of all those "cannot be found" issues) Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" TMHotasLEDSync v1.0.9 Physical USB HID devices managed by script! Currently plugged USB HID devices[3]: 1: "AVA [R] Viper" - "USB\VID_044F&PID_0430&REV_0200&MI_00" 2: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200" 3: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" Installing filter driver to VID_044F&PID_0404. Please Wait...Done! USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&218EB820&0&1) selected Installing filter driver to VID_044F&PID_0412. Please Wait...Done! USB HID device "Viper TQS"(USB\VID_044F&PID_0412\2055385B4633) selected USB HID device with hardware id "VID_044F&PID_0413" cannot be found USB HID device with hardware id "VID_044F&PID_0416" cannot be found USB HID device with hardware id "VID_044F&PID_0417" cannot be found USB HID device with hardware id "VID_044F&PID_0438" cannot be found USB HID device with hardware id "VID_044F&PID_0439" cannot be found USB HID device with hardware id "VID_044F&PID_0432" cannot be found USB HID device with hardware id "VID_044F&PID_043A" cannot be found USB HID device with hardware id "VID_044F&PID_0420" cannot be found USB HID device with hardware id "VID_044F&PID_0428" cannot be found USB HID device with hardware id "VID_044F&PID_0421" cannot be found USB HID device with hardware id "VID_044F&PID_0429" cannot be found USB HID device with hardware id "VID_044F&PID_0422" cannot be found USB HID device with hardware id "VID_044F&PID_042A" cannot be found USB HID device with hardware id "VID_044F&PID_041B" cannot be found USB HID device with hardware id "VID_044F&PID_041C" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined Connecting virtual keyboard...Done Connecting virtual mouse (absolute axes)...Done Server socket listening on TCP port 29914 main returned 0

Hi Slug, Is there an option to turn the LED's Back on on the Throttle with a Button inside DCS when using a plane that is not supported or when it's not needed to have them turned off? I would like such an option. BTW: I get an error when using TARGET Ver. v3.0.25.127_rev1? When using TARGET v3.0.24.618_rev1 everything works just fine. Any Idea why this happens? Thanks in advance for your help.

same problem here! what is going on?

Hi! thanks for your answer! Yes they work just fine after changing it back. that's the issue, they work fine at 2560. the reason I asked was my concern it would cost some performance and cause more load when set to 4096. BTW I don't exactly understand what you mean with the last part of your answer.

Hi, As the title already says DCS keeps changing the resolution on every new start with winwing mfd's from 2560x1440 to 4096x1440. (in 2d and also in VR) I suppose this is caused because of the attached mfd's. Is there a way to avoid this? Now I have to change it back manually and restart which is very annoying. thanks in advance for any help with this issue. anyone having the same issue?

I will do that tomorrow for you. Will contact you.

I don’t know if I have an original installer for that version somewhere, have to look for it then. I deleted the directory of that newer version and copied the one from my backup back. I could zip those files and send them for you? Just let me know what you want.

Maybe I can help you out? Or you could ask their support for an older version?