dutchili

I would like ground spawns to be visible (spawned) even if the slot is not taken. This provides the occupied slots to see more aircraft on the airfield. When people return from missions and exit the game, the planes disappear. This looks weird and removes the eye candy effect for those that are still to arrive.

Look at the nav distance instead of the slant range. It seems weird that B and F change in that way, but you shouldn't use slant range.

DCS loads more than needed and does not unload when vram is full. We can all experience this especially in vr. Alt-tab can get performance back but it doesn't work so good anymore in the latest OB. (Takes long to recover).

visible range really helps indeed and Medium is still sort of nice. I also have the stutters when looking 90 degrees left or right over cities. The FPS meter in DCS is not to be trusted in my opinion. Perceived FPS is not the same as measured/reported FPS. I suppose this is again VRAM, insufficient multi-threading for pre-rendering and synching between threats. Hoping vulcan is released soon and other improvements give us 2d performance in 3d.

This helps: (Not solve, but help)

I may have posted before, but this is a life safer!

null

Could this be it? 2023-04-30 18:15:22.068 ERROR EDCORE (Main): No suitable driver found to mount mods/terrains/marianaislands/assets/assetstextures.zip

@BIGNEWY: bumping this thread. Any plans on improving Marianas?

I don't need f10 for this to happen. This issue occurs in missions with a lot of visuals, like rain, custom liveries or lots of units. The issue for much worse since the patch before the hotfix . We have seen this before last year. Vsynch is off for me too. Dcs log doesn't show it Alt-tab for about 10 seconds solves it. But it usually comes back quickly. Perhaps related: taking off the headset results in permanent black screen in vr, non recoverable.

Interesting stuff!

+1 The dcs.log does not mention it, nor is there a crash log created. 'Crash' is not the right word for me. When you put the (oculus quest 2) headset back on the screen is mostly black and the white hour glass is showing its waiting animation. The only way to recover is to restart DCS.

Is you headset refresh rate set to 90Hz? If so, that defines the maximum. As longs as your displayed FPS is not lower, you can increase your graphics settings.

This pathc is going in the right direction. MP much more stable, improved my graphic settings (MSAA on in VR now :D). Keep up the good work ED. Looking forward to more threads and Vulcan so we can work towards 'max settings' in VR without hardware upgrades.

So the conclusion is that the AI was upgraded and always jamms once locked?

Here you go. MT, 2D, very reproducable. slant range.trk I go into lock, than stt (slant range goes to 99), back to CRM, back to STT, back to CRM. BTW: is there a location where the last flight is saved? I always forget to save the track...

The Viper shows a wrong slant range (99.0) in STT. Additionally the range on the radar is incorrectly set to 120 Nm Steps to reproduce: - lock a target (TMS up) within 40 Nm - Enter STT (TMS up) - Observe how the slant range changes to 99.0 and the radar display changes accordingly - When going back to CRM (TMS down), the correct slant range will show within 2 seconds.

I don't understand the question. Please elaborate.

Confirmed. Hid symbology can be out of sync in time. Same thing with the bombing solution que. It can now also move up again.

Hahaha. Good that your are honest and come back with this

Same here:

Did some more testing: non-MT performance is better for me, even with the ground shadows enabled. My 1ste core is totally maxed out in the MT version, while is have play room in the non-mt version (single player, 1 enemy plane). It seems the total invert of what one would expect.

i just fixed it for Oculus. Previously i had installed OpenXR tools for WMR to get the openxr runtime. I now uninstalled it and used the '--force_openXR' parameter in steam to prevent using OculusVR. In steam i launch DCS with the 'MT preview' option. The in-game fps counter now shows the CPU/GPU bound text which confirms it is working with the MT version. Performance i quite comparable to non-MT....on my i7 and RTX 3070. Was expecting a lot more, but apparently there is still to much going on on the main thread.

Steam always launches ...\bin\dcs.exe, even if you use a shortcut to the other .exe Help is needed from ED.

- Steam does not provide an option to launch the MT version in VR - shortcut "\Steam\steamapps\common\DCSWorld\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR" results in Steam pop-up to approve the launch options, then simply runs DCSWorld\bin\dcs.exe @BIGNEWY, please provide guidance for your Quest 2 customers