Warning Num Samples Per Thread Reduced To 32768 Rendering Might Be Slower ((exclusive))

class RenderEngine private: int samplesPerThread;

No, unless you need every ounce of render speed.

Silence.

Why 32768? That number (2^15) is often a hardcoded safety limit imposed by the render engine or the underlying hardware/API (e.g., CUDA, OptiX, OpenCL). The warning appears when the renderer tries to allocate more than 32768 samples per thread, but something—memory constraints, driver limits, or device capabilities—forces it to that number to 32768.

It is noteworthy that this warning on the same machine. Modern CPU renderers can utilize system RAM (e.g., 32 GB, 64 GB, or more) and often have more robust memory management. When you see the warning with the GPU, it is almost always because VRAM is the bottleneck. That number (2^15) is often a hardcoded safety

: In rendering, "samples" often refer to the number of times the rendering algorithm checks for color information (or other attributes) per pixel. This is particularly relevant in rendering techniques that rely on sampling, such as ray tracing or path tracing. Increasing the number of samples can lead to more accurate and smoother images but at the cost of increased computation time.

This is for production; it’s a debugging tool. Modern CPU renderers can utilize system RAM (e

If you encounter this message frequently, you can optimize your scene using these methods recommended by Chaos Support Switch to Progressive Sampler Progressive Image Sampler