dutchili

Things seem better with NVidia driver 576.66 (no need to blame mod's that are known good)

I experience the same thing with Nvidia 576.52. After the latest DCS patch...it's a matter of time, you just don't know how much time. No crash in DCS log, app hangs. When the app is windowed (while playing VR), i can usually sit it out and get control over windows in a few minutes. In full screen mode....automatic reboot (no BSOD).

no stutters, but crashes that are not mentioned in the dcs.log. Here is an example. After about 20 minutes of flying, the video froze, sound continued for a minute, then a full system reboot. Not an incident. dcs.log DxDiag.txt

Major component: SRS for radio communications in Multi-Player. Major component: Tacview for debriefing in both MP and SP Major component: LotATC for air traffic control in MP My discord uses several mods to enhance the visual experience at airfields and target area's.

I bought a Pixel Crystal Light... - i love the resolution, close to 2D experience - switching between game and 'desktop' is instant - sound of non-DMAS speakers is....better buy the DMAS speakers too - tracking is not as good as the quest. I have issues when looking at my F-16 wingtips. Could be due to my background. Besides this position, it is perfect and better 'smoothened' than the quest, which you will notice when aligning the JHMCS in the Viper. - quality upon delivery was not perfect. Had to correct contrast and brightness of the individual panels, throught the normal software, to balance left and right. One dead pixel in the right panel, no response from customer service on these issues for 3 workdays and a weekend. - setup was 'click and play' instead of those Quest 3 unwanted intro's and safety wizards. - wearing comfort is much better than the Quest 3. It is heavier, but feels lighter. - i get the best performance at 72Hz, quadviews FOV rendering, high(est) resolution. Low-level FPS depends on the map and visible distance setting, FL006+ is steady 72 Hz (and perceived as fluent). The 90Hz setting only works for me with Pimax upscaling enabled, but that comes at the cost of less crispy views. - the asferical lenses have a sweet spot. The pancakes from the quest have better 'edge to exge' sharpness. It took some time to learn to turn my head more, than just the eyes. Ther is also more chromatic abberation, comparable to a quest 2. Primarily visible with high contrast and red colors. Summary: not going back to the Quest 3.

@BIGNEWYThis thread can be closed. The root cause was incompatibility between the Nvidia driver (regardless the version) and Windows 11 core isolation.

DLSS is not the same as DLAA.

I have disabled core isolation. Flown more than an hour now on multiple flights (computer shutdown in between).

@sleighzyththanks for the great tips. They are in line with the advised that I got from NVIDIA. I ran lhe log analyzer on the Ed discord and installed a very old graphics driver as advised. Now I can play for about an hour and 15 minutes before I need to reboot to do it again. @BIGNEWYit does not seem to be a DCS specific issue as I get the same issues with flight simulator as soon as I enter VR

dcs.logDxDiag.txt There you go @BIGNEWY. Hope it helps

I frequently get this error message in the log file, since April 25. Currently on the latest released version, yet i still get this. I experience that the VR images freezes, the sound continuous for a while and if i am lucky DCS writes this log entry. Sometimes the PC writes a mindump, sometimes i just reboots. The minidump and eventvwr often point to nvlddmkm and i see event IDs 14 and 153 in the event log. Happens with Quest 3 and Pimax Crystal light. My friend have more crashes while loading / in multiplayer too, with various reaons. Any help @BIGNEWY

The taxi lights appear in really impractical places at Pferdsfeld. Near or on crossings.

actually, since april 25 or even before if other got updates before that.

From meta support: Greetings from Meta Store Support. We sincerely appreciate your continued patience as we work to resolve the PCVR error affecting v76. We truly apologize for the inconvenience this software update has caused and understand how frustrating this situation has been for you. As a gesture of goodwill for the time and effort you have invested in reaching out to us, we would like to offer you $10 Meta store credit to help compensate for the disruption. If you are interested in redeeming this, please provide the following account details: Full name as it appears on your Meta account Current alias/username as it appears on your Meta account Email address linked to the account This store credit can be applied toward any digital purchase within the Meta Store, including apps and games available for PCVR. In the meantime, we recommend keeping an eye out for upcoming updates on Quest headsets, as we continue working toward a resolution. You may visit this link: Meta Quest release notes to monitor future software updates. Thank you for your understanding and patience. If you have any further questions or need clarification, please feel free to reach out. We are always happy to assist you.

Which software version do you have on the headset? I have 76.1025 it still randomly disconnects with VD when playing DCS.

i just tried DCS in 2D, with the headset connected, DCS still crashed. The OVRservice log indicated it concluded the Headset was not connected, then the system hung....

Meta is requesting to send a bug report from the headset when this happens, or you cannot connect to the PC. It is only a few clicks from the Oculus Dashboard. After installing "2025-05 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5058411)" earlier tonight i played for just over 45 minutes without a crash. I came from the 24H2 preview. I will test more tomorrow. (headset firmware: v76.1025. Meta Quest Link on PTC with version 77.0.0.574.329). So far such delightfull moments have been a one-time-off-lucky-event.

Hahaha. Now go back up again and check the version in your headset too

Version number of Meta link app and firmware?

The joy was short lived...

Played for just over an hour without crashes. However, the anti-aliasing doesn't seem te be working as it used to. Jagged lines.

I have received an update tonight in the PTC channel (Beta). Version number was not updated and is still 77.0.0.574.329, however, I played for 25 minutes without a crash. Hopefully not issues after rebooting and trying again tomorrow. Headset still on 76.1025

In my case the Oculus log files, which you can retrieve by starting the OculusLogGatherer.exe in the diagnostics folder, producing output to your desktop, indicate that the USB connection is lost. When using airlink, the connection to the device is lost too. As a result all operations on the headset fail. Due to lack of exception handling, the system hangs and my dumpfile indicates the GPU was unable to write to some memory address.

v76.1025 dropped on the headset, but no change.

VD din't work for me either since this issue exists