Is anyone able to create renders using Rhino Raytrace that compare to keyshot or vray?

And I made a video of the steps I took: https://peterrz.tinytake.com/tt/MzcwMzc5NV8xMTI1NzkyMw

Hi Peter, well done! You came a long way. But the raytraced and the rendered view was quite far apart appearance vice. So I made a copy of the Raytraced display mode and altered the material setting to use a custom material for all objects, and sat gradient as background for THAT mode only. It does use the lights in the scene though, so you need to do two steps to get this result:
1 - add a rectangular light the size of the objects at twice the objects height and set the light to 60% intensity.
2 - lower the default environment intensity to 0.6

And you’ll get this result in no time:


Same file just switched to normal Raytraced:

That is the easiest workflow I could manage for you. Basically just two steps though, add and alter light and environment.

You can also save an empty file as a template and then use that to import your models into.

Just open the settings page and navigate to OpenGL and display modes and import this:

Raytraced - WHITE -.ini (11.7 KB)

1 Like

Thanks, this is a nice solution. Im not crazy about having to make a light and adjusting it, but it’s just one light so not a biggie. I tried your technique and it seems to work nicely. :slight_smile: Will save it in my template file.

BTW, I find “rendering” a scene creates quite a different look from raytracing…rendering takes like 5 minutes and gives grainy results on metals, whereas raytracing takes seconds but gives a different look…also I noticed when rendering, it uses CPU, and raytrace uses GPU…I have a 2080ti so it would be nice to be able to set it to use the GPU instead (as you can with raytrace/cycles)…
Rendered… as you can see, it seems to ignore the top light in favor of the studio hdri:


Raytraced (exactly same settings as the above rendered):

Hi - the renderer in Rhino 6 uses a completely different engine than the Cycles render engine. That’s why the output is completely different.
In Rhino 7, the Raytraced display mode and the renderer use the same engine.
-wim

To get render files from the Raytraced viewport you can use _-ViewCaptureToFile. I prefer the dashed version over the dialog version, since the dialog does preview rendering, which may be slow on larger and more complex models.

Thanks Wim. Is Rhino 7 early/beta available so I can try this out for myself?

Tried it. What I dont understand is that if I change the width, it pops up a rendering box and I have to wait. Since it already rendered in the viewport, why doesnt it just save the image? Also, any way to have it “render” in the background so I can continue working, as in the case where I want to render out a 4000px wide 300dpi image that takes a while even with my machine?

Yes, Rhino 7 WIPs are available for users with a valid Rhino 6 license.
-wim

How do I get 7 in that case?

Rhino 7 for Windows: https://www.rhino3d.com/download/Rhino/7.0/wip
Rhino 7 for Mac: https://www.rhino3d.com/download/rhino-for-mac/7/wip
-wim

Thanks!

I understand that, but for a free solution it isn’t half bad :wink:
And the benefit of the light is that you can move it around, add more lights if you like, and also adjust their color like here where I use one cool and one warm light:

The links for the WIPs are on the Download page where they have been for years.

1 Like

Thanks Holo. This system seems to work for now. Played with color lighting like you show but I have to learn more about lights in rhino. Will have to master applying textures next and doing proper lighting next!

1 Like

I wanted to see the rendering differences between WIP 7 and Rhino 6, so I did a bit of a comparison specifically comparing Raytrace display and Render mode

RAYTRACE TESTS

Rhino 6:
Display mode: Raytrace White (cycles), 1000 samples, render device rtx 2080ti: 1min39sec:
https://peterrz.tinytake.com/tt/MzcwNzcyMV8xMTI3MTkwNg

WIP 7:
Display mode: Raytrace White (cycles), 1000 samples, render device rtx 2080ti: 1min34sec: https://peterrz.tinytake.com/tt/MzcwNzcxMl8xMTI3MTg5NQ

Tie

RENDER TESTS

Rhino 6:
Render, 1000 samples, render device rtx 2080ti: 5min40sec:
5min limit on video recorder reached: https://peterrz.tinytake.com/tt/MzcwNzc0NV8xMTI3MTk2MA
Resulting render: https://peterrz.tinytake.com/tt/MzcwNzc1Ml8xMTI3MTk4Mg

WIP 7:
Render, 1000 samples, render device rtx 2080ti: 3min3sec:
https://peterrz.tinytake.com/tt/MzcwNzc2NF8xMTI3MjA0MA
Resulting render: https://peterrz.tinytake.com/tt/MzcwNzc2OF8xMTI3MjA0Ng

WIP 7 wins

So between Rhino 6 and WIP 7, the raytrace (cycles) display mode is relatively unchanged between the two. The resulting images and render times were pretty much the same. I did find a very slight improvement in render time when I rendered without having the screen recorder active, but this wasnt significant.

The straight render output, however, was much faster and better in WIP 7 at almost half the time. And the resulting image looks more like cycles render. Nice work on the update. Please release to Rhino 6. :pray:

???

The “Cycles” renderer is actually available for Rhino6 if you use:
_TestPackageManager
and install the “Rhino Render Next” plugin.
after that you just choose it from the Render pull down menu at the top of the screen and set it as the current renderer.

2 Likes

Thank you. Installed but I can’t find it?

Check here you will find it.