Skip to content

PATH TRACING settings row + unified PT state - #12

Merged
proggeramlug merged 1 commit into
mainfrom
feat/pt-settings
Jul 14, 2026
Merged

PATH TRACING settings row + unified PT state#12
proggeramlug merged 1 commit into
mainfrom
feat/pt-settings

Conversation

@proggeramlug

Copy link
Copy Markdown
Contributor

Summary

Game-side close-out of the path-tracing roadmap (engine: Bloom-Engine/engine#93):

  • Video menu row PATH TRACING: OFF / QUALITY (STILLS) / REALTIME - new tri-state row kind, persisted as video.pathTracing, applied at boot and live on change, cycled by click/confirm, clamped by left/right. On GPUs without ray query the row reads N/A (NO RAY TRACING) and the value is inert.
  • One PT state: the menu row, the F9 debug cycle, the --pt CLI flag and the HUD all read/write the same settings value - no more parallel mode variables.
  • PERFTEST harness fix: the mode-1 scripted kill now sets the SH-031 ragdoll fields a real kill sets; it fed undefined into native f64 params and crashed on the first kill. Used for the fight-perf matrix recorded in engine docs/pt/PT-5-integration-and-restir.md (raster ~45/32-36 fps, RT 27.5/20-23, PROG rides raster in combat).
  • HUD build tag v11.

https://claude.ai/code/session_018574BdCfSjdpNK3WLgx1hP

- Video menu gains PATH TRACING: OFF / QUALITY (STILLS) / REALTIME
  (new tri-state row kind), persisted as video.pathTracing, applied at
  boot and live on change. On GPUs without ray query the row reads
  N/A (NO RAY TRACING) and the value is inert.
- PT state now lives in the settings array: the menu row, the F9 debug
  cycle, the --pt CLI flag and the HUD all read/write one value.
- PERFTEST mode-1 scripted kill now sets the SH-031 ragdoll fields a
  real kill sets - it fed undefined into native f64 params and crashed
  the harness on the first kill.

Fight-perf numbers recorded in engine docs/pt/PT-5-integration-and-restir.md.

Claude-Session: https://claude.ai/code/session_018574BdCfSjdpNK3WLgx1hP
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@proggeramlug, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 15821601-668e-44d6-bc02-d5076875844a

📥 Commits

Reviewing files that changed from the base of the PR and between d5de83d and e9abc6c.

📒 Files selected for processing (3)
  • src/main.ts
  • src/menu.ts
  • src/settings.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/pt-settings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@proggeramlug
proggeramlug merged commit a9e0c08 into main Jul 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant