Warning Num Samples Per Thread Reduced To 32768 Rendering Might Be Slower ~repack~ May 2026
Feature Specification: Adaptive Sample Throttling & User Notification
1. Overview
Feature Name: Sample Throttling Notification System Goal: To ensure system stability by preventing buffer overflows or GPU timeouts (TDR) when the user requests a sample count per thread that exceeds hardware limits, while providing transparent feedback that rendering performance may be impacted.
. When the engine is forced to truncate its sampling routine mid-way to stay under the cap, it often has to perform extra passes or management tasks to reconcile that data. Furthermore, if you actually Lower render sample count (if you’re using path
: If the scene is too large for the available VRAM, the engine automatically lowers the "samples per thread" to fit the remaining data. The Performance Hit reduce samples from e.g.
Increase Virtual Memory: In some cases, increasing your Windows pagefile size can act as a "safety net," though this will still be slower than dedicated VRAM. each doing 32k samples
He pressed Y.
How to fix / reduce impact
- Lower render sample count (if you’re using path tracing, reduce samples from e.g., 1024 to 512)
- Increase thread count (more threads, each doing 32k samples, may balance out)
- Update GPU drivers and rendering API runtime
- Check for software updates (renderer may have a hardcoded limit removed in newer versions)
- Reduce scene complexity (fewer objects/textures, lower resolution)
- Switch to a different render device (e.g., CPU instead of GPU, or vice versa)
- Ignore it if rendering is still fast enough — 32768 is often plenty for most frames