zildac

So, even disabling all OpenXR layers (OXRTK, Varjo Foveated) using the GUI layer tool and just having the Reshade OXR layer active makes no differnce. Effect is active in the desktop window but nothing in the HMD

Same issue even with "everyone" with full perms. Very odd, stumped.

Not here D:\DCSWorld I can't see any errors in the ReShade.log, the only other thing is that I am running Matts Varjo Foveated.

I've also installed the "addons" version and there is only the one option as per my screenshot... null

I must be missing something, 2D window works fine (ascii effect selected) but no change in the HMD. I only have one sync option, which is checked. null

Switch it on and off again fixes everything

@speed-of-heat I'm not at home to test this, but are you using Matts Varjo Foveated or Quad Views foveated,could that be a factor? You mentioned layers in an earlier post.

Be great to see this working, I've not used it in DCS for a long time (pre VR). Anyone have any preset configs they'd be happy to share?

Excellent news!

It's sad and disheartening...this should all be an "ED" problem to fix. But unfortuantely it's individuals like @mbucchia that have been bullding on and pushing forward the VR eperience in this sim to cover the shortfalls that the vendor has blatantly ignored or put to the back of the backlog to address , whilst focusing on "stuff" that generates revenue, whilst paying lip service to the real issues. A bug report with the level of detail provided, that is so fundamental to the VR experience should not still be outstanding after nearly two years, that's madnes! Or it's just not considered a priortity, which quite frankly is even more worrying. All DCS users , but especially VR DCS users have a huge financial and emotional investment in the platform, we really need to be treated as such and deserve to have these fundamental issues addressed. Most frustratingly , the issues hve been explained and documented in great detail and include all of the remediation steps. At this point it's just crackers that it's not been latched on to and sorted. It's basically free consultancy from an industry expert, that's just then igonored! Horse to water and all that!

This is great, I hope it's taken onboard and the devs get it fixed as it seems to be something that is rather fundamental to the DCS engine and VR! And with this level of detail the only real excuse would be "time", but that can be addressed with "priority"

Correct, unfortunately

If you have a Varjo headset, just uninstall Quad Views Foveated and install Varjo Foveated and set the config to your liking: https://github.com/mbucchia/Varjo-Foveated/releases/tag/0.2.0 All the info re config can be found in the Wiki including wich DCS settings need to be disabled or cause issues. https://github.com/mbucchia/Varjo-Foveated/wiki And make sure you disable DCS and DCS World in OpenXR toolkit (if you have it installed)!!!

Definetely!

Thanks Matt, I found the issue. I checked OXRTK and DCS.EXE was indeed enabled , because guess what, it used to be called DCS World and it was automatically enabled as a result of the name change! That's going to catch a few people out I suspect.

Understood and hadn't really taken the wider impact of an unsigned release into consideration. As an aside, for me even Varjo Foveated is borked. Just tons of: 2024-07-11 21:37:33 +0100: xrEndFrame failed with XR_ERROR_HANDLE_INVALID messages in the log after the 2024-07-11 21:37:31 +0100: Creating swapchain with resolution: 2048x2048 message A DCS timeout for me I think! This doesn't appear to work for me 2024-07-11 21:37:28 +0100: Creating swapchain with resolution: 1908x1908 2024-07-11 21:37:28 +0100: Creating swapchain with resolution: 1908x1908 2024-07-11 21:37:28 +0100: Creating swapchain with resolution: 1824x1824 2024-07-11 21:37:28 +0100: Creating swapchain with resolution: 1824x1824 2024-07-11 21:37:31 +0100: Application is using Quad Views for this session. 2024-07-11 21:37:31 +0100: Creating swapchain with resolution: 2048x2048 2024-07-11 21:37:31 +0100: xrEndFrame failed with XR_ERROR_HANDLE_INVALID

You could just use Varjo Foveated, it still works. Quad Views Foveated has the issue.

Unfortnately:

I completely understand, and appreciate your frustration. @BIGNEWY I know you've submitted this as a bug to the team, but can you please ensure they understad the context and the detail as outlined by @mbucchia and the fact that in the MT binary version they are doing OpenXR "wrong" and are not compliant with the standard. There are a large number of VR users thast rely on this implementation by Matt to achieve acceptable performance in VR. It would be a real shame to let this one drag on, as it has been and absolute blessing for many many months. @mbucchia Frankly, given what you've already done I'm sure the community who have been reaping the benefits of your work for the last couple of years would be able to cover the code signing cert cost plus some Kickstarter!

Bit cheeky, but could you perhaps add a fix in your QVFR, if they haven't addressed something so fundamental called out over a year ago I'm not holding my breath for it to be sorted anytime soon [emoji849]

Yeah, I think I'd be looking at an alternative solution if it were me. Like just some additional local or even USB attached storage.

[emoji23][emoji1303]

Ah, and then you drop the deck for the last batch run of your shift [emoji16]

This mod may also help, however note that it also removes the dark tint from the helmet visor, but it doesn't need to be installed as a livery as per the mod you reference.

Numerous threads on this, it's an FP.