VRAM usage in Odyssey, performances

Hi,

Playing under Linux/Proton more than under Windows (10) I always lowered my settings to get 60 fps. But ...
Going to Toci to check and buy if possible a G3 weapon, like a few times, randomly (I supposed), my frames dropped a lot, to 40, 30 and even lower when I got out of the ship. (23 under the ship).

Watching CPU usage told me ok, RAM told me ~16GB total (I have 32) so ok, GPU power was high but not so impressive (RTX 2070 super) So I went back the the ship (60fps max locked), exited to main menu, then to the game, went out of the ship and got ~40 after a few minutes (opening galaxy map, system map, watching missions , ....)

Nvidia-setting told me that ... VRAM was full. . Settings were "Average" customized with Textures, Mat. Textures and Terrain Textures set to High.
I rebooted to Windows and checked because it could have been a memory leak in proton but found same VRAM usage.

Lowering textures to average too allowed me to not overflow the video card while still going up to ~7-7.5GB in total. I don't know if it's intended and in fact it's not that important at the moment. If this can help anybody who have perf issues when on foot then this post will have been useful :)

Note : I don't use FSR

regards
 
Opening the galaxy map while on foot in a station always triggers high VRAM usage. It eventually goes back down when you leave but can lower performance until then.
 
I've seen up to ~16GiB in use.

However, the amount of VRAM allocated doesn't say much about how much is actually required. At the same settings that allocated 14GiB+ on my 6800 XT, my RTX 3080 (which only has 10GiB) was running the game just as well.
 
Considering I'm playing on a RTX 2070 with 8GB VRAM and 64GB RAM - this isn't really saying much (the overall thread)

You have other issues me thinks.

Only problem I've had with the game is weird anomalies with planetary rings vanishing around planets - and how planets are drawn - but that seems to have significantly improved after the last patch. Nothing "on-foot" as of yet.
My issues clear up with a logout/login cycle generally.
Bottom line I seriously doubt its a VRAM problem - unless you have a bad VRAM Chip - doubt it.

Course I'm playing on Win 10 Pro so yeah there's that.

Generally when you encounter these kinds of things - a good full blown restart clears up most issues linux wise.
Could also be drivers.
 
Opening the galaxy map while on foot in a station always triggers high VRAM usage. It eventually goes back down when you leave but can lower performance until then.
I also noticed that but everywhere. Textures are not discarded when we close the system map. The choice is discard memory and reload each time the user opens system map, or keep them in memory and give a fast system map opening. They chose to keep them. As I think both design choices have their pros and cons, I don't mind. But we can save some space by settings system map quality to low for example.

Note : I didn't give any of my PC specs because they don't matter. When VRAM is fully used, FPS drop. Instead of crashing games as it happened back in the old times ( a loooong time ago. :whistle: )

@Morbad used VRAM highly depends on your screen(s) size. You'll have to check on your own machine if you're interested in tuning your game. Windows, HWInfo and other tools will tell you how much VRAM is used (I use simple command line tools and Gnome System Monitor under my Debian/Linux). Just beware that you have to restart the game from the launcher to get good values when you change settings. (which annoyed me when I made the tests because I usually set /autorun /autoquit ^_^ )
 
..........

@Morbad used VRAM highly depends on your screen(s) size. You'll have to check on your own machine if you're interested in tuning your game. Windows, HWInfo and other tools will tell you how much VRAM is used (I use simple command line tools and Gnome System Monitor under my Debian/Linux). Just beware that you have to restart the game from the launcher to get good values when you change settings. (which annoyed me when I made the tests because I usually set /autorun /autoquit ^_^ )

I just had a bl00dy good laugh at someone trying to talk tech at @Morbad - gosh thanks for making my evening. LOL

O5vj6wE.gif
 
But we can save some space by settings system map quality to low for example.

Note that this also affects skybox quality. If one is actually running into performance issues due to lack of VRAM they may want to weigh that against other potential trade offs.

I didn't give any of my PC specs because they don't matter. When VRAM is fully used, FPS drop.

It matters if there is a VRAM capacity floor where performance is negatively impacted by having it all allocated. This is the first time I've heard of an 8GiB card having clear issues with Odyssey because of this.

The game can allocate all of the VRAM on my 10GiB+ parts without any apparent negative effect. So, 10GiB is evidently still enough, pretty much irrespective of settings (I was running at 4k with significantly past ultra quality with regard to things like texture resolutions on my 3080). Last time I ran the game on an 8GiB card (a 5700XT) there was also no problem (1440p ultra+). Utilization would climb to maximum, then the game would gracefully evict assets without measurable performance problems or any visual quality issues.

(I use simple command line tools and Gnome System Monitor under my Debian/Linux).

How much overhead, VRAM wise, is there when running the game on Linux via Proton/DXVK or whatever you're using?
 
Playing under Linux/Proton
I have 40% VRAM use on 4Gb 3050 on high/ultra.
That is NVIDIA's memory leak since driver 515. It is fixed in latest.
Read there below:
Also how to properly limit FPS. Limiting outside game looks much better.
 
Back
Top Bottom