Rapierarch

He is not. Meta implemented this feature, and provided it in beta for a long time and probably ED has dev access so they know it way before. ED says that they know it, they know exactly what's changed but they planned to implement it next patch. You can compare it to this. Just imagine MS introduces a new feature to Dx11 and all game vendors needs to implement a patch to their engine to be able to use Dx11 in the future. Ms pushes the update without no way of rolling back after announcement and public beta testing. All game studios implement it except ED. So noone is able to play DCS for 6 weeks. For a VR user it is exactly like this.

Vibration is caused by upscaling of video stream on the headset from 2152pix to 3664pix. I have no idea why you set it like that. Put the encoder resolution width to 3664 which is the native res. Since you are there set the distortion curve Low to get sharper more defined visuals.

This. This will be big if ED does not push a hotfix soon. I was lucky to take action before the update.

This affect oculus pc app being OpenXR runtime to use the headset. It does not matter how it is connected to any headset afterwards. So riftS is also effected.

I had it with 3950x

Ouch My dreams

Yes, but with DLAA or MSAA 2x too there were no shimmering. I have never seen it since F-1 is released.

Quest2 and everything is fine here. Never had the problem described above.

I always imagined Nick Gray as the voice of Mosquito AI.

With the AI navigator and drift recorder also added this will be the first time in the history that a real mosquito combat flight will be simulated.

Oh really? I have never used the vanilla version bundled with the game. Just after update replaced it with the latest one. Is the original one that bad? Wow! that explains the critics.

Since MT preview release I don't see that preload slider in game has any effect. It should not matter. You do not need preload distance unless you are still running on mechanical HDD. PS: if you don't quote my post or tag me I don't get notification. I saw your question by coincidence.

IT is an edit in graphics.lua. At the beginning of the file there is a statement with 2 parameters : Precaching = { around_camera = 50000; around_objects = 10000; around_types = {"world", "point"}; preload_types = {"map", "world", "mission"}; } You need to set around_camera and around_objects both to 0. It is a dynamic setting active during the whole flight. Before MT release it used to have a huge impact on RAM usage too.

I have an update on this matter. I have recently upgraded from 3950x to 5800x3d.(1 week ago) with 3950x I had 100% loaded one core which I needed to turn off in affinity list and turn it back on immediately to make it work at normal load again. That was the solution. With 5800x3d when I turn off the core which runs at 100% at start that 100% load moves to another core. I cannot solve that 100% load problem in 5800x3d. It has a different behavior. FYI.

Upgrading from 3950x to 5800x3d brutally made it smooth in my case. I installed it yesterday and so far everything I tested was wonderful. It is too early to conlude something since DCS still needs to create shaders but in a few days it will be ready. DLSS performance AF:16x SSS: on (my shadows mod relies on it) Terrain shadows: default Shadows: Ultra (my own mod) rendering 5000x5000 per eye. quest2 Precaching disabled Render clipping set to 120km (or 100km probably I need to check what I set last time) mirrors clipping 15km Viewing distance extreme multiplied by 1.3 Lodmult: 0.4