When a scene is extremely "heavy," the GPU takes longer to calculate each sample. The engine sees this delay and preemptively reduces the sample-per-thread count to avoid a system hang.
While it isn't a "crash" error, it is a significant hint that your hardware is hitting a driver-level or architecture-level limit. Here is a deep dive into why this happens, what it means for your render times, and how to fix it. What Does This Warning Actually Mean? At its core, this is a . When a scene is extremely "heavy," the GPU
Often, users set their Max Samples to 0 (infinity) or a placeholder like 100,000, relying on a "Noise Threshold" to stop the render. If the Noise Threshold is set too low, the engine will try to reach that 100k sample count, triggering the 32k thread cap. Try setting a more realistic Max Sample limit (between 4,096 and 16,384 is usually plenty for modern denoising). Here is a deep dive into why this