PATH TRACING settings row + unified PT state - #12
Conversation
- 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
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
Game-side close-out of the path-tracing roadmap (engine: Bloom-Engine/engine#93):
video.pathTracing, applied at boot and live on change, cycled by click/confirm, clamped by left/right. On GPUs without ray query the row readsN/A (NO RAY TRACING)and the value is inert.--ptCLI flag and the HUD all read/write the same settings value - no more parallel mode variables.undefinedinto native f64 params and crashed on the first kill. Used for the fight-perf matrix recorded in enginedocs/pt/PT-5-integration-and-restir.md(raster ~45/32-36 fps, RT 27.5/20-23, PROG rides raster in combat).https://claude.ai/code/session_018574BdCfSjdpNK3WLgx1hP