NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix

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

Open
#844 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug jira runtime
Dominant language
No language data
Stars
1.7k
Forks
99
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce Star Trek Bridge Commander in fullscreen, skipping or watching the intro videos, and compare VRAM usage at the intro, main menu, and mission. Start by examining bridge64.log, remix-dxvk.log, bridge32.log, and dxwrapper-stbc.log to determine which component retains the allocations. Done means identifying the responsible component and confirming that VRAM no longer remains near 3 GiB after entering a mission.

Written by the indexing model from the issue text.

Assessment

Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.