RealDCSpilot

@Stal2k Any changes on your end after the patch yesterday? Terrain: improved background preload for less stutters Terrain surface textures: improved details at altitude for HIGH terrain texture option Terrain: improved loading resources and memory management Terrain: fixed excessively curved paths Terrain: fixed leak after destroying scene object

I've also had this off since it was introduced, tested it back then and found no real benefit. The occasional Steam VR crash still happened on my old 2080ti until i replaced it.

Just WOW!

Process Lasso has a couple more options besides cpu affinity like system priority class, I/O priority and an exclusive application power profile. @Dangerzone disable_write_track = true in autoexec.cfg minimizes extra disk activity, might be worth a try.

+1 Proper VR support would be great.

It's more depending on user's hardware and knowledge to get the best out of it and to get DCS run pretty good in VR. Another thing is that no HMD runs VR game resolutions at it's native panel resolutions (it's always higher, example Index: 2016x2240 per eye). I suspect the streaming (over WLAN or USB) itself as a performance trouble maker, because it has to use CPU power which could conflict with DCS's own CPU usage. Maybe he needs to try to assign separate cores to the streaming process to get a better result. That's part of "tinkering" and trial and error.

The amount of VRAM will definitely make a difference for DCS in VR.

I also use the tool "Process Lasso" to make sure Window's CPU usage runs at highest performance for DCS.exe and exclusively set separate cores to run SteamVR processes (vrcompositor.exe).

@divinee Okay, 7,7GB means that your VRAM usage is maxed out. But can you please be more specific about your page file settings? Did you just change the size from XXXmb to 800mb or did you disable it? Did you also try to change the size to 32000mb or more (best practice for the windows page file is having it set to 1.5x your RAM capacity and prevent dynamic size changing by setting the same size for min and max)?

Well, it's not DCS's fault. I would expect a lot of tinkering needed, if i try the game on a HMD that isn't even designed for PCVR in the first place.

Within the next 'two years'. And i've seen a lot of changes during the last 11 years...

Works now, thank you!

Oh no, they don't need to reduce the quality. Just more efficient usage of textures (resolution) and better memory management will be enough.

Yep, this will be very interesting...

Just to add more info to the topic: https://forums.eagle.ru/showpost.php?p=4528333&postcount=78

Just to add more context information: https://forums.eagle.ru/showpost.php?p=4528333&postcount=78

@Gunnars Driver This also maybe interesting for you.

@propeler Nice! Please inform me when i can order one device from you. :)

@f4l0 Just a tiny setback. If i choose the P47D-30 early version first i still get the script error. But if i choose the D-40 before that and switch to the D-30 the issue doesn't occur.

@walmis Wow, great!!! What a monster! @propeler and walmis What do you use for axis sensors?

It's just a simple guess, yes or no will be enough.

@Stal2k Would you mind to do another test? DCS is always a bit behind with the latest version of the openvr.api. Currently it uses version 1.0.10.0 while the official api is at 1.14.15.0. You can download the latest version here: https://github.com/ValveSoftware/openvr/blob/master/bin/win64/openvr_api.dll Just place it under \DCS_World\bin and backup the old file. This should rule out any incompability issues with the latest version of SteamVR. Maybe it is a bit more bulletproof in stress situations, maybe not.

Okay, now we get closer to the source of a misunderstanding. Please excuse my english, i have to translate everything and it's hard to be exactly precise sometimes. I have to make this guess here, the source of the problem isn't a bad line of code causing an illegal function call somewhere that leads to a crash, it's definitely not that kind of bug. You will never find a step by step procedure to nail it down with 100% certainty that a certain action caused the problem. To be affected by the problem you actually have to play the game in the field. Online, in free for all sandbox missions with other players. If you don't know what the "Through the inferno" missions are, than you seem to play DCS in a different way. I took a look into your mission and found a huge amount of units, yes, but also a lack of variety. Example, having 200 units of the exact same type will make no big difference in VRAM usage. It will just use the amount a single unit of that type needs. You will probably never really run into a problem if you just play DCS in "linear" type of missions, were you basically choose one aircraft, do your mission, finish it and the mission is over. Missions like "Through the inferno" are very popular online, because you can join them and do whatever you want. All the variety that DCS is providing is available there, you can choose every module, use every weapon. You can choose to train carrier landings in a F14, another group of players in A-10s is attacking an enemy airbase over 100km away, while on the other end of the map a player tries slingloading containers with a helicopter. These kind of missions are usually named "...freeflight...", "...training...", "free for all...PVE" etc. A typical online session can take 30 minutes or 4 hours, including switching to all sorts of modules, from jet to helicopter to WW2 aircraft. The server itself will always run 24/7. In these missions the problem is very common for some of us, it can happen after 10 minutes or after an hour. If you are lucky, you only get the frame drop problem for 5 or 10 minutes and it sorts itself out after a while. But since a couple of weeks, Steam VR crashes occur more often and it's not a new problem: https://forums.eagle.ru/showpost.php?p=4379001&postcount=3 It really looks like a problem of bad or incomplete memory management. Instead of clearing memory resources after i choose another jet, DCS just stuffs the next jet's textures and geometry into VRAM and then the next one and the next one until VRAM is full and then memory swapping starts, trying to sort it out somehow. Sometimes Steam VR is the weakest part in this, and crashes. The only way to prevent the problem to occur seems to be having a GPU with lots of VRAM, since i got my RTX3090 the problem never ever happened again on my end. DCS now uses a huge chunk of it, up to 17/18 GB.

That's exactly whats going on. Simply switching to another aircraft just adds data to VRAM without purging the unnecessary data from the former aircraft.

Back from the depths of the forum: https://forums.eagle.ru/showthread.php?t=236834