dutchili

I bet it has to do with the networking, because that is the difference with SP. Not the internet connection, but the way the data is processed/distributed and problem not asynchronous.

I just discovered it all doesn't matter in MP. I get 60 fps in 2d with everything maxed out. In VR i get 16 fps on the ground with all settings on the lowest value, while I can run them maxed out in single player.

I have the same issue. I decided to stop fooling around with settings and just go for the latest FHolger performance kit. Works immediately. https://github.com/fholger/vrperfkit

Yeah, multi-threading ! More benefits that DLSS given where we are now.

Two parameters that lead to this issue are: Slow server connection (from any of the connected clients) and custom plane textures. @BIGNEWY Happy memory leak hunting

Same here with Oculus Quest 2. For me, this problem started at the beginning of the week after: - updating windows 11 using H2 release - updating Gerforce 3070 driver The problem seems to fade after a few minutes and primarily occurs when looking to the far left, right or down. In general (VR) performance is down after yesterdays small update.

Thanks. Did not find that one.

In version 2.7.18.30348, the antenna elevation is not always displayed correctly. It can be 'stuck'. The elevation can be changed, but the change is not visible until you press the AA master mode button twice. Seems to happen after unlocking a target.

You are not alone. The CPU/GPU load is too high in the multiplayer scenario (and can be too in high in single player) Reducing the load can help. Lower game settings, but also a lower rendering resolution in the Oculus settings. Note that can go all the way down to 0.7x, which gives you a huge difference in performance (a minor to moderate resolution effect based on the setting). With quite a similar system, i have in-game PD at 1.5 and Oculus resolution at 1.0 for 'oke looks and. oke performance'. I do get the occasional FPS choke which can be solved by putting the headset down, alt-tab, wait af few seconds, continue. If i set oculus resolultion to .7 i don't have that issue. Still need to find something in between.

I've noticed that when changing the antenna elevation, the search altitude is not always updated on the FCR. Pressing the AA master mode button fixes the issue. I think the issue starts when breaking a lock. I noticed in multiplayer.

Thanks for adding the nuances!

Multi threading implies multi core. Normally the operating system decides which core executes a thread. If you have a hundred cores, the OS may decide to use them all. For performance expectations: running a mission from a local server (same pc as you play on) gives you a nice preview for just the ai being run in a different thread. The impact is huge. Just try it. When more things are run in parallel the game might show the same performance as Solitaire. I am not involved in ED, nor DCS development, just an ex-programmer who loves the performance effects of multi threading.

I've tried the server too. It helps, but a DCS Liberation mission in Syria sill s....s

It's is not your CPU. It is the amount of work your request one core to do, which is too much. So lowering the settings, number of AI etc will help you getting more FPS. But still, you entire CPU (all cores) can do much more, so hopefully ED will priority multi-theading/multi-core to get the most of our CPU's and delivery excellent VR performance.

It is really time for a performance upgrade of the game as we can't simulate proper missions . Multi-threading, multi-core. Come on ED, hold the features and focus on the core. @Flappie @BIGNEWY VR could have the same performance as 2D if the hardware is used properly. And 2D could be much smoother too.

First observation: well noted. The center of mass is behind the mid point, that is why Second observation: when the gear is down, controls are less sensitive.

Stutters seem to be caused by delays in network operations, either 'to the internet' or between PC and headset. For internet: check your ping to the server (in the multiplayer screen). Forget anything above 100 ms. Also, the more users on a server the more data that must be transferred. Above 10 users per server you will usually see worse performance Between PC and headset: the oculus app can check the actual performance. Not every USB-C cable is a fast cable. As for the game and Oculus settings: - shadows on Low will help you - water on low will help you - Clouds on Low will help you - Ansitropic filtering: just turn it off - On the VR tab: set Pixel density to 1.5 for your pc - set resolution in the Oculus App to 0.8 for your pc Of course you want the highest possible resolution, but I've found that lowering this setting instead of increasing it, will give you better game performance and a smoother picture. Unfortunately the super scaling is done by the GPU and not one of your 'i have nothing to do' cpu cores. - In Oculus Debug Tool i have set Link Sharpening to TRUE, to increase the crispyness of the picture. This should give you 36 FPS @ 72hz as a minimum, which is good enough in VR, even in multiplayer. (syria map: 20 fps on the ground, 36 above 5000 ft) I do like the graphics more with PD set to 1.8 and Oculus Resolution set to 1.3, however, that will not work if there is any scripting going on or multiplayer gaming.

I can confirm this is happening sometimes in the current beta (3/8/2022) when using VR. It is unclear to me what the reproduction steps are. It seems random.

Unfortunately the toggle is not even a toggle. I had more luck with moving the cockpit camera forward to improve perceived graphics quality of the cockpit.

Despite other info on this topic I can't get the zoom to work. Toggle zoom and spyglass work by the push of a button or key, but 'Zoom in' and 'Zoom in slow' don't seem to work. The reason i want this to work is because it will get rid of some aliasing. Other suggestions to accomplish the same goal are welcome too. (please forget about MSAA and other in-game settings for that).

In the attached mission, i can see the F-14's from my F16 though the datalink, but not the F15's after their take-off. How can i fix that? group testing.miz

Set textures to medium in dcs and ground textures to low, cockpit to 256. Stay away from skins. The problem appears to be related to texture memory. Alt-tab with the q2 of your face usually fixes it within a few seconds.

In my case there were no bounds, and therefore erratic behavior (sudden stick up input)

A similar issue was seen with multiple usb controllers connected. In my case a Logitec g29 wheel. Disconnected, reset the pc, issue gone.

In latest OB: maverick is very blurry compared to TGP image