Jump to content

DCS & Pimax Crystal Light Constant Freezing and Crashing


Go to solution Solved by pimp,

Recommended Posts

Posted (edited)

Hi All,

I just recently received my PCL and unfortunately, for me I am having a hard time getting it to work with DCS. After days of figuring out how to get the PCL to connect with the latest PimaxPlay software(ver 1.35.01.01), I cannot play DCS for more than 2 minutes before it CTD. Sometimes it crashes as soon as the aircraft loads. This does not happen in 2D. I've sent many DCS logs via the auto bug report option and performed a slow repair. All of my drivers are up to date on my Windows 11 machine. Please help me figure this out. When it works I'm satisfied with the PCL, but this has not been a good first impression at all. So I may have to return it. Please let me know what other info is needed to help resolve this issue.


Thanks in advance!!!

Screenshot 2024-12-10 211852.png

 

Screenshot 2024-12-10 211924.png

 

Screenshot 2024-12-10 211953.png

 

Screenshot 2024-12-10 212019.png

 

Screenshot 2024-12-11 205504.png

my-pimax.zip my-pimax1.zip my-pimaxclient.zip my-pimaxota.zip my-steamvr.zip dcs.log

Edited by pimp

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted

Have you checked all your USBs and HID in device manager to check that Windows is not switching power off to the USB? 
 

Often happens after a Windows update and the first thing I check if a problem arises. HTH 

Ryzen 9800X3D, MSI  RTX 4090, 2 TB SSD, 64GB 5200 MHZ DDR5 RAM, MSI 670E Motherboard, Pimax Crystal. Buttkicker Plus, WINWING Rudder Pedals & F16EX Throttle: FSSB-R3-MKII ULTRA Base/TMWH Joystick: DCS: F16C. 

Posted
45 minutes ago, Nuggetz said:

Have you checked all your USBs and HID in device manager to check that Windows is not switching power off to the USB? 
 

Often happens after a Windows update and the first thing I check if a problem arises. HTH 

Thanks for your reply. There were quite a few HIDs still checked so I unchecked them and retested, but as soon as I loaded into the Apache a CTD occurred.

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted (edited)

What's DCS's Pixel Density set at? In my testing I found Pimax' render setting to give a superior image quality. So, Pimax at 2.0 (or 1.5/1.0, given your GPU) and DCS PD at 0.5.

If that doesn't fix it you need to rule out graphics as a cause by going full potato in the graphics settings, everything to lowest possible. 

Then cross your fingers when you test it.

Have you successfully run the PCL in any other VR games?

Edited by Panzerlang
Posted

Thanks for your reply. I am unsure where that Pimax image quality setting is located but DCS PD setting is set 1. Also, I do not play any other game besides DCS. I will try to lower my DCS gfx settings and retest report back later.

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted
6 hours ago, pimp said:

Thanks for your reply. I am unsure where that Pimax image quality setting is located but DCS PD setting is set 1. Also, I do not play any other game besides DCS. I will try to lower my DCS gfx settings and retest report back later.

It's there. 🙂

pimax render.jpg

Posted

Oh duh. 🙂 I'll try 1.0 and retest. Thanks again.

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted
44 minutes ago, pimp said:

Oh duh. 🙂 I'll try 1.0 and retest. Thanks again.

Just to clarify, the Pimax render setting and DCS Pixel Density setting are interchangeable. You can mix them together (don't know of any reason to do that though) but as already mentioned, I find the Pimax option gives a better image quality (text in the cockpit is clearer for the most visible example). Pimax at max, DCS at min.

Posted

The initial PD change did not work. DCS crashed as soon as I was in the aircraft. So I set the DCS gfx settings to the Low preset and was able to fly longer. So I put all my settings back but turned off MSAA and Rain Droplets. In multiple tests, I was able to fly longer and I thought I figured out the issue but I had another crash in a longer flight. Log file attached. Playing on Low preset is not an option.

dcs.log

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted (edited)

Which Pimax Play version do you have? If you don't already have this, try it out and run OpenXR from it (it gives extra settings in the Device Windows).

How to use Pimax OpenXR

Note: I find the native Pimax OpenXR to be a little better than the external one. You don't need to disable the external one, Pimax takes over. But if you go back to the external one it seems you need to reboot your PC after switching back before it'll run properly again (for me anyway, ymmv).

Also this, so you can see what API layers you have running etc.

GitHub - fredemmott/OpenXR-API-Layers-GUI: UI for managing OpenXR API layers

Edited by Panzerlang
Posted (edited)

Also, use this to at least see if your headset works with something else. If this crashes too it's either your OpenXR is jankey (this is SteamVR) or your headset is fubar.

Aircar on Steam

 

You'll need SteamVR of course, it's free on Steam.

Edited by Panzerlang
Posted

I have the same problem with the Crystal Light. I had it in 90Hz upscale mode. I just tried 72Hz and it seems to be working fine for now, at least on short sessions. If you try it out let me know how it goes.

  • Thanks 1
Posted (edited)
17 hours ago, ChuckyChuck said:

I have the same problem with the Crystal Light. I had it in 90Hz upscale mode. I just tried 72Hz and it seems to be working fine for now, at least on short sessions. If you try it out let me know how it goes.

Thanks for your reply. Unfortunately for me this did not work. It CTD as soon as I loaded into the Apache and took off. There was an Pimax Play update that I was hoping would fix my issue but it did not. I also tried the Low preset again and I was able to fly a little over 5 minutes before it CTD with no crash log prompt.

Edited by pimp

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted
2 hours ago, Flappie said:

Hi @pimp. What does CTD? DCS or the Pimax software?

If it's DCS, please attach the latest zip file from Saved Games/DCS.../Logs.

Hi @Flappie, Crash To Desktop(CTD). Sometimes DCS crashes to desktop without the crash log report prompt and sometimes it crashes where I am able to send the crash report to ED. The Pimax software is still running after DCS crashes.

dcs.log-20241212-035429.zip

  • Thanks 1

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted

Thank you. You have the dreaded "DX device removed" error. It means that your GPU was not able to answer DCS requests. This is was caused DCS to crash.

Now, we must find what happens with your GPU. You can try all solutions listed here, one by one:

 

2024-12-12 03:47:36.974 INFO    Dispatcher (Main): loadMission Done: Control passed to the player
2024-12-12 03:47:37.032 WARNING SCENERENDERER (14412): render graph: forced to update texture desc of already created texture on the same frame (0)
2024-12-12 03:47:37.034 WARNING LOG (3000): 1 duplicate message(s) skipped.
2024-12-12 03:47:37.034 INFO    EDTERRAINGRAPHICS41 (14412): instancer factors has been changed. Update lod buffers.
2024-12-12 03:47:37.034 INFO    EDTERRAINGRAPHICS41 (14412): 	 distanceFactor = 1.000000
2024-12-12 03:47:37.034 INFO    EDTERRAINGRAPHICS41 (14412): 	 instancerDetailsFactor = 1.000000
2024-12-12 03:47:37.034 INFO    EDTERRAINGRAPHICS41 (14412): 	 forestDistanceFactor = 0.700000
2024-12-12 03:47:37.034 INFO    EDTERRAINGRAPHICS41 (14412): 	 forestDetailsFactor = 1.000000
2024-12-12 03:47:37.769 ERROR_ONCE DX11BACKEND (7140): texture 'uh1_tail_spec' not found. Asked from ''
2024-12-12 03:47:40.748 WARNING BACKENDCOMMON (8172): Need to reprocess [DDS] image '/textures/AH-64D_inside_D_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2024-12-12 03:47:45.316 WARNING BACKENDCOMMON (8172): Need to reprocess [DDS] image '/textures/ah64_pilot_seat_all_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2024-12-12 03:48:08.416 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-12-12 03:48:09.895 WARNING LOG (3000): 2 duplicate message(s) skipped.
2024-12-12 03:48:09.895 ERROR_ONCE DX11BACKEND (7140): texture 'VRTooltip' not found. Asked from ''
2024-12-12 03:48:10.204 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-12-12 03:53:05.674 WARNING LOG (3000): 156 duplicate message(s) skipped.
2024-12-12 03:53:05.674 ERROR_ONCE DX11BACKEND (16008): texture 'breakingwaves_deadlock.tif' not found. Asked from ''
2024-12-12 03:53:05.674 ERROR_ONCE DX11BACKEND (16008): texture 'breakingwaves.tif' not found. Asked from ''
2024-12-12 03:53:05.846 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-12-12 03:54:27.360 WARNING LOG (3000): 55 duplicate message(s) skipped.
2024-12-12 03:54:27.360 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2024-12-12 03:54:28.787 WARNING LOG (3000): 1 duplicate message(s) skipped.
2024-12-12 03:54:28.787 ERROR   VISUALIZER (14412): xrEndFrame failed with error: XR_ERROR_RUNTIME_FAILURE
2024-12-12 03:54:28.787 ERROR   DX11BACKEND (14412): DX device removed. Reason: 0x887A0006
2024-12-12 03:54:28.788 ERROR   DX11BACKEND (10552): Failed assert `false && "failed to create texture"` at Projects\render\dx11backend_win8\Source\DX11TextureManager.cpp:761
2024-12-12 03:54:28.788 INFO    EDCORE (10552): try to write dump information
2024-12-12 03:54:28.790 INFO    EDCORE (10552): # -------------- 20241212-035429 --------------
2024-12-12 03:54:28.791 INFO    EDCORE (10552): DCS/2.9.10.3948 (x86_64; MT; Windows NT 10.0.26100)
2024-12-12 03:54:28.792 INFO    EDCORE (10552): C:\Program Files\Eagle Dynamics\DCS World\bin\GraphicsCore.dll
2024-12-12 03:54:28.793 INFO    EDCORE (10552): # C0000005 ACCESS_VIOLATION at 00007ff8eaf90f92 00:00000000
2024-12-12 03:54:28.794 INFO    EDCORE (10552): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World\bin;', symOptions: 532, UserName: 'genea'
2024-12-12 03:54:28.795 INFO    EDCORE (10552): OS-Version: 10.0.26100 () 0x100-0x1
2024-12-12 03:54:28.796 INFO    EDCORE (10552): 0x0000000000060f92 (GraphicsCore): render::RenderGraph::reset + 0x2352
2024-12-12 03:54:28.798 INFO    EDCORE (10552): 0x0000000000057b24 (GraphicsCore): render::RenderGraph::createRenderablesCollection + 0x8B4
2024-12-12 03:54:28.798 INFO    EDCORE (10552): 0x0000000000054956 (GraphicsCore): render::RenderGraph::bakeGraph + 0x1D6
2024-12-12 03:54:28.798 INFO    EDCORE (10552): 0x000000000001e894 (SceneRenderer): DCSSceneRenderer::bakeRenderGraph + 0x34
2024-12-12 03:54:28.798 INFO    EDCORE (10552): 0x0000000000156385 (Visualizer): smCamera_Implement::getClipRegion + 0x1E565
2024-12-12 03:54:28.798 INFO    EDCORE (10552): 0x0000000000047a89 (edCore): ed::SyncTaskQueue::push_task + 0x14449
2024-12-12 03:54:28.799 INFO    EDCORE (10552): 0x0000000000046f87 (edCore): ed::SyncTaskQueue::push_task + 0x13947
2024-12-12 03:54:28.799 INFO    EDCORE (10552): 0x0000000000048833 (edCore): ed::SyncTaskQueue::push_task + 0x151F3
2024-12-12 03:54:28.799 INFO    EDCORE (10552): 0x00000000000323b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2024-12-12 03:54:28.799 INFO    EDCORE (10552): 0x0000000000014ea0 (ucrtbase): wcsrchr + 0x1F0
2024-12-12 03:54:28.799 INFO    EDCORE (10552): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17
2024-12-12 03:54:28.929 INFO    EDCORE (10552): Minidump created.

 

  • Like 2

---

Posted
7 minutes ago, Flappie said:

Thank you. You have the dreaded "DX device removed" error. It means that your GPU was not able to answer DCS requests. This is was caused DCS to crash.

Now, we must find what happens with your GPU. You can try all solutions listed here, one by one:

 

Thank you @Flappie. I will try these as soon as possible and report back.

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted (edited)

Hi @Flappie, I reset my bios but I still received a crash but with a report. I do not see a DX error in this one. Is there anything you can see with your expertise? In the meantime, I'll continue with the other steps. Please see log zip attached.

dcs.log-20241215-062548.zip

Edited by pimp

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted

Some messages linked to the Apache caught my attention, so I checked if I had the same messages, and I do. This means they are not the source of your issue:

My log:

2024-12-15 10:38:42.477 INFO    EDTERRAINGRAPHICS41 (16188): instancer factors has been changed. Update lod buffers.
2024-12-15 10:38:42.477 INFO    EDTERRAINGRAPHICS41 (16188): 	 distanceFactor = 1.200000
2024-12-15 10:38:42.477 INFO    EDTERRAINGRAPHICS41 (16188): 	 instancerDetailsFactor = 0.833333
2024-12-15 10:38:42.477 INFO    EDTERRAINGRAPHICS41 (16188): 	 forestDistanceFactor = 1.000000
2024-12-15 10:38:42.477 INFO    EDTERRAINGRAPHICS41 (16188): 	 forestDetailsFactor = 0.833333
2024-12-15 10:38:42.566 ERROR_ONCE DX11BACKEND (10776): texture 'f15_wing_l_spec' not found. Asked from ''
2024-12-15 10:38:44.183 WARNING BACKENDCOMMON (332): Need to reprocess [DDS] image '/textures/AH-64D_inside_D_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2024-12-15 10:38:45.726 ERROR_ONCE DX11BACKEND (11924): texture 'mi_8_tex_spec' not found. Asked from ''
2024-12-15 10:38:47.605 WARNING BACKENDCOMMON (11924): Need to reprocess [DDS] image '/textures/ah64_pilot_seat_all_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2024-12-15 10:38:49.599 WARNING BACKENDCOMMON (10776): Need to reprocess [DDS] image '/textures/AH-64D_inside_D_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2024-12-15 10:38:57.086 INFO    VISUALIZER (Main): Preload() finished
2024-12-15 10:38:57.537 INFO    Dispatcher (Main): precache units resources in slots
2024-12-15 10:38:57.849 INFO    EDCORE (Main): Created game pool: h:2 n:5 l:2
2024-12-15 10:38:57.849 INFO    Dispatcher (Main): loadMission Done: Control passed to the player
2024-12-15 10:38:57.974 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440]
2024-12-15 10:38:58.068 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2024-12-15 10:38:58.848 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440]
2024-12-15 10:39:00.267 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2024-12-15 10:39:01.048 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440]
2024-12-15 10:39:01.662 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2024-12-15 10:39:01.682 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME

Your log:

2024-12-15 06:23:25.872 INFO    EDTERRAINGRAPHICS41 (10312): instancer factors has been changed. Update lod buffers.
2024-12-15 06:23:25.872 INFO    EDTERRAINGRAPHICS41 (10312): 	 distanceFactor = 1.000000
2024-12-15 06:23:25.872 INFO    EDTERRAINGRAPHICS41 (10312): 	 instancerDetailsFactor = 1.000000
2024-12-15 06:23:25.872 INFO    EDTERRAINGRAPHICS41 (10312): 	 forestDistanceFactor = 0.650000
2024-12-15 06:23:25.872 INFO    EDTERRAINGRAPHICS41 (10312): 	 forestDetailsFactor = 1.000000
2024-12-15 06:23:28.137 WARNING BACKENDCOMMON (15532): Need to reprocess [DDS] image '/textures/AH-64D_inside_D_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2024-12-15 06:23:30.457 ERROR_ONCE DX11BACKEND (15532): texture 'uh1_tail_spec' not found. Asked from ''
2024-12-15 06:23:30.850 WARNING BACKENDCOMMON (4696): Need to reprocess [DDS] image '/textures/ah64_pilot_seat_all_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2024-12-15 06:23:32.641 WARNING BACKENDCOMMON (18480): Need to reprocess [DDS] image '/textures/AH-64D_inside_D_Normal.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2024-12-15 06:23:52.314 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-12-15 06:23:55.109 WARNING LOG (22224): 3 duplicate message(s) skipped.
2024-12-15 06:23:55.109 INFO    DX11BACKEND (10312): Compile shader: enlight/raycursor.fx:DIRECTX11=true;MSAA=2;USE_DCS_DEFERRED=1;
2024-12-15 06:23:55.129 ALERT   DX11BACKEND (10312): Error: Can't find precompiled shader for effect enlight/raycursor.fx:DIRECTX11=true;MSAA=2;USE_DCS_DEFERRED=1;.
Recompilation process will take some time, please wait
(this situation should not occur on end user PC, if there is no manual shader editing)
2024-12-15 06:23:55.258 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-12-15 06:23:58.345 ERROR_ONCE DX11BACKEND (18480): texture 'VRTooltip' not found. Asked from ''
2024-12-15 06:24:07.465 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-12-15 06:24:36.429 WARNING LOG (22224): 39 duplicate message(s) skipped.
2024-12-15 06:24:36.429 ERROR_ONCE DX11BACKEND (15532): texture 'kabinaNight' not found. Asked from ''
2024-12-15 06:24:36.867 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-12-15 06:25:47.384 WARNING LOG (22224): 61 duplicate message(s) skipped.
2024-12-15 06:25:47.384 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2024-12-15 06:25:47.385 ERROR   DX11BACKEND (4132): Failed assert `false && "failed to create texture"` at Projects\render\dx11backend_win8\Source\DX11TextureManager.cpp:761
2024-12-15 06:25:47.385 INFO    EDCORE (4132): try to write dump information
2024-12-15 06:25:47.387 INFO    EDCORE (4132): # -------------- 20241215-062548 --------------
2024-12-15 06:25:47.388 INFO    EDCORE (4132): DCS/2.9.10.4160 (x86_64; MT; Windows NT 10.0.26100)
2024-12-15 06:25:47.390 INFO    EDCORE (4132): C:\Program Files\Eagle Dynamics\DCS World\bin\GraphicsCore.dll
2024-12-15 06:25:47.391 INFO    EDCORE (4132): # C0000005 ACCESS_VIOLATION at 00007ffd2b230f92 00:00000000
2024-12-15 06:25:47.392 INFO    EDCORE (4132): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World\bin;', symOptions: 532, UserName: 'genea'
2024-12-15 06:25:47.393 INFO    EDCORE (4132): OS-Version: 10.0.26100 () 0x100-0x1
2024-12-15 06:25:47.395 INFO    EDCORE (4132): 0x0000000000060f92 (GraphicsCore): render::RenderGraph::reset + 0x2352

 

I believe the "ANTIFREEZE ENABLED" is met when DCS detects the PC has a hard time answering its requests. But this does not help us much.

Another Pimax Crystal user ran into a similar crash issue a few weeks ago. He fixed this after he reinstalled both PimaxPlay and the NVIDIA driver. You should give it a go if you haven't already:

 

---

Posted (edited)

Hi @Flappie, so I uninstalled my gfx drivers using DDU and installed the latest version 566.36. Also, uninstalled and reinstalled PimaxPlay's latest client version. I restarted after each install just in case. I was able to fly for about 6 minutes before DCS crashed. New logs are attached. Any idea when this post is going to be moved to the appropriate thread?

dcs.log-20241215-164511.zip

Edited by pimp

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted (edited)
On 12/15/2024 at 5:56 PM, pimp said:

Any idea when this post is going to be moved to the appropriate thread?

It's my fault, I forgot to ask a moderator. It will be done tomorrow. 👍

I see your log says VMP is active:

2024-12-15 16:34:22.377 WARNING EDCORE (Main): hypervisor is active

If you have no use for it, you can disable it. You can follow this guide: https://support.microsoft.com/en-us/windows/options-to-optimize-gaming-performance-in-windows-11-a255f612-2949-4373-a566-ff6f3f474613

I also see you are using Process Lasso. I know there was a lot of core issues with MT back then, but this issue was fixed some time ago. Therefore I would recommend not using Process Lasso with DCS anymore:

2024-12-15 16:34:24.677 WARNING APP (Main): ProcessLasso is running
Edited by Flappie

---

  • Solution
Posted

Hi @Flappie,

I've been busy but I have been testing. For the last few days I have been able to figure out the issue. If I enable the "Lock to Half Framerate" option in Pimax Play DCS runs perfectly. In fact, it's more smoother locked at 45. The debugger shows I'm CPU Bound in red and my frametimes graph is much more stable. Not spiking all over the place. Not sure why I need this setting but it could be a combo of Windows 11, DCS, & Pimax issue. Hopefully all those bug reports I submitted to ED can help the devs.

 

Screenshot 2024-12-21 154004.png

 

Previously, I did disable Process Lasso, but that did not work. Now I have disabled it since it does not look like I need it any longer. Also, you mentioned the logs showed my VPM was active but I did not see that in my Windows Features.

Screenshot 2024-12-16 230014.png

 

Regardless, I'm glad I finally figured this out. Thank you for your time and effort in helping me get to this solution.

i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz

EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT  | HOTAS Warthog | Saitek Flight Pedals

Posted (edited)

I'm glad you found a solution. Thank you for sharing it. 👍

In case you'd want to go to the bottom of the "the hypervisor is active" message, you can try this procedure from Microsoft to confirm what DCS detects:

Quote

 

To determine whether the Hyper-V hypervisor is running, follow these steps:

  1. In the search box, type msinfo32.exe.

  2. Select System Information.

  3. In the detail window, locate the following entry:

    A hypervisor has been detected. Features required for Hyper-V will not be displayed.

 

From what I'm reading, the solution could be to turn off Memory Integrity, as indicated in my previous link, here. This feature is supposed to add some security. It's off on my PC.

This video shows it can lower performance in games. I wanted to test this but I can't: Window tells me that I can't turn on Memory Integrity.

Edited by Flappie

---

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...