NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix

[Runtime Bug]: Duke Nukem Forever gives a black screen no matter what.

Open
#963 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug

Attempting to launch Duke Nukem Forever with rtx-remix 1.2.4 results in the game giving a black screen with no video output at all, the audio is still present however and the game itself can still be interacted with like normal except that you're completely blind.

How do you reproduce the bug?

Add rtx-remix's files to the Duke Nukem Forever/system folder.

Launch the game and observe a black screen that stays, the only thing visible is the rtx remix overlay that shows up initially.

What is the expected behavior?

The game should not have a black screen and instead show the video output as expected.

Version

1.2.4

Logs

bridge32.log
bridge64.log
remix-dxvk.log

Crash dumps

No response

Media

No response

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 reproducing the black screen with rtx-remix 1.2.4 in Duke Nukem Forever after placing the RTX Remix files in the game's system folder. Review bridge32.log, bridge64.log, and remix-dxvk.log for the rendering failure; done means video output appears while audio and interaction remain functional.

Written by the indexing model from the issue text.

Assessment

Domain
computer-graphics, game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.