OSPRay always create float framebuffer
When OIDN compatibility was disabled, VTK was creating a uchar framebuffer.
Having a floating point framebuffer can be useful even without denoising if OSPRay is a delegate pass of other OpenGL render passes that need floating point precision (e.g. tone mapping).
The drawback is that the framebuffer comsumes more memory but this should not be an issue.
Edited by Michael Migliore