Massive stutters in Battle of Normandy Career Mode

[gydaveb]

I have a pretty robust system... Ryzen 9 7950X, RTX 4090, 64 DDR5, SSD. I use the Quest 3. In the Battle of Normandy Career Mode, flying Breakthrough from the Beachhead in a P-51, I get so much stuttering, low framerate, etc that it is basically not worth playing. Does anyone have any magic advice to improve on performance and make the career playable? Any settings recommendations or anything? I'm a very experienced flight simmer, and have another modern combat flight sim up and running at a rock-solid 72 fps despite it's history of poor performance, but I have to admit I'm frustrated in my attempt to get satisfactory performance out of IL2.

 

Thanks for any help in advance!

 

*edit: Should have mentioned... I am using OpenComposite to bypass SteamVR and just use OpenXR.

Edited January 27, 2024 by gydaveb

[BOO]

Im not a VR player but from Rhineland onwards the game suffers from assets loading in heavy scenes (where the games stutters until everything is is in the memory. This seems to stem from stuff loading in "Chunks" as opposed to individually based on distance from player. Normandy seems to have taken that and run with it with things such as barrage balloons linked to moving ships also adding to the load etc. That was my experience anyhow.

 

I have a system that runs GB in 2D to a point where, if i wasnt limited by vsync, id cap the fps to same wasting power, yet if i play a beachead scenario its a stutter fest. 

 

I dont think there is a magic bullet other that trying to reduce the visuals to the point of pointlessness but its been a long time and i may be wrong. 

[firdimigdi]

Sadly it's a case of this:

 

 

If you are willing to jump through some hoops, this is what I do for smooth "singleplayer" campaign gameplay:

 

On my 7950X3D I run the game and VR software on the 8 3D cached cores and a dserver on the other 8 cores. Then I setup PWCG to generate a co-op campaign and join it via multiplayer (hence "singleplayer").

 

Ridiculous as it is this shows that it's not a matter of processing power as it runs perfectly fine once the AI threads stop blocking the main thread since they are forced to run on the cores that the dserver is limited to. Needless to say that a singleplayer mission generated using the same parameters results in stuttering as soon as a few AI units show up.

 

The downsides of this method: extra steps, no pause. The upside: pals can jump in and play the campaign with you at any point.

 

Edited March 9, 2024 by firdimigdi
typo