MickyG

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.