Chief_Biv

I was forced to get a new headset mid last year when my G2 cable failed. I also only have a RTX3080. I purchased the Crystal (OG). The eye tracking has enabled me to avoid upgrading my PC for the last 12 months and I reckon for another 18months at least. Spending money on an eye tracking headset made sense for me and if I was in the position of purchasing now I would rather get a Super than a Light. However, sorry to hear that your 3080 is failing. You may as well get the latest GPU if forced to and that will give you options to consider the Crystal Light. The OP had a 4070Ti and would have benefited from eye tracking except that his CPU is not as strong and probably would not cope with Quadviews.

I don't quite understand what you did differently. I thought there is only one way to connect the Crystal to the Display port on the GPU. What have you done differently to fix this that is different from normal method? nullnull

Ok. So you are CPU limited. It is going to be difficult for me to help you. You have a better GPU than me and therefore I cannot speak with any experience with a rig like yours. If Quadviews tips you over from being GPU to CPU limited combined with a drop in fps then there must be something else swamping your CPU's capacity. You will have to investigate what else is consuming CPU resource in the background. Use the Windows Task & Resource Performance manager to observe all this. Does it show your CPU at 100% capacity, are you temperature throttled, are all your CPU cores being utilised? Also, you may want to try turning off any data export apps you may have running in conjunction with DCS (e.g. Tacview, Winwing's SimAppPro, etc). I also assume you are running the very latest version of DCS too. I am running out of ideas. But it looks like something has maxed out the critical core in your CPU.

Is does not make sense that you are CPU bound with an X3D CPU chip. I have read that when Turbo mode is on that the CPU/GPU bound indicator is no longer reliable - see here; DCS World Performance and Settings Guide | Osean Air Force 8492nd Squadron What is your GPU and how much RAM do you have? Does the Toolkit also tell you that you are CPU bound when turbo mode is off? Does the DCS fps frame counter that you pictured above also tell you that you are CPU or GPU bound in agreement with the Toolkit fps counter? When trying Quadviews have remembered to turn on Quadviews with the new tick box within the DCS settings? Are you using Motion Smoothing in Pimax Play?

That one is plenty strong. Make sure you are not running stuff in the OpenXR Toolkit if you are running Quadviews. It is safer to disable the toolkit. See if that fixes things.

Quadviews requires a good CPU to run alongside DCS. What is your CPU?

WMR still works with 23H2. You have to avoid 24H2.

I am not surprised. You really need to rely on MR and DLSS on top of QV if you want to look at a quality visual in the G2 with a 4070Ti. There always has to be a compromise until you have a 5090. It's really up to you to pick your compromise. 60Hz is a pain for a lot of people (flickering), but is good for others.

I did not know that. I only started using the companion app after getting the Crystal. I edited the config file when I had the G2. Yes, I forgot you also have to tick the new Quadviews tick box in DCS.

I am not sure why it did not work for you last time. It only worked in MT and ST has been removed now. The additional advantage of Quadviews is that you can really tweak its settings. The easiest way to do this is by using the Quadviews Companion as I referred above. Anyway, have fun with it now. G2 was and is a good headset. Just remember not to update Windows 11 beyond the 23H2 feature set to keep the G2 working.

Go to this page for clear instructions: https://github.com/mbucchia/Quad-Views-Foveated/wiki . Follow these carefully and don't try any shortcuts. There are some settings you may have to change in the OpenXR Toolkit as described in this linked page. (e.g. do not implement the Fixed Foveated Rendering in the toolkit if you are using Quadviews.) If you are confident enough to read the advance settings section here https://github.com/mbucchia/Quad-Views-Foveated/wiki/Advanced-Configuration you will note that you can enhance the resolution in the focus section. Also there is QuadViews Companion for easy config adjustments. https://www.digitalcombatsimulator.com/en/files/3332882/ There is a bit of effort involved, but Quadviews is supported in DCS and well worth recommending to a DCS user.

If you are really interested in maximising fps and minimizing frame times, you really need to implement Quadviews and use its fixed foviated rendering. That way you can run the non-focus outer area at a lower resolution and the centre focus area at full 100% to get the most out of the G2. My G2 cable broke and I moved on to a Crystal. However, before this happened I started using Quadviews, stoppped relying on the OpenXr Toolkit for tweaks and was pleasantly surprised. I also had to employ Motion Reprojection and DLSS Quality to get a smooth experience because my RTX3080 is not powerful enough to achieve 90fps without these whilst displaying native resolution and PD=1.0. It seems as though you are avoiding adopting these particular settings. Whilst I also believe that the RTX4070Ti out performs a 3080 I don't think it can achieve 90fps without down-rating the resolution or PD as you have done. If you want to look at a better picture in the headset you will have to make a compromise somewhere and these are my suggestions. What Google and AI told you is true for a single 1440p monitor. Your G2 is more than a 1440p monitor times 2 (one per eye). I dont think the AI thought about the two displays in the headset.

OpenXR Toolkit is not absolutely necessary. However there is nothing wrong if you still want to use it and it has some benefits for G2/WMR users. If you are tech savvy and you upgraded your PC hardware you could also use Quadviews (look up the guides) that will give you a performance boost, but I would not recommend it because your CPU is not strong enough to run it. If you have a G2 and you have set OpenXR as your default run time in the OPenXR Tools for Windows Mixed Reality, and you have ticked the "enable HMD" in the VR tab in DCS settings, then the only thing you need to do to launch DCS in VR is: Launch Windows MR and turn your headset on; and Launch DCS DCS now launches VR in OpenXR by default making launching DCS in VR very simple for you provided you have set up your PC to run your headset in OpenXR and not steam/OpenVR by default. You don't have to run the OpenXR Toolkit, or the OpenXR Tools for WMR apps unless you want to change their settings outside the game, or to enable or disable them prior to launching the game. However once they are enabled, you don't really need to touch them. Unfortunately, this stuff is quite complicated. I hope this helps you understand it a little more.

I have a Pimax Crystal with a RTX3080. I have run it without eye tracking on rare occasions, which would be similar to running the PCL. It's ok. You will have to run DCS using Quadviews and with medium textures and settings. I run it at 72Hz. I can get it running at 72fps aggressive foveated rendering but in some situations it drops below this still. I can get away with aggressive foveated rendering with eye tracking, but you will have to tone it down in the PCL because it does not look pleasant without eye tracking.

I did not think it was possible. I always had to fall back on MR for smoothness. By the way, my G2 cable broke and I bought a Crystal instead.

ED said it is coming and now there are a lot of people who would like an honest update, including me

I have Windows 11 Home edition. I have made this entry in the Registry Editor. Can some who knows how W11 Home works advise if this will keep my machine on the 23H2 update? null

If you have QV enabled in the new Pimax Play you have to disable the OpenXR Toolkit. They are not compatible.

Correct. The Toolkit does not provide Quadviews, just conventional foveated rendering. I think you should leave QV unticked and you should not experience any noticable change. I believe in this week's patch it was changed to a on/off switch for those that have Quadviews installed. However, BigNewy needs to confirm this because his Tuesday response above only applied to DCS before this week's update.

I believe that has happened to me too. I also had a crash, and had to reboot the whole PC. Tracking this thread. I have not got time to experiment for a couple weeks. Does running the new start game UI or bypassing it make a difference?

I think that is helpful. I will edit the file so it points to the new folders that replaced the old "\Mods\aircraft\Flaming Cliffs" folder that has disappeared. I think I can see what ED changed in the DCS folders and files. Yes, that fixed it. Thanks a lot!

With the change from FC3 to having individual modules I can find no content for the J11 module. Was there any content for this plane in the original FC3 or has it been deleted during the update?

I have just updated to the new hot fix patch today after missing the previous one due to other reported issues. I can now see that FC3 does not exist as a module anymore, but has been replaced by the individual aircraft modules. However, all the complimentary campaigns that come with these planes have been reset to "inactive" after the update. How do we get the old status back?. I presume there has been a delinking of these aircraft from something stored on the Saved Games folder because of module name change?

Use Quadviews for your FFR and turn it off in OpenXR Toolkit. To be honest I would experiment with sharpening in the DCS settings or OpenXRToolkit, but not both. Pick the one you think gives the best result. I would also leave any upscaling to those that come in the game and leave this off in the Toolkit. I don't think I use the Toolkit settings for anything other than colour balance anymore. All of the other settings in the Toolkit are either now provided in-game or in Pimax Play or in Quadviews. Have fun with it. At least you have a 4090 to drive it. It should be great.

So the best work-a rounds are either?: Turn Quadviews off; or Turn eye-tracking off but leave Quadviews on??; or Leave on Quadviews and eye tracking, but run in ST but with the "-force OpenXR" [sic] argument in the execution string? I am not sure if option 2 would work. Please advise someone?