edmuss

Out of interest, is there any visual clarity improvement with openxr in comparison to the oculus runtimes or is it just a bit faster?

Do you mean openxr runtime vs oculus runtime? I believe that there have been improvements reported when using the quest, I couldn't say for certain. Easy enough to install openxr, set your oculus to use openvr instead of oculus and test it out, if it's no dice then switch back to the oculus runtimes

Cannot be overstated enough! Ignore everything you've been told it's well out of date.

Only the index finger is active in DCS so the middle finger is never going to do anything; I make a fist with my index finger extended and it works perfectly just about all the time. IR interferance/reflection is what stops it tracking the fingers nicely; I've written about it a couple of times in this thread, have a look back and see if any of the workarounds help

Awesome that it's opened up so much extra performance! To alleviate the performance tanking try to reduce some settings that eat up VRAM, that would mainly be textures and shadows I think. Also worth while looking at lower texture mods, things like the tree mods by @Taz1004 reduce memory usage whilst looking better. Once you've gotten the ingame toolkit menu to load then you'll have access to FSR upscaling which will unlock another chunk of performance. I'm not sure of ins and outs of getting the toolkit to show in the quest but it's possible.

Mines hotter than the 3600 @4.3Ghz by about 10°C on load with the L3 cache in use (in DCS or small FFT runs in prime95), gets up to aron 75°C, it idles at 33°C; this is on air. I only play in VR or 1080p because that's what my monitor is It's certainly a very focused cpu and has a rather niche place, but if AMD can solve the heat issues and incorporate it into the newer generations then they're going to be monsters!

I've not experienced the water drop effect in SVR but it's quite apparent in openxr, hopefully it will be improved upon. It's the same for nvidia as well as AMD. I run without reprojection and sit at 60-80fps, it ghosts a little in certain scenarios but generally it's plenty smooth enough, I'm flying low and slow though so that might make it less obvious. The hefty drop is to do with the overheads needed to make the reprojection work. Using the openxr dev tools performance overlay you can see app_GPU and post_GPU, these are the time for the VR render and the time for the overheads respectively. Basically add the two together and that should dictate which refresh rate fraction bracket you're sitting in. 20ms app_GPU + 5ms post_GPU = 25ms (40fps) which means you've missed the 45Hz bracket (half of refresh rate) and it's dropped down to the next bracket which is third refresh rate (30Hz); this is why you appear to have suddenly lost a whole bunch of FPS. There also needs to be considered is that the refresh rate brackets get progressively smaller each time (specifically 45/15/7.5 Hz gap between brackets) so the reprojection overhead eats up a much larger proportion of the available bracket. I see the 30Hz bracket as a bailout and you should ideally tune to keep in the 45Hz bracket for the majority of the time.

I've never used the skatezilla app, just the ED supplied batch files (on the FAQs section of the website if you don't have them) to do the update/clean/repair; I do use standalone though. You can convert steam module licenses to standalone licenses (but not vice versa) so apart from the faff of downloading the latest version again it's not a problem. If you're not using the open beta version of DCS I'd recommend you do so as there have been a number of VR performance improvements (couldn't tell you what they are but FPS has improved recently).

It's one of the biggest threads in recent times on the VR forum

It should work just fine, stick with it as the benefits are pretty considerable Have a search through the thread for the crash error and you should find a fix.

There's hope yet but it will involve making some compromises DCS VR is a fickle beast and it's possible to generate relatively smooth gameplay (certainly in single player) with moderate hardware; however it is not plug and play and there is a lot of time to invest in tweaking. Jump into the VR subforum and have a look at the openxr thread, intended for wmr headsets but it has performance and functionality benefits over the other runtimes. Are you running the oculus or steamvr runtimes? With the Q2 you might be struggling a bit at full resolution, however with the openxr runtimes you can reduce the resolution, apply upscaling and foveated rendering, all of which will claw back those precious MS of frametime. edit: the frame rate tanking in VR seems to be linked to low VRAM, I have 8GB on my 3070 and in steamvr it's a constant issue, the first flight will generally be ok but subsequent flights will kill performance till DCS is restarted. In openxr the problem is almost entirely eliminated due to much lower VRAM demand from the renderer, I think it will be the start of improving things for yourself in VR.

Yeah something seems a miss because it should request a VR restart for any resolution change, enabling/disabling reprojection or enabling/disabling upscaling (FSR/NIS). Perhaps try resetting the options from the toolkit desktop app?

The toolkit resolution override will supercede the desktop app so I'm not too sure what's happened there. Is it a repeatable drop in performance (so it goes back up if you remove the OXRTK resolution override)? Could it be something else external that's nailed your framerate? edit: Jabbah on the open composite discord had just raised the point that the latest windows update has forced HAGS on which will affect performance. Check that it's off

My main issue is usually forgetting to turn off pitch control and it sits there bobbing up and down; trying to time the rocket launches when it's oscillating never works Like you say more practice and a longer run in should make things run a bit better. Hours and hours of bombing around in helos in arma3 seems to have prepped me reasonably well for general flight, it's FM is actually very much like flying the shark. With the better rudders it just feels like it goes exactly where I want it to.

Yes you will but I wouldn't bother unless you're already on the am4 platform (which you're not). I would look at getting new motherboard and processor once the new AMD processors have come out and there are comparisons between the Intel 12th gen vs AMD 7000 Obviously the X3D is the only CPU currently with the monster L3 cache that DCS loves so much and whilst I suspect it will make an appearance in the 7000 lineup I don't think it will be on initial launch. I don't know how much performance delta there would be going up to a 12th gen Intel with your 2080ti but I've certainly seen a healthy increase with my 3070 (which is marginally slower) simply by switching to the X3D.

Yeah I'm holding trim whilst manoeuvering (been watching a lot of @Volk. videos) and I do normally run with some of the AP channels on (bound them to the trim hat on the warthog stick) but I'm finding that even without the AP it's really controllable now I've got such granularity on the rudder axis. I'm getting to grips with the vikhrs, again having such large travel on the rudders means it's really easy to line them up. The cannon is super easy and I suck with the rockets

Resolution override sets the resolution of the render in the headset. At 100% render resolution the rendered image in the G2 is 3176ish pixels wide, reducing the number will increase performance at a loss of visual clarity, inversely increasing the number will increase visual clarity at a loss of performance. How much you increase/decrease by is personal choice (if at all), play around with it and try to find a sweet spot, personally for me I find 2800-2900 wide to be the best compromise of performance over quality. Motion reprojection is a much more complicated subject and is concerned with producing smooth movement within the headset. In general terms, in order to have perfectly smooth movement the render speed (Hz/fps) has to match or beat the refresh rate of the display panels (this is typically 90Hz/fps). However, particularly in DCS it's hard to achieve 90fps on higher resolution headsets like the G2 without having to reduce settings massively which defeats the object of having a high resolution headset. What motion reprojection does is when your GPU can't achieve refresh rate it reduces the frames rendered to a fraction of the refresh rate (in the case of openxr it's half, third or a quarter) and uses the previous and following frames to be rendered to generate a synthetic frame that is then interpolated in the middle to make it feel like your getting 90Hz. This is all wonderful except sometimes the synthetic frame generated doesn't perfectly match up and causes visual distortions in the image, this is pparticularl apparent on the edges of ccockpits and rotor/prop blades where you have something moving slowly relative to something else. It's personal choice to use it or not, if you don't and you can't achieve refresh rate then you will suffer from some image ghosting when you translate your head (slide it left/right/up/down/forward/backward) but rotational movement should be smooth, however you will suffer from no visual distortion and clarity will be better.

Were you using the default resolution in the openxr desktop app before overriding it in the toolkit? If so it will have automatically set the recommended resolution based upon the amount of VRAM you have. For my 8gb 3070 it's about 2450 I think, it equates to about 62% render resolution. The number is calculated by the size of the three frame buffers with 4x MSAA applied should be less than 10% of available VRAM.

Mine is installed and running with the 3070, like for like settings in still seeing fps uplift across the board, especially on the lows. A10c easy instant action peak fps is up about 10-15% but the average is consistently higher. KA50 meggido to haifa tour gains 25-30% more fps on the ramp and consistently 20% higher in general flight. Both of these are lightweight missions with regards to the CPU and it's still giving a very healthy improvement on a saturated mid range GPU. I set up a quick mission with 475 units and CPU times according to openxr performance overlay have dropped from 120ms to 80ms and it's almost flyable! Coming from the 3600@4.3ghz to the 5800X3D (@4.45 consistent boost clock) is a significant improvement edit: further testing, KA50 flight low overland on Marianas is giving 50fps, was lucky to get 40 before!

Best to provide some more info to try and troubleshoot, what settings do you have in both DCS and toolkit and what fps are you getting when it's ghosting? You can transfer steam modules to standalone without any problems, just means downloading it all again. I think there's a guide on how to do it in the FAQs section of the ED website.

I think it's in the system tab under override resolution. 100% resolution on the G2 is 3176 wide, especially if you're running MSAA you should be able to drop to 2800 wide without any significant quality loss but with a fair improvement in performance

Are you able to get the OXRTK menu to appear in the headset when you're in DCS? I rebind the default keys in the conpanion app to Ctrl+ arrows rather than F1-F4 as it seems to work better; I use Ctrl+Down arrow to open up the menu. Follow my rough outlines for setup on the first post of this thread to figure out what would suit you best and then continue tweaking until you have smooth experience that you're happy with. Given your hardware (being pretty similar to mine) I would start with the following as a baseline in OXRTK and tweak it accordingly: - Override resolution to around 2600-2900 wide on the G2. Enable FFV on quality/wide preset (the slowest but best looking). In DCS run medium/low textures to start with (you can always turn them up if you have GPU headroom), low/flat shadows and set the rest to medium. I would disable MSAA unless you need to use it. Try it with and without MR, it will be smoother with but with artifacts but performance is generally better without it; you are relying on openxr vsync to keep it relatively smooth, it's not as good as MR or achieving refresh rate but I find it perfectly usable in the 55-75 fps range that I get.

That should start up DCS in openxr without any problems. Start up wmrp first, then start DCS from a desktop shortcut linking to the DCS.exe and it all should be fine. Steamvr shouldn't open in any instance and it shouldn't open itself.

Mine is arriving tomorrow

Yup, lefuneste updated it shortly after openxr was shown to be useful for DCS