divinee

9L said at the FB that end of march-early april..

No matter which version. I've had those steamvr crashes since ~august/september and i've had almost all possible versions during that time.

Big +1

+1

Steamvr and wmr both still run normally after blackout, no errors?

Are you sure? I think you are correct with that the latter is much lower resolution but i think you mixed up those samplings or i didn’t understood correctly your explanation. PD in dcs just multiplys resolution in X and Y axels like if you have 2160x2160 resolution and put 1.1pd in dcs, resulting resolution should be 2376x2376. So going from 1.0 to 0.5pd is not 50% reduction in pixels, it’s a lot more. Steamvr SS% is changing the amount of pixels and then going for example from 100% to 50% you will get 50% reduction in pixels. Please correct me if i’m wrong, but i’m quite certain it’s that way. G2 per eye is about 2160x2160 in steamvr SS 48% and in 100% about 3300x3300. If it’s linear resolution it should be ~4300x4300 in 100%.

That’s not only for 30-series and there are also steps which affect steamvr native sets. For example deleting steamvr settings file which is what i’d recommend for you to try. With wmr glasses that problem is just pronounced because steamvr-wmr eats more vram than steamvr native sets..

Try these steps

+1

I also had same kind of memory issues and i found that in task manager details tab, one of the steamvr processes had ”high” priority. I changed that to normal and after few days of testing i haven’t manage to get ram usage over 28gb anymore in any situations. I play _very_ big PvE campaigns with syria map.

You shouldn’t need boundaries. Boundaries are meant only for roomscale games so you don’t hit anything. First check that your room has good enough lighting. Next check that you don’t move stuff too much without clearing environment data. Inside out tracking stores data of your environment and if you move stuff too much, tracking doesn’t know your position anymore and switches to 3dof. Go to wmr settings and clear environment data. Then teach new seated position (or new standing position if you play roomscale games) and check what happens. Also check that your glassses are connected to usb3.0 port. In some cases 3.1 can cause problems.

Seems to be quite common problem nowadays. Did you happen to press F10 or F2 when that happened and do you have 8gb or less vram? Here are some links to same kind of problems (which i’m sure are all related and there’s lots of more. I only scratched the surface with these links). Any of these match to your symptoms?

In single player? What kind of scenario because that’s insanely lots of supersampling for 5700xt? You are running about ~3000-3200^2 px per lense which is about ~90-95% Steamvr SS.

Have anyone tried to reinstall 20H2 version of Windows? I'd be curious to know if it helps with random fps drops and problematic memory handling before doing that by myself I don't want to revert back to 1909 because with 20H2 there came corrections for barrel distortion and general image quality improvements for G2. Edit: Sorry for the little hijackin of the thread..

Of course there are ways to find out the altitude of certain point and i’m aware of those. It just doesn’t help with HARMs because different systems should communicate together and it’s not that simple. If it would be that easy, why USAF even bother to buy HTS for their vipers Hornet doesn’t have systems like HTS which give HARM accurate target data straight for ”PB” equivalent mode which allows it to loft. Block50 Viper is just designed for sead, hornet is multipurpose striker.

I don’t know about the 3D world model but if we’d had that kind of things, the waypoints should have altitude data automatically just like A-10 has. Hornet knows it’s position by gps/ins and barometric altitude which you correct by changing pressure setting. (Edit, also radalt but i’m not sure if that is used at weapons employment)

Harm doesn’t know the distance to the emitter because it doesn’t know where the ground is at the point of the emitter. If you change the altitude of the emitter, the distance changes. Hud also only shows the direction. edit: also if i understood correctly hornet’s harm implementation is simplified and should be more like HAS in Viper..

Is that shared memory handled by game or by nvidia and dx? Rolling back drivers doesn’t help so my guess is by the game. @BIGNEWY or @NineLine can maybe inform that if we are up to something? Because if ED is already aware of this problem we are troubleshooting for no reason I installed those drivers from Mustangs post and they seem to make small improvement. Not absolutely sure but feels like that shared memory is clearing better. Can be placebo so we need testing results from another users also. @glide good to be help

I have to try that, TY Mustang for the tip! I managed to backtrack that memory leak a little bit and it seems that if gpu is not using ”shared memory” seen in windows perf tab, all is fine. After shared memory starts to get used like in heavy MP PvE missions or very heavy SP missions, the problem starts.

I rolled back to august version of nvidia drivers last week but saw no notable difference.

Yeah, i noticed great improvement already when november(?) patch came out but there's still lot to do. It won't take long to restart game after every flight so it's still playable. Hopefully it won't take long for ED to fix that because i don't want to fix that probem with 3090

My regular settings are quite a close to yours glide, but i still can replicate that fps-drop anyday with about 30% succes rate. When i put the minimum settings, minimum sampling etc, game still makes that fps drop but its more subtle. Shader cache option did no difference except longer cockpit loading times etc. It's very noticeable that when i spawn at caucasus, vram memory allocation is about 6gb. After first LShift-R (or crashing the aircraft and respawning), allocation goes to about 7gb, then 7,7-7,8 which is maximum and after that the framerate starts to drop and frametimes start to spike until the game is unplayable. After restarting the game vram allocation is back to normal.

I’m quite certain that op’s problem is not setting-dependant but caused by the vram leak which has been causing same kind of symptoms since autumn. I’ve had that since the release of syria and i’ve run all possible settings to get rid off it with no help. Even different steamvr versions and nvidia drivers etc. Nowadays i just routinely restart the game after every flight to avoid the fps drop. I’m curious to hear if op finds solution to the problem so i’ll follow this thread but i’m little skeptic before ED improves the vram handling..

Except on top on the radiomenus the mouse is not moving with head so it's not impossible..

Is it possible that after pressing F10 the GPU loads hangar textures, models etc to vram and after leaving F10 map gpu still keeps those hangar things in vram and doesn’t clear them? Switching to other program clears vram and returns regular fps? Same kind of thing possibly happens after switching aircraft or respawning. I don’t have enough knowledge about how vram works but there are now more than 10 topics in these forums and all have same kind of vram releated problems so there must be something wrong.