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

Thanks @-Rudel- for the clarification.

@Moezilla I don't know how their bugtracker works but I believe since you have posted the bug you had some options like asking further questions. LOD issue is recently closed. Did you get any feedback about implementation of lods?

My god it affects all the way to the threadripper. I wonder what DCS skips causing it to run better in forced restart. I didn't try it myself but was thinking that might be an intel thing. But if it runs same on the dripper we may call this proven to be replicable at all systems. Edit: It has no impact on my system. I have a modded graphics lua for example precaching is disabled mainly. Tried it various times. No impact at all. 3950x 96GB 3200Mhz 4090 Quest2 72hz 4800x4800 per eye via quest rift link.

I have already tried it in various settings. I have no change at all. It just needs to be above target fps.

Nope, I use 0 software. I would even not buy any hotas which needs a software to run. Nothing Just DCS and Oculus running. Since I don't play MP not even SRS is installed. Ehm. Are there 2 different control settings for CW and normal. I actually never flown the CW I have this problem also with BF-109 only those 2 modules but problem manifests itself more with spitfire. I'm clueless actually. That's the weirdest bug I have seen so far.

They are porting an existing game which still has bits and pieces from 25 year ago as a matter of speaking. They are also adding new features to the core meanwhile. And above all they are not working 5 years on it. Work probably started much sooner and probably last 2-2.5 years it is going with full momentum. Since they are not building something new. There is a lot of lost work due to port fails. And also unforseen tasks like rewriting huge portions which they thought they could port without a problem. You can imagine that they are restoring the colosseum to a modern sports arena without losing its soul aesthetics and quality.

Когда мы можем ожидать превью Vulkan?

When it happens you visually see that. You are halfway pressing the rudder but rudder goes full deflection and pedal does not move any more in the cockpit while you can still keep moving your rudder. Controls setting still shows your input half deflection and output is also same. I have no curves in rudder. When this happens I immediately set the saturation 50% to fix it. Then it fixes itself in another flight so I set the saturation back 100%.

I wasn't sarcastic about this one. I really find it impressive. Especially this is happening in real time render not in an offline enhancement filter.

Wow DLSS is attempting to fix a render problem in raw output. What a time that we are living in