NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix

[Runtime Bug]: Portal with RTX – Present semaphore bug

Open
#854 2 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

This is actually the second runtime bug within two or so days that I have encountered, but RTX Remix insists that I report it, so here I am.

Anyway, this bug seems to relate to something called a Present semaphore not being released as expected, according to bridge32.log. It would not surprise me if the first bug turned out to be related to this problem.

How do you reproduce the bug?

I began replaying Portal with the intent to complete the bonus set of maps, particularly the challenges. This session spanned about 1 hour, 20 minutes, and 54 seconds before the crash. In the last minutes leading up to the crash, I was attempting to beat the clock for gold in Test Chamber 15. In one part of the chamber, I simply skip the second "ball and catcher" puzzle and tightrope my way across the pool of sludge in the following manner: I create the portals on the walls, as this puzzle would expect, before standing inside them. Then, I fire my gun and immediately jump just outside the portals as I briefly wait for another portal to be created before landing back inside. I repeat the process one more time before I reach the destination, all while the lift has not been activated by solving the second ball and catcher puzzle at this point. If this description is too confusing for you to understand, just know that it is a very difficult maneuver that has led me to reload more times than any other part of the chamber in this challenge, and that is exactly what happened.

What is the expected behavior?

The runtime should release the Present semaphore. As an aside, I see a warning in bridge32.log about two DirectInput8Create and DirectInputCreate procs being injected. It could be unrelated to this bug, but it is worth investigating. I am glad the log file reminded me as I was concluding this report.

Version

remix-main+909ce539

Logs

bridge32.log
bridge64.log
remix-dxvk.log

Crash dumps

This crash dump appears to be for the first bug: NvRemixBridge.exe_20250526_002311.dmp
If rerunning Portal with RTX causes RTX Remix to create the second dump, I will upload it.

Media

If a picture is worth a thousand words, then this screenshot should help illustrate the puzzle I reloaded the test chamber on the most. As a reminder, this is part of a time challenge in which I skipped one puzzle and attempted to zip right through the puzzle here.

Image

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

Start by reviewing the attached bridge32.log, bridge64.log, remix-dxvk.log, and the available NvRemixBridge crash dump, then attempt to reproduce the crash in Portal with RTX during the described Test Chamber 15 sequence. Done means identifying why the Present semaphore is not released and confirming that the runtime no longer crashes; investigate the DirectInput injection warning separately if relevant.

Written by the indexing model from the issue text.

Assessment

Domain
computer-graphics
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.