edmuss

When you're just on the threshold of switching between 45 and 30hz reprojection brackets the FPS shown will be averaged over a couple of seconds. It's quite possible that you're only just over the threshold for a second and then bounce back under it. Try increasing some settings as a test to see if it will force down to the 30hz bracket

Make sure to leave it unlocked in openxr toolkit, then if you drop below the threshold for 45Hz it will drop down to 30Hz which is equally smooth. It could well be a CPU spike causing the stutter. Turn off civilian traffic and drop visibility a bit to help the CPU along. Keep an eye on the appCPU frametimes when it stutters, I would imagine it's just DCS overloading the week CPU and ram. edit: use this when running DCS, it recovers ram very well and can prevent your machine grinding to a halt when ram is low. https://www.koshyjohn.com/software/memclean/

Try to reset the global open composite switcher to steamvr and then back to open composite. Swapchain image timeouts can be any number of things though, requests have been made to increase the timeout value but not made it's way though yet.

The only way to stop that is to turn on reprojection (which is currently suboptimal image quality in openxr) to smooth it out or beat refresh rate. What you're currently doing is relying on the runtime vsync to try to smooth things out, basically you're only displaying frames at half the refresh rate (45fps). Rotational head movements will feel smooth but fast moving things close by will be jumping. Beating refresh rate syncs everything together and the image is completely clear and all motion is smooth. At 90hz you're not going to do it but you have a chance at 60hz (if you can handle the refresh rate flicker), however you need to be consistently above 60fps otherwise it gets really uncomfortable relying on 30hz vsync.

About 40% I think, the display panels are 2160 but you need to render higher and mush the pixels together to account for lense distortion.

3160x3160 is the render resolution to run the G2 at 100%

The CPU can't process the data from DCS fast enough, 50% just shows that half of the cores are loaded. Imagine trying to force a river through a hosepipe, that's what DCS is trying to do.

In comparison to the rift s you're pushing approximately 540% the number of pixels at 100%. You will not sustain the same settings. You're also going to be bottlenecked by the CPU quite severely. Also ram is too low really, running mem cleaner when flying will help. Running a 3080ti I can get 60-85fps but I have a 5800x3D to push it along fast enough. Drop the resolution to around 2800 wide, reduce visibility, water and clouds to medium. Turn off the reflections and ambient occlusion and traffic to low or off. Have a look though my openxr tuning guide for some baseline ideas for setting it up and you should be good. You need to be looking at a motherboard, CPU and ram upgrade fairly soon though. edit: you also need to have your system in absolute tip top condition to make the most of your hardware. Follow Thud's VR4DCS guides to the letter and don't skip a thing.

DCS version doesn't matter, you still get the same differences between openxr and steamvr

350 queen bux here currently which equates to about 615 kangaroo pounds, that's including vat@20% though edit: I suppose they should be king bux now shouldn't they?

It is workable but you have to make compromises. I got pretty good results with my 3070 (a touch slower when stock than a 2080ti) and could generally keep 50-60 fps. If you're happy to use reprojection then you're laughing as you should be able to hold >45Hz with pretty high setting. I did overclock the tits off my 3070 so bear that in mind regarding the following: - With the 3070 I would run openxr at 2400-2600 wide resolution, medium textures*, generally medium settings and no msaa. This was without reprojection, enabling it I could push most things up a bit. If you use upscaling then you'll gain a bit more overhead, I could get up to around 80fps at best but I'm not keen on the aliasing/shimmer caused by the upscaling. *The 2080ti (11gb and 352 bit wide bus) will likely run high without problems but with the 3070 (8gb and 256 bit wide bus) it caused some slowdowns). With the 3080ti I can now run MSAA, higher resolution and high settings whilst getting around 75fps average. The current state of terrain shadows with 2.8 causes me a 4-5ms frametime hit so I turn them off, in 2.7 I had them on flat; the rest of my settings between 2.7 and 2.8 are the same and I have pretty much identical performance.

I'm generally getting 60-80fps in the KA50 currently, openxr running the G2 at 2800wide with foveated rendering (which unfortunately doesn't run on AMD for DX11 DCS) on quality/wide preset. Settings below were for 2.7 which was faster as such I have had to drop terrain shadows to off (as currently they give me an unacceptable 5ms performance hit) but everything else is the same. I run the headset at 60Hz with reprojection off so I'm consistently beating refresh rate apart from on marianas where I get about 55-65fps in which case I switch to 90Hz and suffer the slight vsync ghosting edit: note that this is SP only not MP

If it's VRAM related, try running openxr, it's much better on vram utilisation than wmr4steamvr

I just glued little bits of plastic to the keys

That all looks about ok, I can't explain why the reprojection should be dropping out unless it's simply lags due to the CPU bouncing around. It should hold a pretty steady boost clock unless you're thermal or power constrained?

FSR introduces lots of shimmer unfortunately, I've found equal performance and better image quality to simply reduce the resolution in openxr and use MSAA to smooth out the aliasing. In all honesty I'd leave your settings as is apart from the secondary shadows, terrain shadows and MSAAx4. Turn off FSR, drop the resolution down to 2600-2800 with MSAAx2 and see how you get on

Turn off all software overclocking tools and set it up in hardware via bios

Both are software solutions only and independent of hardware. There are differences in image because of how they handle the upscaling/sharpening but it's largely the same performance wise and personal preference with regards to the image.

Kill secondary shadows and drop MSAA to 2x, flat terrain shadows have the same hit as default for me, I've currently got them turned off. If you're running those settings at 100% G2 resolution I'm not surprised it's slow

I get zero time to load textures if there's no slot choice involved, if I have to choose a slot then it's typically 3-5 seconds to load it all in. This is SP only, but any missions where it loads directly into the cockpit there is no waiting for texture load at all

Your analogy is pretty close It's odd that it works in one scenario but not in the other. Unless for some reason your GPU isn't pulling enough to keep the reprojection engaged but you should be able to easily. Try resetting all of the openxr toolkit options, ensure that turbo mode is definitely off if you're using reprojection and have a play with locking and then unlocking the reprojection rate. Turn on the developer performance overlay as well as the WMR one and keep an eye on postGPU frametimes as this is what displays some of the overheads caused by reprojection. If it's spiking to 8-9ms for example then that would likely manifest as a failure somewhere in the reprojection and it may simply be turning off. For reference, my 3080ti uses about 3-4ms overhead if I turn on reprojection.

The dampers I picked up for my stick (which proved to be ultimately a little heavy for the usage) aren't all that big and could be packaged into the side on a stick extension pretty easily. The damper force could be changed by drilling out of piston ports, they're fully serviceable so no issue to dismantle them. I played around with different oil weights but didn't get so far as drilling the pistons. I'm going to reutilise them on the rudder pedals and the collective I'm planning. They cost £12 each on eBay and whilst cheap they work really well for what they are. I modelled them up in solidworks (as per attached image), the body is 100mm long and free stroke is about 55-60mm, overall length is about 200mm.

The desktop app will set a global resolution (either by the default VRAM calculation or manually overridden) and the ingame toolkit will then override this if set. The two are not cumulative, it's either one or the other

Yeah, it can be a bit hard to read, especially at higher resolutions! It will be red any time that you're below refresh rate, the fact that it's not blue at all would indicate that you do have reprojection off. Generally the only time it will be green in DCS is if you're: - running super potato settings on a free flight mission running the headset at 60Hz and getting more than 60 fps / less than 16ms appGPU running a 4090 with a CPU man enough to keep it going Try dropping the resolution to pull the frametimes down, MSAA should quell any shimmers at the cost of 2-3ms frametime; in my experience low resolution + MSAA gives better performance and image than high resolution alone.

Not quite If you leave the resolution override on default in the openxr tools desktop app, the resolution will be set at a recomended value based upon the amount of VRAM you have. For my 12gb 3080ti it's a little over 3100 wide, for my 8gb 3070 it was about 2450 wide. From memory the calculation is based on three back buffers with 4xMSAA applied to them shouldn't be more than 10% of available VRAM. If you override the resolution on the desktop app and set it to 100% then it will be 3160 (or there abouts). You can see the current set resolution on the second tab of the openxr tools desktop app.