Nuggetz

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

Having updated Quad Views to the latest v1.1.3 the clarity and fps issues experienced have been resolved in my Pimax Crystal. However if DLSS or any of the AA/DLAA settings are selected I get a few lines of white text in the headset (only) fov close to the edge so difficult to read as it moves with the headset. In short something to do with autoexposure off, resolution numbers etc. The only way not to have the message is with DLSS and DLAA set to off. Once flying DLAA can be selected on but frankly no improvement noticed with the shimmer were present ie pylons security fences etc. Otherwise good work ED and mbucchia for the Quad Views update (great work!).

As a fellow Crystal user I can confirm I am experiencing the same sorts of issues. If I am unable to resolve tomorrow I will switch to my 8KX to see if the issues are restricted to the Crystal.

I had been very happy with my FPS and clarity using Quad Views also. I must recheck all my setting’s tomorrow.

I guess I must be doing something wrong given the positive comments above. Using my Pimax Crystal the clarity of the visuals is very poor and even a reduction in FPS. I have tried playing with all the DLSS and DLAA settings with all the DCS settings set high etc. I have checked the Open XR toolkit which is set to default. Will investigate more tomorrow but at a loss so far and somewhat deflated. UPDATE: Just updated Quad Views to the latest version 1.1.3. Clarity and FPS restored.

The inability to maintain radar lock especially in guns BFM has been very disappointing since two patches ago. That is with or without background clutter. WhileI have enormous respect for the developers at ED I am crossing my fingers the radar update gets released very soon.

+1 The map is excellent and the bench mark by which other maps will be judged within DCS.

Having done more flying with guns BFM against various aircraft targets on different maps ground clutter does appear to be a factor but I have also positioned the F16 below and behind the target (clear sky beyond) and find the radar can continue to drift and lose lock. I am not sure this is the effect that DCS was attempting to replicate. I will be watching future GrowlingSidewinder videos with interest especially those low level guns BFM videos to see how he gets on.

You may be onto something there. I will investigate this tomorrow. Thank you for your reply

I am experiencing problems with the F16 radar in dogfight mode since yesterday’s patch. If I merge with a eg F14 with the intent of having guns BFM fight I can repeatedly lock the F14 however the 12,000 ft gun reticle does not stay locked on target as has been the case since day 1 of the F16. No sooner is the target locked than the reticle drifts off. It can auto relock but cannot maintain the lock. I have tried TWS, RWS, VSM and TMS up and down and cannot understand what has changed. If it’s me then hands up, but if I use the NTTR instant action mission (9X) on F5 drones, but use guns only DCS performs normally (as before the patch) so why the difference? if anyone else having similar issues or can someone let me know what I am doing wrong please? Many thanks in anticipation. No track file due to the very large size with my 8KX.

SOLUTION: I appear to have found the solution, at least for me. I have switched from Pitool (V.277) and now use Pimax Client 1.10 all the problems experienced when switching between F1-F10-F1 appear to have been resolved with a much smoother experience and high FPS. Hope this helps other Pimax users.

I continue to experience lagging and wobbling headset visuals despite recent software update. Given the FPS is 75 @ 75hz it appears that moving one’s head gives the impression the headset tracking can’t keep up resulting in the laggy stuttering views inside and outside the cockpit. I have turned the textures down and MSAA off (Pitool 1.75) which has helped in general but the main issue persists. As long as I don’t touch the F10 key performance and visuals are very good. Has anyone found a solution yet?

You will know that in reality aircrew value their 1000, 2000…. Hours on aircraft type proudly displaying badges on flying suits and jackets. Although ED are incredibly busy developing MT and other important features I wonder if having digital equivalents to 1000+ hour badges and possibly the fabric equivalent from a ED shop merchandising perspective would be of interest to DCS pilots? Not sure how to implement digitally perhaps a mod to the avatar used by the individual? Hopefully if there is enough interest and development time allows ED may consider -Just a thought. Standing by to get shot down.

Same for me (F16), specs below.

Have you tried importing the new DCS shortcut into your mygames folder in Pitool? This help me.