Varjo is broken after new update (solved)

[motoadve]

FDR Mbuccia does not work.

Eye tracking does not work

Quadviews its a downgrade with worse graphics and performance.

 

Solved:

 

Uninstall MBuccia DFR, then re install it , start game, and go to VR options and check Quadviews option, it gives you an extra 10 to 15fps like always with DFR, and you can adjust your focus and peripheral values to your liking.

Look at this picture, this is why DFR is better than the rest, top picture is stereo all the screen is high resolution, then Quadviews, which is better, and  lower is Quadviews and Foveated Rendering, even better, no wasted performance on the areas your eyes dont see. 

Edited October 1, 2024 by motoadve

[festr]

I can confirm. FDR Mbuccia stopped working. Following the recommended varjo enabling foveated rendering (without the mbucha) enables the foveated rendering but the eye tracking does not work. 

[motoadve]

10 minutes ago, festr said:

I can confirm. FDR Mbuccia stopped working. Following the recommended varjo enabling foveated rendering (without the mbucha) enables the foveated rendering but the eye tracking does not work. 

I got it to work with the registry change recommendation, works but its a huge downgrade with very low resolution and worse performance than before.
Unacceptable honestly, looks and performs like crap and that is with a AMD 7800X3D and a 4090.

 

[festr]

I have managed to debug the foveated rendering - the rectangle in DCS is too small - we need to have control over this in DCS - to be able to change the rectangle size + possibility to change the resolution scaling of the rendering in the inner and outer - otherwise its huge step backwards. 

there is also glitch when looking left the rectangle changes like this on the picture and I can see artefact on the whole image if this happens: 

 

null

[BIGNEWY]

Hi all, 

we will ask the team to take a look. 

thank you 

Please attach your dcs logs 

[festr]

turning off the eye tracking in the new vr option fixed the problem with wonky center area. 

mbucha extension is also working but the quad rendering MUST be enabled in the DCS and eye tracking MUST BE DISABLED 

all is working as expected - the only problem for varjo seems to be that the eye tracking has to disabled 

[motoadve]

1 minute ago, festr said:

turning off the eye tracking in the new vr option fixed the problem with wonky center area. 

mbucha extension is also working but the quad rendering MUST be enabled in the DCS and eye tracking MUST BE DISABLED 

all is working as expected - the only problem for varjo seems to be that the eye tracking has to disabled 

Not working for me, I have a Varjo Aero, which headset do you have?

[BIGNEWY]

can you attach your dcs log motoadve, we can look for clues. 

thanks

[festr]

42 minutes ago, motoadve said:

Not working for me, I have a Varjo Aero, which headset do you have?

on varjo discord another user with aero reported that it works for him like before the patch. Did you enabled the quad rendering in the new DCS option in the VR section? 

(I have XR4) 

[motoadve]

33 minutes ago, BIGNEWY said:

can you attach your dcs log motoadve, we can look for clues. 

thanks

Thank you , I made DFR work, and also got the multipliers working, so it looks as before, however I have some stutter that I did not had before , used to be super smooth.

To make it work I did the following:

Deleted Mbuccia DFR

Re installed Mbuccia DFR

Deleted the Varjo OpenXR registry

Checked Quadviews in VR options in DCS

Unchecked Eye tracking in VR options in DCS

 

Log is attached, thank you for looking into it.

dcs.log

4 minutes ago, festr said:

on varjo discord another user with aero reported that it works for him like before the patch. Did you enabled the quad rendering in the new DCS option in the VR section? 

(I have XR4) 

Yes, and in VR settings I get this message.

null

[Tempest7]

Varjo works fine for me with quad views both on and off, and eye tracking on and off. 

Mbuccia's own docs recommended that you DO NOT use his software for the varjo headset and rather use the Windows Registry Editor to manually enable the quadviews for applications regardless of support. Now that DCS supports it in the options, I don't think there's a need for even that. So I've disabled the regedits and just used the in game DCS options. 

[motoadve]

44 minutes ago, Tempest7 said:

Varjo works fine for me with quad views both on and off, and eye tracking on and off. 

Mbuccia's own docs recommended that you DO NOT use his software for the varjo headset and rather use the Windows Registry Editor to manually enable the quadviews for applications regardless of support. Now that DCS supports it in the options, I don't think there's a need for even that. So I've disabled the regedits and just used the in game DCS options. 

DFR Works now with Quadviews checked, and Eye tracking unchecked,  Mbuccia DFR has better performance than Quadviews,and you can also fine tune the focus and peripheral values for better increased resolution and better performance, he recommends to use Quadviews because he does not support DFR anymore, but definitely Quadviews its a downgrade from DFR, unless you never modify focus and peripheral values, then might be the same.

 

In game works, you are right,I tried Quadviews and Eye tracking checked in game, the visuals are a lot worse and the performance reduced by 10 to 15FPS compared to DFR, I recommend DFR.

[Jimmy8x]

I am on a brand new fresh install of Windows 11, with no mbucchia tools.  

I am using Varjo's registry edits to force DFR. https://varjo.com/vr-lab/make-the-best-out-of-your-varjo-experience-update-on-varjo-quad-view-eye-tracked-foveation-and-varjo-base-settings/

It is working well, with the new Quad Views option enabled, and the 'Track the eyes position' option DISabled. When 'Track the eyes position' is enabled, eye tracking quality is significantly worse. 

Edited October 1, 2024 by Jimmy8x

[Darpa]

 I am not very technical so I am not going to try the Varjo registry edits but I do have default Mbuccia DFR installed (I have never modified any values). 

So am I correct in assuming I can either:

1)  Keep Mbuccia DFR installed and in the new DCS VR options just check Quadviews and UNcheck eye tracking

2) Remove Mbuccia DFR and check both Quadviews and Eye tracking (but I may get worse visual quality and performance)

I just want to make sure before I update. Thanks

[Tempest7]

1 hour ago, motoadve said:

DFR Works now with Quadviews checked, and Eye tracking unchecked,  Mbuccia DFR has better performance than Quadviews,and you can also fine tune the focus and peripheral values for better increased resolution and better performance, he recommends to use Quadviews because he does not support DFR anymore, but definitely Quadviews its a downgrade from DFR, unless you never modify focus and peripheral values, then might be the same.

 

In game works, you are right,I tried Quadviews and Eye tracking checked in game, the visuals are a lot worse and the performance reduced by 10 to 15FPS compared to DFR, I recommend DFR.

I did not notice worse visuals or performance with both boxes checked.

 

But I uninstalled mbuccia's solution after he recommended using Varjos Win Reg editor. 

I'm on the Aero. Fyi

1 hour ago, Darpa said:

 I am not very technical so I am not going to try the Varjo registry edits but I do have default Mbuccia DFR installed (I have never modified any values). 

So am I correct in assuming I can either:

1)  Keep Mbuccia DFR installed and in the new DCS VR options just check Quadviews and UNcheck eye tracking

2) Remove Mbuccia DFR and check both Quadviews and Eye tracking (but I may get worse visual quality and performance)

I just want to make sure before I update. Thanks

I'm running the second option and I'm not noticing worse visuals. Or performance. 

There definitely seems to be some variance here. 

[motoadve]

Uninstall MBuccia DFR, then re install it , start game, and go to VR options and check Quadviews option, it gives you an extra 10 to 15fps and you can adjust your focus and peripheral values to your liking.

Look at this picture, this is why DFR is better than the rest, top picture is stereo all the screen is high resolution, then Quadviews, which is better, and  lower is Quadviews and Foveated Rendering, even better, no wasted performance on the areas your eyes dont see. 

[festr]

13 hours ago, Tempest7 said:

Varjo works fine for me with quad views both on and off, and eye tracking on and off. 

Mbuccia's own docs recommended that you DO NOT use his software for the varjo headset and rather use the Windows Registry Editor to manually enable the quadviews for applications regardless of support. Now that DCS supports it in the options, I don't think there's a need for even that. So I've disabled the regedits and just used the in game DCS options. 

Mbuchas DFR is crucial for XR4 headset which has 4k panels for each eye. There is tuning option which allows to lower the peripheral resolution - I personally use 0.6 scale factor of the peripheral alongside with DLSS which still looks nice (almost indistinguishable from the scale 1) and it saves a lot of FPS. I can also make the focus area larger to my liking. There is also "turbo mode" switch which smoothness FPS if you reach maximum possible for the headset (less stutters). The tuning option like scaling of the resolution and scaling the focus area is crucial and this should be possible to define directly as a new DCS internal options before we can fully drop mbuchas DFR.  

[mmike87]

Out of sheer curiosity, I decided to move to the latest Varjo Base after sticking with the last 3.x version for so long as the 4.x versions seemed to kill performance on the "all-but-abandoned" Aero (thanks, Varjo! You're why I ordered a Somnium VR-1!).

I tried the registry settings suggested by the Varjo blog post, uninstalled Varjo-Foveated, and ran my usual Caucuses free-flight route and frame rates and visual quality were noticeably worse. Not sure if I did something incorrectly or not, it's possible. I noticed that the Varjo-Foveated Github suggests not using the tool any longer and going with the Varjo solution - which makes we wonder if I did something wrong given that mbucchia's solution (for me at least, and it seems a lot of folks) still offers the best performance option for Varjo users.

Blows my mind that someone who doesn't even work for these companies can still out-do them on the side and for free. Makes me really appreciate Varjo-Foveated and still wonder why no one else can seem to get it right.

Procedure I followed:

1) Uninstalled Varjo Foveated

2) Downloaded latest Varjo Base and installed

3) Verified the headset was working correctly

4) Made registry changes as per Varjo blog post

5) Re-started Varjo Base using the option in the app

6) Started DCS

7) Verified that "Quad Views" option in VR was checked (it still was)

8. Started free-flight mission and marveled at the giant step back in performance and quality

I un-did everything except the 4.4 Varjo Base install, re-installed Varjo Foveated and all is well again. The only good news is I can at least run the latest Base software, for whatever that is worth given the lack of attention the Aero receives. At least whatever was killing performance on the Aero in earlier 4.x versions seems to have been fixed.

[mmike87]

I tried another experiment. I stayed with the latest Varjo Base, but set both registry keys to 0 and also disabled Quad Views in DCS. I then re-enabled OpenXR Toolkit, and enabled Turbo Mode and the fixed foveated rendering.

My frame rates seem a little lower ... less time at 90 and more time in the 70-80s... BUT, I swear it seems smoother and there are fewer stutters. To make up for not being able to increase the focal-point resolution like we can with Varjo Foveated, I set the render resolution in DCS to 2.0 ... and then the middle and outer rings of the custom FR in OXRTK to 1/8 and 1/16 respectively.

The visual quality still is not as good as with Varjo Foveated, but overall I think the experience seems smoother.

Not sure if I will keep it this way ... and I am not even 100% convinced the fixed foveated rendering is working because changing it doesn't seem to change anything visually. I do miss being able to use the post-processing features.

Anyway, an interesting experiment.

Edited October 12, 2024 by mmike87

[Shein]

On 10/12/2024 at 4:50 PM, mmike87 said:

I tried another experiment. I stayed with the latest Varjo Base, but set both registry keys to 0 and also disabled Quad Views in DCS. I then re-enabled OpenXR Toolkit, and enabled Turbo Mode and the fixed foveated rendering.

My frame rates seem a little lower ... less time at 90 and more time in the 70-80s... BUT, I swear it seems smoother and there are fewer stutters. To make up for not being able to increase the focal-point resolution like we can with Varjo Foveated, I set the render resolution in DCS to 2.0 ... and then the middle and outer rings of the custom FR in OXRTK to 1/8 and 1/16 respectively.

The visual quality still is not as good as with Varjo Foveated, but overall I think the experience seems smoother.

Not sure if I will keep it this way ... and I am not even 100% convinced the fixed foveated rendering is working because changing it doesn't seem to change anything visually. I do miss being able to use the post-processing features.

Anyway, an interesting experiment.

I'm right there with you. I want a VR-1 so bad because I'm so done with varjo's BS. 

I haven't flown DCS in a few months and I come back to find nothing works anymore. I completely nuked all my VR applications and started from scratch and I can't get a non-stuttery mess no matter what I do. I'm trying to go back to however I had Mbuccia set up because that was the last thing that worked...