kzial

I had a similar problem few year ago, Playing offline was the solution (completely shutoff the network, unplugged). After some investigation it was the motherboard 'network optimisation' program that was causing trouble. Also putting the pagefile on another drive (even if you have an ssd) could help.

This is a reprojection artifact. The only solutions are to increase the fps or to change the headset (the reprojection algorithm is of different quality depending on the band)

Also dcs uses mainly two cores so being at 50% cpu means your are capped by the cpu power.

To my experience, the memory clock (ddr and cache) have a huge influence on fps. Be sure to put them at the best value

I had this kind of tracking problem. It turns that it was due to my USB cable extension. I've identified the problem by looking at the windows error log and saw USB disconnections.

iirc there is a folder with the 7 first missions of the campaign in coop version

Before buying a new rig you could do some optimization. The goal is to identify the bottleneck (there is always one) : CPU raw power, gpu, communication (ram speed) between then and heat management. You should stick to core 0 and 2 for games as they are often the fastest. Also in my case, the sdram frequency made a huge difference in VR as well as forcing the CPU in frequency (windows tends to slowdown them for energy saving reasons). Having a good heat dissipation is also primordial as your CPU will slowdown to avoid damage in case of heavy load. I hope it will help you to get the best of your rig.

There is an option in the graphics settings for the resolution of the inboard camera try to put 512.

You can try to update your motherboard USB drivers. Also try to test the headset with all unnecessary USB devices unplugged (sometimes the bandwidth is shared among several USB plugs) and make sure that the headset is alone on it's USB controller.

The version of the modules are linked to the version of dcs. So you have to take a look to dcs changelog on the forum.

There is a small knob to turn at the bottom right of the main panel to set the light on. Sorry I cannot send a picture right now.

You can turn on the uv light at the bottom right of the pannel. It helps a lot.

You can use thrustmaster target gui to map the F keys to the hats only when a modifier key is pressed (the paddle in my case).

It happens to me too with my Lenovo explorer. It happens when wmr looses track of your motion (the xyz axis are lost). Usually, moving my head around helps the camera to track my position back. If not enough I fix it by launching the headset setup or turn the lights on.

Just don't copy the model folder.