shadowborn Posted September 23, 2023 Posted September 23, 2023 Hi. This is a quick "war story", maybe it can help someone. I ran DCS about a year ago with a HP Reverb G2 Rev. 2. DCS crashed a lot. At the time this had two reasons, which made diagnosis cumbersome: One, the cable shipped with the G2 (even the Rev. 2 purchased directly from HP) was still faulty. HP shipped me a new one, this resolved my issues with OTHER games in VR. Not with DCS. The DCS crashes only subsided when created a Windows page file (I had initially operated under the assumption that "32 GB ought to be enough for everyone" (miss-quoting a certain MS founder here), and that no swap would be needed. My DCS demanded an extra 10-20 GB of swap or so. Then it ran, in VR, mostly fine. Some days ago the crashes came back. What had changed? I had begun to fly in VR and multi-player. It would appear (my) DCS demanded more than 50 GB of total virtual memory to be the sole, single player on a Nevada map with a handful of AI assets. Madness? I ordered another 32GB of RAM (more RAM to the airplane gods!). Alas, in between the order and the shipment arriving, I solved the problem. I had custom graphics settings set initially for the PC screen and my RTX3080. These were set not THAT high. Alas, when I switched to VR, I left them in place as is. Before the RAM arrived, I did one thing: Reset my graphics settings to the "VR" preset. That solved my problems, the multiplayer Nevada mission now runs fine on 32G plus some swap (and possibly doesn't even need swap, I haven't checked). What changed? Good question. Unfortunately I haven't logged the old settings. I think terrain textures went down one step. My preload range was already set pretty low, I reduced it and the tree cover a bit more. That is all I can identify. Alas, if you have crashes in VR, or excessive RAM usage, the lesson here is to reset the FX settings to the preset, not leave them on "seemed reasonable for flat screen" settings - even if that gave more than 90 frames/sec even in VR. Over and out. 2 "I crash, therefore I am." A10-C II Tank Killer - AH-64D - AJS-37 Viggen - AV-8B Night Attack V/STOL - Black Shark 3 - F-4E Phantom II - F14 Tomcat - F-16C Viper - F5-E Tiger II - F/A-18C - Mosquito - Mi-24P - MiG-21bis - SA342 Gazelle - UH-1H Huey - Flaming Cliffs 3 - Supercarrier - Combined Arms. Caucasus - Mariannas - Nevada - Persian Gulf - Syria - Channel - Normandy 2.0 (I might have a module collection problem - send help!!) HP Reverb G2, Winwing F16EX, Orion 2 w/ F/A-18 Grip, VKB Pedals.
shadowborn Posted September 23, 2023 Author Posted September 23, 2023 Oh, also this: VR is AMAZING. Before you try VR, you THINK you know how it will be. It's so much more. I sat in the cockpit of my F14 / F18 / AH-64 etc. for (taken all together) hours gawking at the incredible graphics. The texture of a radar screen that now for a first time looked like actual glass, complete with layers of smear or fingerprints. I almost fell of my chair, awkwardly twisted while reading the label on the side of a headrest of an ejection seat. And by that point I wasn't even flying yet. VR is pretty epic "I crash, therefore I am." A10-C II Tank Killer - AH-64D - AJS-37 Viggen - AV-8B Night Attack V/STOL - Black Shark 3 - F-4E Phantom II - F14 Tomcat - F-16C Viper - F5-E Tiger II - F/A-18C - Mosquito - Mi-24P - MiG-21bis - SA342 Gazelle - UH-1H Huey - Flaming Cliffs 3 - Supercarrier - Combined Arms. Caucasus - Mariannas - Nevada - Persian Gulf - Syria - Channel - Normandy 2.0 (I might have a module collection problem - send help!!) HP Reverb G2, Winwing F16EX, Orion 2 w/ F/A-18 Grip, VKB Pedals.
Recommended Posts