Thank you for providing the AMD ProRender plug-in for Mac! At present, it provides sufficiently viable speed for visualization inside Rhino on Mac OS. Appreciated!
Not sure if the following is coming from AMD (the plugin code you implement) or something Rhino is doing? Only tested on Mac OS and one workstation, though I see the issue across multiple different .3dm files/models I’ve tried.
When rendering with a ‘white studio’ and a ground plane for shadows, a gray line runs across the render, which appears to be the edge of the Rendering Pnl produced ground plane. (If I rotate the model, the line moves its location up or down.)
@nathanletwory is correct. This is the ground plane causing the issue. The reason is ProRender and Rhino don’t understand the ground plane the same way. I suggest you disable the Rhino ground plane and add a surface object below your chair large enough for the shadow. Then assign the surface the ProRender Shadow Catcher material.
Any chance the Rhino/ProRender ground plane issue is able to be fixed, some way, in future, on the Rhino side?
While not a deal breaker, it is a buzzkill to have to turn that layer on/off repeatedly when using ProRender for repeated real-time photorealistic visualization (as opposed to Render), especially considering that ProRender is the only viable (speed) alternative inside Rhino on Mac OS at present.
You still get a Solution , but in terms of completeness, it’s a Solution …
To be honest managing the ground plane manually like this is much better from rendering technicality perspective anyway. An automatic ground plane is a rather huge and messing with accelleration structures. Doing it manually allows you to improve performance - perhaps I should add a Raytraced shadowcatcher material as well.
Interesting! I don’t doubt the technical specifics, especially with complex scenes, nor your expertise. My scenes, however, are almost exclusively product oriented - a single object in a white room. Out of curiosity, I ran a ProRender test with this simple Eames chair reference model. Good quality - 500 samples - 1920 x 1080. It confirmed your performance thesis:
1:17 - Ground Plane
1:05 - Plane/Shadow Catcher
Faster is better! No doubt!
Then I interacted with the real-time viewport set to ProRender, first with the ground plane enabled, and second using the manual method - Plane/Shadow Catcher. I could not perceive a difference. (though I’m sure there was a marginal measurable difference based on the 500 sample render test.)
So in this use case, I’d still appreciate the convenience of a ground plane. I supposed my opinion is influenced from years using Keyshot.
As for a Raytraced shadowcatcher material - heck yeah too! That has got to help someone, and I look forward to the day (if I live that long… ) when Cycles Raytraced is viable (speed) on Macs.
ProRender for Rhino currently doesn’t support the material library. I’ve looked into supporting it before and it could be a possibility. I’ve logged a request so I don’t lose track of it and I’ll keep you updated.