Optix not working in SR22

Hi @nathanletwory
I’m having problems with SR22 - the optix “core” doesn’t seem to want to compile; no problem with the ordinary Cycles core. I’ve left it sitting for some 20 minutes now, and show “Rendering” in the status bar, but only the GL preview is shown. Sysinfo below.

SysInfo

Rhino 7 SR22 2022-8-9 (Rhino 7, 7.22.22221.05001, Git hash:master @ 05abcc088fb84e0c3c2a5b9b063bd4a14a3fb17f)
License type: Commercial, build 2022-08-09
License details: Cloud Zoo

Windows 10 (10.0.19044 SR0.0) or greater (Physical RAM: 95Gb)

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro RTX 4000 (NVidia) Memory: 8GB, Driver date: 7-21-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 516.94
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1

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-21-2022
Driver Version: 31.0.15.1694
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB

Rhino plugins that do not ship with Rhino
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Twinmotion Direct Link 2020.2 (e24ee14a-9514-47da-8fe6-f6e61b20160e)\Twinmotion Direct Link 2020.rhp “Twinmotion Direct Link 2020” 1.0.6.0
C:\Program Files\Rhino 7\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
D:\Dropbox\2D & 3D\Rhino plugins\ScaleOverlay.rhp “ScaleOverlay” 1.0.0.0
C:\Program Files\SimLab\Plugins\SimLab VR from Rhino\SimLabVRPlugin.rhp “SimLab VR for Rhino”
D:\Dropbox\2D & 3D\GH\elefront421\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0
C:\Program Files\Rhino 7\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
D:\Dropbox\2D & 3D\Rhino plugins\StereoView.rhp “StereoView”
C:\Users\jn\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\RPC\0.0.13\RPC.rhp “RPC”
C:\Users\jn\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\IntelDenoiser\0.6.4\IntelDenoiser.Windows.rhp “IntelDenoiser.Windows” 0.6.4.0
C:\Users\jn\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0
C:\Users\jn\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\SubstanceImporter\2.0.2\Substance.Win.rhp “SubstanceImporter” 2.0.2.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.22.22221.5001
C:\Program Files\Rhino 7\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 7\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 7\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.22.22221.5001
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.22.22221.5001
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\Alerter.rhp “Alerter”
C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.22.22221.5001
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.22.22221.5001
C:\Program Files\Rhino 7\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 7.22.22221.5001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.22.22221.5001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
C:\Users\jn\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\PanelingTools\2021.3.2.446\PanelingTools.rhp “PanelingTools”

Checking here. That is peculiar indeed. While I investigate luckily CUDA rendering still works.

I’m a bit confused as to how this is possible. I did recompile the OptiX kernel, but I did not change anything to the Cycles kernel code. The only bigger change is that the CUDA kernels are now delivered as .ptx files, just like the OptiX kernel, which was already delivered as .ptx since the very beginning.

@Normand did OptiX work for you before you updated to SR22? What SR were you prior to SR22?

1 Like

So to see what is going on I built local debug version with the PTX OptiX kernel as provided in the installer. This works just fine here. Then I built a Release version of Rhino 7, still with the same PTX OptiX kernel - that also works.

What doesn’t work for me either is the Rhino 7.22 installation. I continue to investigate, but this is proving to be a tough one to dive into, since the build in my dev environment works just fine :confused:

1 Like

Hi @nathanletwory
Yes, I’ve had Optix as my default for some time - I use Cycles mainly for pre-viz in Rhino, and we do a lot of interiors, where Optix most of the time had a (albeit tiny) advantage. Before SR22 I guess I was at SR21, although I have just been away on summer holiday, so I might have missed a service release (but I don’t think so!). Let me know if it would help for me to revert to SR21 to see if that works :slight_smile:
-Jakob

I’ll have to do some testing myself first. I’ll test with SR20 and SR21 as well. Currently unknown is why the OptiX kernel works in my own build, but not the official installer build.

1 Like

@Normand I found the cause and a fix for the problem. Tracking here RH-69807 OptiX device fails to render .

I’ll link you a new build once one is available.

1 Like

RH-69807 is fixed in Rhino 7 Service Release 22

having the same issue, stuck in “Rendering…”

using rhino Version 7 SR24 (7.24.22308.15001, 2022-11-04)

have Nvidia Quadro RTX 4000 with compute capability of 7.5

*apologies, seems to work after I restarted rhino.

If you had a driver update before that then the optix kernel was being compiled at that time, this always takes a moment.