johnbowzer

You need to have far vision corrected, but there is also this FROM HONSVR: The Pimax Crystal / Crystal Light VR headset has a shorter focal distance compared to other VR headsets, approximately 1 meter. If you wear progressive lenses or reading glasses, please consult your optician for a prescription tailored to a 1-meter focal distance. If you use single vision glasses (one prescription for both near and far distances), you can use your existing prescription directly.

I think DLSS does not work on GTX cards, which your signature shows?

No. That is the issue. None via cable link. Only in vdxr. I am going to try what Qcumber mentioned, no AA in vdxr, see what happens.

Tried both 72 and 80 in both link and vdxr, and can get full or almost full fps without repro, and tried with and without repro. I get the ghosting in vdxr always. And it is looking out front, or to the side at other planes. And it seems to be a DCS thing. No ghosting in MSFS2020 with VDXR. I set up a scenario to get a fast pass with another plane and no ghosting. I realize there are many variables we deal with, but I have tried many things to isolate. But no joy to this point.

I have been experimenting with the Q3 for months on and off with both oculus link usb, and vdxr wireless. And numerous multipliers, etc, like mentioned here, on both platforms. One thing that I get with vdxr no matter what, is airplane ghosting. Any fast mover going by, even on its six when it banks away hard, its like a second bandit in tow. Terrible. And this with other modern jets, Korean era and WW2 era bandits. I get very little, mostly none of that with oculus link. No different using the new DLSS4 and new driver. I retried various tests after setting up DLSS4 but same thing, and I figured that would not make a difference.

Been following this thread and another one about DLSS4 and presets, like K. Might be worth checking this info I found on enabling it, which I did it. Waiting for comments on the other thread to see what others might find. Sure appears to make it much simpler.

I decided to give this a go, and found something I did not expect after reading through these threads and others in the forum on DLSS4 and how to implement and use/activate it. I first went online to get nvidia profile inspector and came across this page as well. It suggested that the other tools maybe were not needed. So no nvidia app, no dll replacement, and I assumed no DLSSSwapper either. My DCS is a clean install, original dlss dlls. I already had nvidia 572.16 installed clean, after DDU removal. I do not have nvidia app, dlssTweaks or dlssSwapper installed. So per that reddit page, I installed profile inspector, set the global overrides per this page, used the registry edit to see the DLSS info on screen, and launched DCS on the monitor. With settings using DLSS - Quality it shows it is using the latest dlss4 with preset K. I ran MSFS 2020 with DLSS set, same. This suggest that just the new nvidia driver is required, with the overrides needed via NPI, but that is it.

Here is F18 over Marianas and over Navada. With some aricraft over other maps the game ms will be as low as 2-3 ms.

Have not got the new update yet. But, do you feel you get better performance using H264+ at 500mbs rather than AV1 @ 200mbs ?

Thanks all. In VD streamer I use AV1 for Quest3, with 'automatically adjust bitrate' checked. Then in headset settings are Godlike, 72fps, default 200mbps, sharpening 100, SSW disable, SnapDragon checked. I can mostly get 70fps. Tried a few ingame settings, DLSS, and just DLAA or TAA. Those changes do not fix the behavior. I fired up Elite Dangerous for a bit and do not see it there. Seems to be a just DCS thing for me. Gunna keep digging. Man, simulating is stimulating. Oh, and in the VD Performance overlay I get about 45ms for latency.

I searched the forum and internet and I do not quite have my head around compression artifacts, so just what they are. I run an i5-12600K, RTX 4080. Using VDXR and 6E router at 2400 mbps. I have a fairly good image and 70-ish fps, but something I am getting in the headset are a flickering in the image, a flash, but not of light, the image gets a quick dark jagged visual. This happens just a fraction of a section at random, but can be every few seconds, or maybe not until after 10 seconds, and sometimes several flickers within a few seconds. It does not matter what aircraft or area. So I wonder if this is these artifacts, or something else. A different sim nevers get this issue.

Yup, for the Q3, I use RemoteDesktop, VDXR/Streamer, God mode at 80, and if I figure I want to have a longer session, I just plug in the USB cable to a powered port on my desktop, or my powered USB hub right from the start. I got 3.5 hours that way and still had a bit of juice left. Never pushed it to a battery full drain though. I had my G2 for 2 and half years. It was great. But after switching to Q3, and particalrly uisng VDXR, and to be fair I am running a RTX4080, for me it is significantly better.

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.