NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix

[Runtime Feature]: Further Anti-Culling Improvement

Open
#571 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What is the context of the feature/improvement?

To further enhance the anti-culling in the RTX-Remix runtime, particularly to assist with older games where the rendering area is very limited. This improvement aims to maintain a seamless visual experience by ensuring that areas previously seen by the player continue to be rendered, even when the game itself might stop rendering them.

Please describe the feature/improvement?

Enchanced anti-culling would help remember to render the world around the player/area. Helping prevent light from leaking onto scenes and to better implement path tracing into older games without the need for more trivial coding or getting into older games codes.

What would be your solution? (optional)

One potential solution is for the runtime to map out the surroundings as the player moves through the game. This mapping would allow the runtime to remember and continue rendering objects and environments that were previously in the player's view. Additionally, a concept of a "backdrop blanket" could be implemented, where a static rendering layer persists in the background, maintaining the integrity of the scene even if the game stops rendering certain parts. This approach would help mitigate the culling issues commonly seen in older games. Maybe the mapping could be done through captures? Like the runtime would remember the order things have been rendered in from the mod.usda - and through that mod it would know what's rendered and where walls/roofs should be. Just brain-storming, no developer here, just imagining :)

Version

2024.3.1

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

No source file, test, or entry point is named; begin by locating the runtime's anti-culling and path-tracing implementation. The proposal is exploratory, so confirm its scope and acceptance criteria with maintainers first; done would require previously seen areas to remain rendered without the reported light leaks.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.