johnbowzer

I have been using the Quest3 for 3 months now, owned a Reverb G2 V2 for 2 years, first headset, until last week. I sold it. My experience with the Q3 using link cable is better than anything I got with the G2, with every bit of tweaking that I could find/try. And it has a lot to do with the bigger sweet spot, but certainly not all to do with that. With not too much tweaking I have significantly more readable cockpits... and nice to just move your Mark 1 eyeballs instead of the entire head. And for the last few weeks I have switched to using VDXR, the OpenXR runtime to use with Virtual Desktop. So yeah, using the Q3 wireless. My router already supports the higher transfer rates for 2.4 GBPS, which many 5G/modern routers already do, and all 6G routers do. You do need that. And I can even leave the link cable plugged in to USB, though link not enabled, and it still charges, slowing the battery drain. And with VDXR even better visual results and frames than with link cable.

@mbucchia, hey I was wondering something after I read some info on DLSS, NIS, etc. In that info on NIS, it was mentioning that if you want to enable it, one had to do that in nVidia control panel via the "Image Sharpening" setting. But if we want to use NIS for DCS and we use the Toolkit, that should be left off in control panel, correct?

Hi. Going to try sharpening using the Toolkit. I am running a 3080. Seems NIS would be best option, is that what NVidia users prefer?

@lefuneste01, I have a clean install of 16.3 for OXR to match DCS version. I reset some some minor color changes as I had before, but adjusting haze up or down appears to have no effect. It did before with earlier version. Do you know if there is an issue with haze with 16.3 OXR and stable 2.7.14.24228 ?

"We seem to be made to suffer. It's our lot in life." - C3PO

I think the Microsoft Store is wacky, definitely some people see a different name for the same thing. They were supposed to drop the "developer" from the name. And some see that in the store, some do not, yet the installed product still shows the word in the title bar. As I do. Latest version, store does not show the word "developer" but opening my installed product via store open button still does.. So pretty sure 'OpenXR Developer Tools' and 'OpenXR Tools' are same thing, in the MS store. May be a Windows 10 or 11 thing.... The toolkit, as mentioned is the other one...

a nilpointer exception

I thought I was/am missing something, posts were getting confusing, but now I think that for the last several days there have been install and troubleshooting suggestions that are mixing the old and new ways to get OPENXR working with DCS. Unless I got it wrong, this is the evolution? The initial "per-application" method as per @nikoel was - short version - clean DCS, then replacing DCS's <openvr_api.dll> and <D3DCompiler_47.dll> and adding the <opencomposite.ini>. And this may still work. The new "system-wide" method as per updated post 1 using the opencomposite.exe. And this method requires no files to be put in DCS's bin folder, other than an <opencomposite.ini> should you want/need to use one. So the DCS version of </bin/openvr_api.dll> is not touched, and the DCS </bin/D3DCompiler_47.dll> is deleted or renamed so the windows version gets used (which is basically what was being used for the per-application method). I did everything as per new post 1 for system-wide install, and DCS ran in VR with G2, so it must be using OpenXR. Re-enabled OpenXR Toolkit 1.1 and it is OK. Just wanting to ensure that I got it right and am not leaving features off the table.

@TED, what are "the 3 files" that you are referring to?

It does, albeit somewhat quasimoto.

I did a search, didn't find a mention that defined it... what is the "3-9 line"?

It doesn't matter what mod tool you use or if you do it manually... but the 3dmigoto folder needs to go under the dcs bin folder, according to the first post. The contents of it do not go in the bin folder. That is the only way the instruction to run the initial loader exe before running dcs.exe is valid... "The mod must be launched with [DCSInstall]\bin\3dmigoto\3DMigoto Loader.exe prior to DCS.exe execution"

@HoBGoBLiNzx3, The OXR Toolkit is optional really. The OXR Dev Tools gives you the resolution options, MR on/off, which I use on always. And the OXR version of 3Dmigoto gives you sharpening, the haze reduction, color enhancing, and more. I am using the OXR Toolkit, but almost using none of its features now. I could even not use it at all since setting up 3Dmigoto... Some others may weigh in on how they use both to achieve more, but perhaps you don't need it.

@edmuss, I am on a 3080 & G2 and just wondering about using the RTSS, as per your edit in main post regarding locking it, and your observations when you ran it that way. .. if setting framerate to 45, was that with also setting OXRDT to 100%, MR disabled, and OXRTK disabled? Or was that also with OXRTK with NIS 100%, frames unlocked? And your references to resolution.. in game or ? Apologies, but I get bogged down in details sometimes.

Though I rarely install anything under c:/program files../ unless I have too, I saw it mentioned that having DCS under there can be problematic if you have it there.