Cycles: GPU Optix kernel loading with Bevel/Ambient Node. #102162

Open
opened 2022-10-30 13:13:34 +01:00 by Robert Lechl · 34 comments

XMGNEO17 Laptop AMD Ryzen9 5900HK Radion.
Operating system: Windows 11 Home. 21H2
Graphics card: Nvidia Geforce RTX 3080 Laptop GPU. 16 GB VRAM.

Blender Version
Blender 3.2-3.4 show the error. Blender 3.1 and before not.

Short description of error
The error happens when ever an Ambient Occlusion or Bevel Node is used and connected in a shader and GPU option OPTIX is enabled for rendering in Cycles. It does not happen with CUDA or CPU.
Blender will start render process and stops with the line: Preparing for rendering, this can take time.. etc. At that point the UI is still working, but will freeze after trying to cancel rendering. Blender can only be forced to shut down. Scene changes are lost.

Exact steps for others to reproduce the error
The but is very simple to reproduce:

  1. Open Blender and apply a shader to the cube.
  2. Add a bevel/Ambient node to the shader and connect it to any input. Doesn't really matter which.
  3. Enable Optix in the preferences and set cycles as render. Make sure its set to use GPU.
  4. Switch viewport to preview render.
  5. Blende will stop preparing the scene and won't move further. Its UI is still reacting until trying to stop the process.
XMGNEO17 Laptop AMD Ryzen9 5900HK Radion. Operating system: Windows 11 Home. 21H2 Graphics card: Nvidia Geforce RTX 3080 Laptop GPU. 16 GB VRAM. **Blender Version** Blender 3.2-3.4 show the error. Blender 3.1 and before not. **Short description of error** The error happens when ever an Ambient Occlusion or Bevel Node is used and connected in a shader and GPU option OPTIX is enabled for rendering in Cycles. It does not happen with CUDA or CPU. Blender will start render process and stops with the line: Preparing for rendering, this can take time.. etc. At that point the UI is still working, but will freeze after trying to cancel rendering. Blender can only be forced to shut down. Scene changes are lost. **Exact steps for others to reproduce the error** The but is very simple to reproduce: 1. Open Blender and apply a shader to the cube. 2. Add a bevel/Ambient node to the shader and connect it to any input. Doesn't really matter which. 3. Enable Optix in the preferences and set cycles as render. Make sure its set to use GPU. 4. Switch viewport to preview render. 5. Blende will stop preparing the scene and won't move further. Its UI is still reacting until trying to stop the process.
Author

Added subscriber: @RobertLe

Added subscriber: @RobertLe

#104342 was marked as duplicate of this issue

#104342 was marked as duplicate of this issue

#104231 was marked as duplicate of this issue

#104231 was marked as duplicate of this issue

#100395 was marked as duplicate of this issue

#100395 was marked as duplicate of this issue
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Thanks for the report. Not a bug I would say.
I'm able to confirm the long waiting time but it compiled after some time.
Wait for render kernels to load. Because interrupting the process does result into the freeze.

Thanks for the report. Not a bug I would say. I'm able to confirm the long waiting time but it compiled after some time. Wait for render kernels to load. Because interrupting the process does result into the freeze.
Author

Interesting case.
I tested my work scene and got no response even after 15 min wait time.
I tested an empty scene with a cube and did through a preset material on it.. no response in 5 min (So I shut it down)
Then I did just add a bevel node to a cube.. simple scene. 3 min later the rendering started.
So once compiled it worked on the other scenes too.
I then switched to Blender 3.3.1 and again the same process. However it took this time 4 min to start render the cube.

I would say, this is clearly a problem.

  1. Because its not clear why I take different time depending to scene.
  2. It didn't happen in 3.1, or with Cuda, M1 or other hardware.
  3. It need to be repeated for each version of Blender.

A solution would be waring the user as soon as he switch to Optix for the first time, that he need to do a test run to enable Bevel and Ambient Occ. node. Maybe that could be done right when Optix is enabled first time. Somehow this information must exist somewhere in the system.

Interesting case. I tested my work scene and got no response even after 15 min wait time. I tested an empty scene with a cube and did through a preset material on it.. no response in 5 min (So I shut it down) Then I did just add a bevel node to a cube.. simple scene. 3 min later the rendering started. So once compiled it worked on the other scenes too. I then switched to Blender 3.3.1 and again the same process. However it took this time 4 min to start render the cube. I would say, this is clearly a problem. 1. Because its not clear why I take different time depending to scene. 2. It didn't happen in 3.1, or with Cuda, M1 or other hardware. 3. It need to be repeated for each version of Blender. A solution would be waring the user as soon as he switch to Optix for the first time, that he need to do a test run to enable Bevel and Ambient Occ. node. Maybe that could be done right when Optix is enabled first time. Somehow this information must exist somewhere in the system.
Member

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Member

Hi, thanks for the update. Checked in 3.2 and prior versions, kernel compiling doesn't happen there.
Some commit between 3.2-3.3 has introduced this. This is one time process so I'm not sure how to bisect.
#100395 and #100246 are probably related.
I'll forward this report to devs for now.

Hi, thanks for the update. Checked in 3.2 and prior versions, kernel compiling doesn't happen there. Some commit between 3.2-3.3 has introduced this. This is one time process so I'm not sure how to bisect. #100395 and #100246 are probably related. I'll forward this report to devs for now.

Added subscriber: @FLEB

Added subscriber: @FLEB
Member

Added subscribers: @dodo-2, @badjano, @MaxArch, @giorgifolio, @lbarros, @Tyler-Spicher, @Torch-1, @rjg

Added subscribers: @dodo-2, @badjano, @MaxArch, @giorgifolio, @lbarros, @Tyler-Spicher, @Torch-1, @rjg

Added subscriber: @Frederik-Ostergaard

Added subscriber: @Frederik-Ostergaard
Member

Added subscriber: @imdjs

Added subscriber: @imdjs
Member

Added subscriber: @KloWorks

Added subscriber: @KloWorks
Philipp Oeser removed the
Interest
Render & Cycles
label 2023-02-09 14:04:04 +01:00
Member

@brecht hi, can you check this?

@brecht hi, can you check this?

Anyone know if this will be looked at?

Anyone know if this will be looked at?

Blender 3.5 and still not been fix.
is there plan to fix this issue ?

Blender 3.5 and still not been fix. is there plan to fix this issue ?

Thanks for the report. Not a bug I would say.
I'm able to confirm the long waiting time but it compiled after some time.
Wait for render kernels to load. Because interrupting the process does result into the freeze.

even with 3.5 still crash, even I left it for more than 8 minute it will not working and crash.
Please confirm it as high Priority.
I can't render with AO anymore.
Thanks

> Thanks for the report. Not a bug I would say. > I'm able to confirm the long waiting time but it compiled after some time. > Wait for render kernels to load. Because interrupting the process does result into the freeze. > even with 3.5 still crash, even I left it for more than 8 minute it will not working and crash. Please confirm it as high Priority. I can't render with AO anymore. Thanks
Pratik Borhade changed title from Cycles GPU with Optix crash which Bevel/Ambient Node. to Cycles: GPU Optix kernel loading with Bevel/Ambient Node. 2023-04-25 05:33:58 +02:00

Same problem here on Linux, RTX 3070 - first one here using Linux to report this so it is not OS specific.

Same problem here on Linux, RTX 3070 - first one here using Linux to report this so it is not OS specific.

Blender 3.6.4
RTX 4070
Windows 11
Cycles with Optix
Basically the same symptoms when adding AO node to the color input. Cycle stops rendering, the image can be frozen on the last rendered image if I make the object appear by pasting it from another scene. For a few seconds I can still move in space even if the rendered image is frozen, then the software crashes.
I'm reporting this because I haven't seen anyone report this bug with a 4000 series graphics card (I don't know if it matters).

Blender 3.6.4 RTX 4070 Windows 11 Cycles with Optix Basically the same symptoms when adding AO node to the color input. Cycle stops rendering, the image can be frozen on the last rendered image if I make the object appear by pasting it from another scene. For a few seconds I can still move in space even if the rendered image is frozen, then the software crashes. I'm reporting this because I haven't seen anyone report this bug with a 4000 series graphics card (I don't know if it matters).

I have the exact same symptoms, and I'm quite sure it just takes a long time to load the kernels. This process happens when using some rendering features for the first time with a new Blender version, like AO, bevel, or OSL.

In my machine it can take more than 15 minutes, during which Blender does not respond, consumes a lot of resources, and any attempt at using the program (or too much resources elsewhere) just slows it down more and usually leads to a crash. My advice is to just let it load for as long as it needs and don't try to use Blender while it's loading.

I have the exact same symptoms, and I'm quite sure it just takes a long time to load the kernels. This process happens when using some rendering features for the first time with a new Blender version, like AO, bevel, or OSL. In my machine it can take more than 15 minutes, during which Blender does not respond, consumes a lot of resources, and any attempt at using the program (or too much resources elsewhere) just slows it down more and usually leads to a crash. My advice is to just let it load for as long as it needs and don't try to use Blender while it's loading.

maybe i got the same, but different!?
#115149

maybe i got the same, but different!? https://projects.blender.org/blender/blender/issues/115149

Me too,, when use Bevel shader, Optix crashs, switch CUDA will works.
Blender 3.6.5lts
i7+8700, rtx4060, windows 11

Me too,, when use Bevel shader, Optix crashs, switch CUDA will works. Blender 3.6.5lts i7+8700, rtx4060, windows 11

Happening in Blender 4.0.2 stable

Happening in Blender 4.0.2 stable

Still happens in 4.2 alpha.
Windows 11, RTX 3070

Still happens in 4.2 alpha. Windows 11, RTX 3070

Can confirm with rtx 4070 4.2 Alpha

Can confirm with rtx 4070 4.2 Alpha
Brecht Van Lommel added
Type
Bug
and removed
Type
Report
labels 2024-06-14 16:02:13 +02:00

can Confirm this too!
Broken:
Blender 4.1.1
Blender 4.1
Blender 4.0
Blender 3.9

RTX 4080 Super
ryzen 9 7950X3D

Nvidia Driver Versions:
Studio Driver 555.99
Game Ready Driver 555.99

only with OptiX and Gpu selected in Cylcles. When using CUDA or with CPU Rendering it works fine

16.June.2024

can Confirm this too! Broken: Blender 4.1.1 Blender 4.1 Blender 4.0 Blender 3.9 RTX 4080 Super ryzen 9 7950X3D Nvidia Driver Versions: Studio Driver 555.99 Game Ready Driver 555.99 only with OptiX and Gpu selected in Cylcles. When using CUDA or with CPU Rendering it works fine 16.June.2024

It's happening to me on 4.2.0 LTS but I never had this issue on previous versions

GTX 1660Ti Mobile
i7 10870H

NVIDIA Driver version: Game Ready Driver 555.99

On CUDA or CPU works fine but when the problem appears when using Optix

It's happening to me on 4.2.0 LTS but I never had this issue on previous versions GTX 1660Ti Mobile i7 10870H NVIDIA Driver version: Game Ready Driver 555.99 On CUDA or CPU works fine but when the problem appears when using Optix

Same problem here:

Blender 4.2.0
RTX 3070
i5 10400

Nvidia Game Ready Driver 560.81

With Cuda works fine.

Same problem here: Blender 4.2.0 RTX 3070 i5 10400 Nvidia Game Ready Driver 560.81 With Cuda works fine.

Same problem in the 4.2.3LTS.
But after a waiting for more than 20 minutes, i did succeed in loading and then rendering.
However, the loading time is too long.

Same problem in the 4.2.3LTS. But after a waiting for more than 20 minutes, i did succeed in loading and then rendering. However, the loading time is too long.
Author

Just as a follow up, I have about 1-2 minutes now testing on MacOS 15 with M3 and Win11 with RTX 4090.
I guess it's depending to the performance of the graphic card. However the precompile should be part of the installation process, or have a better user information.

Just as a follow up, I have about 1-2 minutes now testing on MacOS 15 with M3 and Win11 with RTX 4090. I guess it's depending to the performance of the graphic card. However the precompile should be part of the installation process, or have a better user information.

2 years.... Nobody want work on it 😂😂😂

2 years.... Nobody want work on it 😂😂😂

yes, it would be great if this can be fixed soon. bevel and ao node are essential in our pipeline.

yes, it would be great if this can be fixed soon. bevel and ao node are essential in our pipeline.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
20 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#102162
No description provided.