AM55
(9.0.25329.12305, 2025-11-25) Windows, OpenGL
Can you give a bit more information? In that short clip I see you change a slider and see the raytraced result changing.
Hello @Gijs,
I’m currently unable to submit proper bug reports through the usual PRO channels. Would you like me to report the issue here instead?
Also, the video upload size limit on this platform is quite small, which is why my video submission is very short. I would really prefer a more professional and dedicated platform for submitting bug reports.
As for the issue:
It seems that the Ambient Occlusion (AO) slider is not working as expected in Rhino (version 9.0.25329.12305, 2025-11-25), on Windows using OpenGL in the Raytraced display mode.
Actual behavior: Makes the material black
At 20%, the AO effect appears almost completely black and looks significantly different from the Rendered display mode.
Expected behavior:
At 20%, the AO texture should be nearly transparent and visually similar to what is shown in the Rendered view.
The reason you were kicked out of YT is not personal,
the fact that you could report directly on YT was a rare exception. As mentioned before, I much prefer to repeat the bug first and add it to the tracker, so that, when the moment comes this bug gets fixed, I have the original file that I created to test the bug, that the test file is as simple as possible, and that the bug is added to the correct system, affected versions are reported correctly and a few more things.
This bug is easy to reproduce and a simple ball with a checker texture is sufficient to illustrate this.
RH-91022 AO texture doesn’t render correctly
1 Like
It would be great to see even stronger automated quality assurance (AQA) and a test-driven development (TDD) approach—those help prevent regressions like this in the first place.
It doesn’t seem to be a regression. I see the same bug in 7 8 and 9
1 Like