rtx-remix icon indicating copy to clipboard operation
rtx-remix copied to clipboard

[Runtime Bug]: High Vram usage after reacing the main menu

Open Trekkie-ship-it opened this issue 7 months ago • 3 comments

Describe the bug

Not sure if its a dxwrapper, bridge, or a dvxk issue.

Star Trek Bridge Commander using dxwrapper 7to9 latest release and remix 1.0.0.

Reaching around ~3GiB of vram usage according to rtx gui after reaching the main menu of Star Trek Bridge Commander, During the intro videos it hits ~1.8GiB, main menu around 3GiB, and launching a battle or a mission it never goes down.

How do you reproduce the bug?

Launch the game in fullscreen and hit the space bar to skip playing the intro videos or let them play. Tried deleting the videos but it doesn't help. Remix gui shows vram starting at 1.8GiB and jumping to ~3GiB at main menu.

What is the expected behavior?

No response

Version

1.0.0

Logs

bridge64.log remix-dxvk.log bridge32.log dxwrapper-stbc.log

Crash dumps

No response

Media

https://github.com/user-attachments/assets/1d90cdb2-b97b-4c7e-8b48-31485bd66dc8 Test run of the game at 480p stretched to 1080p

Trekkie-ship-it avatar May 12 '25 11:05 Trekkie-ship-it

This sounds like just typical Remix memory usage unless you have a reason to think otherwise.

Remix usually takes a fair bit of memory as it has many buffers needed for ray tracing and other operations done by external libraries (e.g. NRC, DLSS), hard to say exactly how much is needed as it depends on resolution and the configuration, but 3 GB is within the range I'd expect. Maybe a bit high for running only at 480p though, but it really depends on the specifics.

As for why it jumps up only when reaching the menu, some of these resources are lazily allocated, so having the memory increase after intro video like this is typical as the menu is where ray tracing actually starts and thus triggers allocations for those resources. Additionally geometry will only start filling up BVHs after it's available, and any textures will be lazily allocated by the texture streaming system once they are determined to be in use, so those sorts of memory increases also will happen after ray tracing begins as well.

anon-apple avatar May 12 '25 19:05 anon-apple

Maybe it is a resolution thing. Attempting 1920x1080 with rtx causes the game to crash.

For comparison running in 1280x1024 window mode via dxwrapper I reach the main screen @ 2.2GiB. Image Image

Full screen window mode via dxwrapper 1280x1024 in game is still under 3GiB but I lose mouse control over the rtx gui. Edit: Hitting the Windows key brings it back . Image

Fullscreen non-window mode 1280x1024 in game. Image

bridge64.log remix-dxvk.log bridge32.log dxwrapper.in.log dxwrapper-stbc.log

Trekkie-ship-it avatar May 13 '25 04:05 Trekkie-ship-it

Thanks for the update! We've filed REMIX-4400 for internal tracking.

NV-LL avatar Jul 07 '25 20:07 NV-LL