Dear all,
I have a problem with capturing my view to file in raytraced mode and lighting. When I capture my view to file not all sources of light seem to be included in the render. Has anybody encountered the same problem. It takes a long time to render, could it be my laptop is not strong enough? I’m using rhino 7.
This is the view capture
This is a screenshot of my raytraced view
Kind regards,
Lance
If you used _ViewCaptureToClipboard or _ViewCaptureToFile in the Raytraced viewport the results should look the same regardless of strength of computer.
If you can share the file with me using Rhino - Upload to Support then please do so. I’ll be able to investigate the issue. I have pre-filled my email address so that I get automatically notified when the upload has completed.
Hi Nathan,
Ah great. I uploaded the file accidentally 2 times. I don’t know which is the first upload is, but it should be the second. Might be that I uploaded the same file twice, but one as a zip.
Thanks in advance
Ah, I see dutch in the title, leuk (:
The _ViewCaptureToFile works fine for me. Make sure that current renderer is set to Rhino Render before you do the capture if you want to capture Raytraced. Setting a different render engine may cause changes to how certain types of data are passed on - like lighting and materials may be different. (I don’t have these engines installed: V-Ray, Enscape, Twinmotion).
Hmmm, I think I’m rendering with correct engine, though I do happen to have all these three engines installed that you just named, is there any other way to turn them off? What does legacy rhino render do?
You can turn the other engines off by going to Tools > Options > Plug-ins, pick the “Plug-ins not shipping with Rhino” from the drop-down to quickly narrow down the amount of plug-ins in the list.
Then right-click on each of Enscape, V-Ray, Twinmotion and choose Enable Load Protection. Then restart Rhino and see if it works any better.
Rhino Render Legacy is the engine used in Rhino 6 and prior, it should not affect the result between Raytraced and its ViewCapture results.
Unfortunately, still doesn’t seem to do the trick. This is my system info:
Rhino 7 SR14 2022-1-10 (Rhino 7, 7.14.22010.17001, Git hash:master @ d8a2d020be8cb487bfc091316ef32170cfc7eddb)
License type: Educational Lab License, build 2022-01-10
License details: Cloud Zoo
Windows 10.0.22000 SR0.0 or greater (Physical RAM: 16Gb)
Computer platform: LAPTOP - Plugged in [79% battery remaining]
Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 9-5-2020 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA Quadro P1000 (NVidia) Memory: 4GB, Driver date: 7-1-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 462.94
> Integrated accelerated graphics device with 4 adapter port(s)
- Video pass-through to primary display device
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 7-1-2021
Driver Version: 27.21.14.6294
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
Rhino plugins that do not ship with Rhino
C:\Users\Lance\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\EleFront\4.2.2\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.14.22010.17001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.14.22010.17001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.14.22010.17001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.14.22010.17001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.14.22010.17001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\BlockEdit.rhp “BlockEdit” 7.14.22010.17001
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
I did a test on an Macbookpro M1, with no GPU at all.
Your setup looks good as far as I can tell, and your file didn’t show anything out of the ordinary. I’l check on my Windows machine still.
I’m sorry hold on a moment, it might be working… I got confused by the preview… The actual render seems to be fine in at least this instance
Btw, I never use ViewCaptureToFile or ViewCaptureToClipboard with the dialog. That is all too slow, and the preview I generally don’t need.
Since your model is rather heavy I’d use the command-line version that doesn’t try rendering previews: -ViewCaptureToFile or -ViewCaptureToClipboard. You still can make the same setting changes in the command-line, but that will be much more responsive.
Well, as for now, view capture to clipboard seems to be doing fine, however view capture to file is still incorrectly rendering…
view capture to clipboard
view capture to file
Your capture to file looks exactly like I have in the viewport, and these render correctly for both on my machine.
Looks like I have to turn on the directional light that has intensity 1.0 to get the light you’re looking for. It was turned off in my version.
Ah yes, I’m sorry I miscommunicated that… I have know realized after running some tests that the resolution seems to be the bottleneck. Viewcapturetofile and viewcapturetoclipboard, seem to neglect the lights whenever the resolution gets to high. thanks for sticking around btw
Higher than a set limit? Let me try capturing at scale 2 so the resolution doubles.
Raytraced and Rhino Render in v7 are my babies, so I want them to work correctly (:
Rendering at 2308x1236 still looks good to me. (enabled denoiser to get smoother result with just 150 samples).
Even three times the resolution works still fine
note: too bad discourse rescales all images, so no original size here, but render resolution for the 3-time scale is 3462x1854
hmmm whatever I’ve been doing it’s something wrong… now no matter which resolution I chose it is not showing the directional light… I don’t know if this is fixable… These renders look amazing by the way (:
Can you please try using the dashed version instead? -ViewCaptureToClipboard.
Easy when using a good model (:
I’ve done that already
Your last screenshot shows you using the undashed version, though, where you get the GUI dialog that renders a preview as well.
It should not matter really, but it does slow down the process of getting to rendering.
But if results are still inconsistent then I’m not sure what to suggest next. I’ll have to think it through and see if I can reproduce the reported behavior at all.
