Nuggetz

After much investigation I have found a work around. if I disable eyetracking and auto IPD the headset no longer goes blank thus crashing DCS 10-60 minutes into a session. Note: eyetracking and and auto IPD work fine right up to the crash so it’s not a calibration failure. Historically I had connected the Pimax Crystal data cable to a USB 2.0 (not USB 3.0) which had worked fine for months but now I use USB 3.0. More testing over the weekend and then an email to Pimax on Monday! UPDATE: Following an exchange of emails with Pimax I have restored eyetracking. The solution was to remove the DP cable from the headset socket and disconnect the short cable from that socket direct into the headset. Then the long DP cable is insert directly into the DP socket under the headset top cover. Thus eliminating the short cable altogether.

I will check next time I log in. Thank you for the suggestion.

I have been hopeful that I might have fixed things but the crashes continue. I attach the latest log which shows a number of errors and warnings but I cannot figure out what is going on. Any suggestions please? dcs.log

Thank you for your suggestion. I don’t use pass through. it is early days but I think the Echo19 Core update may have been the root cause. I have deleted the Core update and at least temporarily deleted the ECHO19 sound module. I ran two long missions last night with no crashes in SP Mode. This morning I plan on doing some MP missions. If that works without crashes I will consider the problem resolved. I shall report back later.

Thank you for your help. I did recently download the ECHO19 Core update to my existing ECHO19 sound mod but I did delete the new Core update just in case it was that causing the problem. I need to uninstall the original ECHO19 files as well and then reinstall the base module only. Fingers cross that fixes it. thanks again.

I have been trying to fix this problem and thought I had made progress when flying two long missions in the Kola map this morning. I attach this mornings logs. I note there are a lot of XR runtime errors and that the trackfile was skipped due to the large size. Any help gratefully received. TY dcs.log dcs.log-20240508-073445.zip

Thanks Bignewy, PSA, TYdcs.log dcs.log-20240507-100112.zip dcs.log-20240507-061550.zip

After playing from 10-60 minutes my headset goes blank and DCS crashes. When I look at the latter entries in the Log there is a warning that the track file is too large. This happens in both SP and MP. I have been using the Crystal for 10 months and this problem has only just started in the last 2-3 weeks. I have done a slow repair on DCS but is still happening. I have also raised a ticket with Pimax but would welcome any help or advice to resolve this issue. Thank You. ps I have approx 1.0 TB of spare memory at this time.

I have noticed with today’s update that: I opened an F16 mission in my missions and moved an aircraft a few miles (air) but when I tried to save DCS would not allow me to do so. I could Save A$. I also noticed that upon landing with a F16 TGP attached and then rearming the TGP stops working but TGP power off/on restarts ok. Not sure if this behaviour is intended?

Although you issue may be different when I had flickering with my 8KX it was down to the main cable. Try connecting your Crystal direct to your PC eliminate hub issues and try again. Check your Device manager to ensure Windows cannot turn off USBs/HIDs. HTH

When you calibrate just have the Pimax software running and only tick the eyetracking box. Do not tick IPD or wearing notification. If you know your IPD that would be good and set it manually. Then retry the calibration hopefully it should work this time. HTH

I would add that unless I power the Crystal on first before any power to the PC the headset/client do not connect. I also have to regularly check the USB/HID trees in Device manager to ensure the box allowing power off to the USB is not enabled. There have also been a number of time the headset disconnects after various time periods causing DCS to crash. I suspect these issues are all related so I hope a fix is provided soon. Thanks.

I would check your Device Manager. Go through each of your USB trees and HIDs and check that Windows has not ticked the box to allow power to be turned off under Properties and Power Management tabs. Once you untick any offending boxes this will stop your problem which affects the headset which in turn causes DCS to crash. HTH.

I recall this topic from an earlier post and I thought you might be interested in what others achieved.

Not working for me either

Maybe the Crystal cable is faulty (I had one fail with my 8KX). I would also clear out your NVIDIA cache if you have not done it for a while which may help. ignore the sim it’s the Nvidia guidance that’s the important bit. HTH Also check your cable connections and that you have a good power supply to the headset the provided USB hub can be iffy. Again alternative powered USB hubs are available and YouTube videos are helpful. HTH

My experience is that once the PC and any related power is switched off the headset stays shut down. if you intend to continue using your PC I recommend removing the battery while the headset lights are off and that ensures it’s off until you next want to use it. HTH

I just wanted to add my appreciation for the developers- well done all. VR appears to have a cleaner, smoother set of images with increased FPS. DLSS now appears to have the benefits of DLAA but with increased performance included. Thank you all again.

I have a Pimax Crystal with which I am very happy with one exception. In the left lens only I can now see a couple of arcs of guardian rings which now acts as a distraction in the low fov. I have used the Pimax forum and contacted Pimax directly for a solution without success so far. With Pimax support I am about to rollback the Pimax Play and Crystal firmware but before doing so I thought I would ask the DCS community. As far as I know the Crystal does not use guardian rings and I don’t have SteamVR installed so chaperone rings do not apply. I have done the usual resetting, uninstalling and reinstalling of all relevant software including clearing out the PC registry without success. Does anyone have any ideas to help resolve this issue please. Note: Guardian rings in Pimax XR is set to off. Many thanks in advance. UPDATE: Faulty headset returned to Pimax replacement headset received- all good now.

Can I ask is everyone in this thread using quad views version 1.1.3. As a 3080TI user I had been experiencing imaging quality and fps issues after 2.9 but now run the Crystal at max resolution/72hz and enjoy super clear images and pretty much rock solid 72 fps most of the time with most settings high/max. Apologies if you are already using 1.1.3 but didn’t see it mentioned in the thread. Hope this helps.

I had a similar problem and this solved the problem for me: EDIT & Fix: Mbucchia solved the problem by fixing a registry entry: Open registry at HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore Set the key ShowDlssIndicator to 0 Hope this helps

Thank you so much Mbucchia, you are a legend the layer/text has disappeared with both DLSS and DLAA. Thanks again

Hello Mbucchia firstly huge respect and thanks for all you do for the community. This could be lengthy so please bear with me, but I may have found a bug in QVFR. When DCS 2.9 was released I noticed a transparent layer in the Pimax Crystal that had some white text in the bottom left hand corner. It is not easy to read because of the location that moves with the headset. The text mentions something to do with auto exposure and some resolution numbers etc. I swapped back to my Pimax 8KX where the text also appears. I posted a couple of entries in the 2.9 thread release, but noted that no one appeared to agree or support my post or indeed raise their own. This issue only arose if I selected DLSS or DLAA. If for example I use MSAA X4 the text is not visible. This morning I disabled eye tracking in Pimax XR and QVFR. I also disabled eye tracking in the Pimax software the selected DLAA in DCS and noted the text did not appear but the FPS was down in the twenties. I reselected QVFR in Pimax XR and tried again and the text is back along with some odd shadow effects which had also been present. The work around is to select QVFR and eye tracking in Pimax XR, Eye tracking in the Pimax Software and MSAA x4 in DCS. Apart from some minor shadow shimmer the usual AA issues are dealt with and I get very good FPS. I apologise if this is posted in the wrong place in advance. Although I have a work around it would be nice to take advantage of the DLAA/DLSS feature in DCS. Any advice would be most appreciated. Regards

Thanks for the hot fix patch today. However, I continue to experience a transparent layer in both the Pimax 8KX and Crystal that contain white text in the bottom left corner. The text/layer moves with the headset so it is not possible to centralise to read more clearly. The text refers to auto exposure off and some resolution numbers and I cannot read in whole or clearly. It only appears in the in cockpit view once flying or on the ground. Any other screens at various stages do not have the text. I don’t know if it is possible to switch this layer off? Any assistance gratefully received. EDIT & Fix: Mbucchia solved the problem by fixing a registry entry: Open registry at HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore Set the key ShowDlssIndicator to 0 SOLVED

Updating Quad Views to version 1.1.3 fixed the clarity and fps problems for me, thank you mbucchia so so much