fixed Pimax Crystal Quadviews seems to broken after last patch.

[zzzHACKSAWzzz]

This thread alone proves that ED doesn’t test prior to updating. To stuff up such a major component of VR is mind-blowing. Here’s a suggestion ED, stop giving preview versions of modules to YouTubers who mask the real issues that are present and start giving updates to actual, community based testers who can spot these issues before they enter the wild. Oh and for gods sake, start implementing what mbucchia has been telling you guys for over a year. Inexcusable imho. 

Edited July 12, 2024 by zzzHACKSAWzzz

[Gideon312]

Same problem here on the Crystal and without the quadview I’ve got bad performance.

RTX 4090, AMD7800, 64 GB RAM, SSD

[WipeUout]

I've been using Quadview with my Pimax 8KX because it is far more superior to fix foveated rendering feature in Pimax Play or OXRTK.  It is borken for me as well, and even OXRTK does not work anymore.  Please fix this, I am going back to 2.9.5 as it is the only temporary fix for that 2.9.6 stutter fest and 2D DCS is not an option.

[Hariskut]

1小时前，Gideon312说：

Same problem here on the Crystal and without the quadview I’ve got bad performance.

RTX 4090, AMD7800, 64 GB RAM, SSD

I think your RTX4090 is strong enough to give you a good FPS, even without quadview.

[Gideon312]

7 minutes ago, Hariskut said:

I think your RTX4090 is strong enough to give you a good FPS, even without quadview.

Nope it doesn't 

[Mantikor]

Same issue here,

based on the strong marketing campaign with DCS and Pimax (dedicated to QuadViews!!!) I expect this issue to be priorized high  , I'm just a little wondering, why this not popped up during beta testing. Is there honestly no single Crystal User within the Beta Team ?

 

Ok enough sarcasm, looking forward to the fix

[Rufuz64]

Crystal / 4090 / QVFR / 72Hz / Stable 72 FPS with high settings.

Yes, Quad view simply is mandatory. Without this, the resolution would have to be lowered considerably to achieve a good FPS.
In my opinion, QVFR + Aero or Crystal are currently the best setups for playing DCS with the best quality in VR.
What really scares me is that such a bug would certainly have been noticed... It really seems that ED does not test with such a setup.

Picture: Open Flight School VR-Workshop Benchmark

[noknees]

Just in case anybody hasnt found it, 'Sandboxcode' has been kind enough to compile a replacement DLL that points to the renamed DCS https://drive.google.com/file/d/1KgQfV73_xPjVoVZMW9nwzrNT3fKcDAyu/view

Haven't tested it yet but folks are reporting it works 

[Rufuz64]

vor 10 Minuten schrieb noknees:

Just in case anybody hasnt found it, 'Sandboxcode' has been kind enough to compile a replacement DLL that points to the renamed DCS https://drive.google.com/file/d/1KgQfV73_xPjVoVZMW9nwzrNT3fKcDAyu/view

Haven't tested it yet but folks are reporting it works 

Tested, works

[mbucchia]

See

 

 

the unsigned DLL will screw up ALL OpenXR games that have anti-cheat, regardless of whether these games use or not use quad views.

It will make them fail in a way that will also pop up my name on the screen "failed to load XR_MBUCCHIA_quad_views...." aka pointing fingers at me 

This is why I'm not distributing the unsigned DLL.

Some examples of games using OpenXR and Anti-cheat that will break with an unsigned DLL system-wide: Pavlov, WRC, Contractors Showdown, Roblox...

 

 

In others words: people are going to copy this file, forget about it, then eventually they will run some game that will crash, point to me, and people will come and complain that I broke their games

On top of that, PLEASE, we have to stop bailing out Eagle Dynamics. They wrote some buggy OpenXR code. They need to fix it. By having people adding more and more duct tape to "hide" their problems, we are removing their accountability and continuing to deepen the problem.

They're not going to take this seriously and do the proper fix, if we keep bailing them out:

 

Edited July 12, 2024 by mbucchia

[Rufuz64]

vor 7 Minuten schrieb mbucchia:

See

 

 

the unsigned DLL will screw up ALL OpenXR games that have anti-cheat, regardless of whether these games use or not use quad views.

It will make them fail in a way that will also pop up my name on the screen "failed to load XR_MBUCCHIA_quad_views...." aka pointing fingers at me 

This is why I'm not distributing the unsigned DLL.

Some examples of games using OpenXR and Anti-cheat that will break with an unsigned DLL system-wide: Pavlov, WRC, Contractors Showdown, Roblox...

 

 

In others words: people are going to copy this file, forget about it, then eventually they will run some game that will crash, point to me, and people will come and complain that I broke their games

 

With a lot of respect for your work. I don't understand how this can be, since the DLL is in a directory that is only used for QVFR?

C:\Program Files\OpenXR-Quad-Views-Foveated\XR_APILAYER_MBUCCHIA_quad_views_foveated.dll

[gonvise]

2 minutes ago, Rufuz64 said:

With a lot of respect for your work. I don't understand how this can be, since the DLL is in a directory that is only used for QVFR?

C:\Program Files\OpenXR-Quad-Views-Foveated\XR_APILAYER_MBUCCHIA_quad_views_foveated.dll

The QVFR layer works in all OpenXR games

[mbucchia]

5 minutes ago, Rufuz64 said:

With a lot of respect for your work. I don't understand how this can be, since the DLL is in a directory that is only used for QVFR?

C:\Program Files\OpenXR-Quad-Views-Foveated\XR_APILAYER_MBUCCHIA_quad_views_foveated.dll

But how do you think DCS loads this DLL?

It is installed system-wide via a registry key (what we call "Implicit API layer loading").

Every single OpenXR game that launches will go and load that DLL, regardless of if it's DCS or of it uses quad views at all. There is no way to "filter" the loading of the DLL for each game. We have to cast the wider net - aka ALL OPENXR APPS - and them the API layer has detection logic for whether it is needed or not. The problem is that this detection logic is inside the DLL. So the lack of signing will make all OpenXR apps try to load the unsigned code, which will flag all anti-cheat software.

 

 

Edited July 12, 2024 by mbucchia

[csparks66]

mbucchia - Hats off to all the work you put into QuadViews. Hopefully ED will work on a proper fix.

 

For me the best solution was to turn off eye tracking in my Pimax software as I did not seem to lose any frames, just a degradation in the overall quality. 

I also experienced an issue after experimenting with multiple alternatives where my Pimax stopped going into VR. This was because I was messing with the OpenXR Foveated Rendering. In that case you have to follow the Open XR routine you do when setting up Quadviews. This includes setting Open XR Toolkit to safe mode and then reset the Open XR tool in VR. You can find the instructions by doing a search for QuadViews for Pimax then going to the Pimax blog for QaudViews foveated rendering. This reset everything and I was able to launch back into VR with QuadViews enabled but with eye tracking off.

[oCMANo]

6 hours ago, csparks66 said:

mbucchia - Hats off to all the work you put into QuadViews. Hopefully ED will work on a proper fix.

 

For me the best solution was to turn off eye tracking in my Pimax software as I did not seem to lose any frames, just a degradation in the overall quality. 

I also experienced an issue after experimenting with multiple alternatives where my Pimax stopped going into VR. This was because I was messing with the OpenXR Foveated Rendering. In that case you have to follow the Open XR routine you do when setting up Quadviews. This includes setting Open XR Toolkit to safe mode and then reset the Open XR tool in VR. You can find the instructions by doing a search for QuadViews for Pimax then going to the Pimax blog for QaudViews foveated rendering. This reset everything and I was able to launch back into VR with QuadViews enabled but with eye tracking off.

To workaround and be able to play with a decent FPS, I did the below.

With my settings, I just:

• Disabled 'Allow use of the eye tracker' in PimaxXR Runtime
• Lowered the DCS resolution down to 1440p from 4K
• Updated the DLAA/DLSS nvngx.dll with the latest version (https://www.techpowerup.com/download/nvidia-dlss-dll/), and switched from MSAA 4X to DLSS Balanced.
• In QuadViews raised the Focus Size from Horizontal and Vertical up from 25 to 30, and is quite playable now at 65-80 fps.

Hopefully they fix the issue soon.  Would like to go back to full resolution with the eye tracking, but hasn't been the end of the world.  

Edited July 13, 2024 by oCMANo

[Hunter Joker]

With mine, I just:

• Disabled 'Allow use of the eye tracker' in PimaxXR Runtime
• Lowered the DCS resolution down to 1440p from 4K
• Updated the DLAA/DLSS nvngx.dll with the latest version (https://www.techpowerup.com/download/nvidia-dlss-dll/), and switched from MSAA 4X to DLSS Balanced.
• In QuadViews raised the Focus Size from Horizontal and Vertical up from 25 to 30, and is quite playable now at 65-80 fps.

Hopefully they fix the issue soon.  Would like to go back to full resolution with the eye tracking, but hasn't been the end of the world.  

Can You write here how to substitute the dll? I know that apart overvrite it You must execute sono batch/executable...

Inviato dal mio RMO-NX1 utilizzando Tapatalk

[RetroOne]

Same issue here on Pimax Crystal...... ughh.  Will try turning off Quad view but hopefully they fix this soon.  The last version everything was running great with eye tracking and Quad view setup so it must be something that changed with this update.

[oCMANo]

2 hours ago, Hunter Joker said:

Can You write here how to substitute the dll? I know that apart overvrite it You must execute sono batch/executable...

Inviato dal mio RMO-NX1 utilizzando Tapatalk
 

Don't think you need to do anything other than replace the nvngx.dll in \Eagle Dynamics\DCS World OpenBeta\bin-mt directory.  

If someone knows otherwise let me know, but on the techpowerup page all it says was to replace the DLL in the game bin folder.

[stelr]

Sorry, but latecomer to this issue.  Pimax Crystal here, using a 3090, so QuadViews is essential.  I have the same issue and cannot fly until HotFix from DCS.  PLEEEESE prioritize this issue ED!

[instigatorxb]

So sad. Had an extremely tough work week and had purchased/downloaded the Afghanistan map yesterday in hopes of jumping in and checking it out tonight.

Pimax Crystal user, jumping to another game for the time being. <heavy sigh>

Just found the "Enable Virtual Reality Headset" slider doesn't stay set on exit/restart either. Probably better to chew on smaller code updates per patch.

Edited July 13, 2024 by instigatorxb
Added a newly found "feature"

[Dentedend10]

Pimax Crystal user, Quadviews is essential. I am also disappointed that this was not caught, as it is obvious right as you load up the game with Quadviews installed. Not willing to go back to lower graphics settings and disable eye-tracking which is the single most important feature of high resolution headsets. This magic software by mbucchia made DCS not only look incredible but also perform reasonably for VR users. Please fix this ED

[Dangerzone]

6 hours ago, instigatorxb said:

Just found the "Enable Virtual Reality Headset" slider doesn't stay set on exit/restart either. Probably better to chew on smaller code updates per patch.

Strongly suggest sticking with Skatezillaz DCS Updater for launching DCS still. It’s been doing a terrific job at launching DCS with different configurations for ages and it’s pretty solid/reliable. 

[Panzerlang]

Same here, the quad-view foveated box is jerking around (Pimax Crystal). 

[Hunter Joker]

I hope in a fix at least on Monday...at the moment I can't even test the new patch and the new map that I bought cause of it..

Inviato dal mio RMO-NX1 utilizzando Tapatalk

[Grennymaster]

for i have to disable eye tracking, then i can use quad view as usual, just without the eye tracking. Not the best but better then without complete. Im sure ED will fix this asap