App crashes when connecting via remote desktop
digitalfrost84 opened this issue · 3 comments
I often use my PC via remote desktop. Tarkov settings crashes when I connect. Event log shows this error:
Faulting application name: tarkov-settings.exe, version: 1.2.0.0, time stamp: 0xdb91a93d Faulting module name: KERNELBASE.dll, version: 10.0.19041.1110, time stamp: 0x4809adf2 Exception code: 0xc000041d Fault offset: 0x0000000000034ed9 Faulting process id: 0x2620 Faulting application start time: 0x01d7915502c8fda2 Faulting application path: C:\Users\frost\Apps\tarkov-settings.1.2.0\tarkov-settings.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: ca26e899-1993-4abd-8ad4-686d26f736ce Faulting package full name: Faulting package-relative application ID:
Also:
Application: tarkov-settings.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: NvAPIWrapper.Native.Exceptions.NVIDIAApiException
at NvAPIWrapper.Native.DisplayApi.SetDVCLevel(NvAPIWrapper.Native.Display.Structures.DisplayHandle, Int32)
at tarkov_settings.GPU.NVIDIA.set_Saturation(Int32)
at tarkov_settings.ColorController.ResetDVL()
at tarkov_settings.ProcessMonitor.WinEventProc(IntPtr, UInt32, IntPtr, Int32, Int32, UInt32, UInt32)
I think something went wrong with handling display when modify saturation value.
Sorry to say but I can't help you.
First, This app isn't written for remote desktop environment. (i.e. RDP, parsec, etc.)
Second, Too many things should be considered and tested for remote gaming environment. And that's out of my ability.
I understand that. I don't want it to work with RDP. I just want it not to crash when opening the session so that I don't have to restart it manually later.
It would be sufficient if the tool could detect an RDP session and simply do nothing in this case.
The display ID is \.\DISPLAY129 in my case, adapter name "Microsoft Remote Display Adapter" and the device id is "RdpIdd_IndirectDisplay".
You could simply catch this exception and then test if the adapter name matches for example.
Well, I should look into it. Time to write some try and catch statements.