Cycles Optix internal compiler error #73533
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#73533
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10
Graphics card: RTX 2070
Blender version: v2.81a (steam latest)
Everything was fine, but one day I start getting this exception each time I render(I'm always using optiX):
only optix+Cycle render not work
this happens with any scenes
Added subscriber: @aisatan.ne
OPTIX INTERNAL COMPILER ERRORto Cycles Optix internal compiler errorAdded subscriber: @pmoursnv
Added subscriber: @brecht
Changed status from 'Needs Triage' to: 'Needs User Info'
This issue may be similar to #73076 (Optix render kernels constantly reloading on Linux).
Deleting the cache file from the
%LOCALAPPDATA%\NVIDIA\OptixCache
folder might help, in case it got corrupted.Thanks, but it didn't help, the exception left the same and some of the cache files re-created
Changed status from 'Needs User Info' to: 'Needs Triage'
Changed status from 'Needs Triage' to: 'Needs User Info'
Can you try the latest daily build then, in case it's already solved? https://builder.blender.org/download/
Or try upgrading the NVIDIA drivers to the latest version?
And if that does not help, please run Blender with
--debug-cycles
command-line argument and report back the console output after reproducing the problem (which contains more detailed information about the OptiX error).This can be done by running
blender_debug_log.cmd
that is included with the Blender installation. After Blender exits it will show you log files, which can be attached to this report.I have the latest (game ready version) for today, 450.12
Yes, alpha v2.83.2 works fine for me, but not the beta.
I guess I will wait?
files from blender_debug_log.cmd:
debug_logs.zip
and console output with --debug-cycles:
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
The latest official (and supported) driver on Windows is 442.19. May I ask where you got a 450.12 one?
Good point, I get updates from GeForce Experience (Game Ready version), but I'm also Windows Insider, I guess they gave me a test build of drivers too (maybe through windows update)
I will try to reinstall the official one from nvidia page.
Hi, I installed 442.19 and it did help, so we can close this I guess, thank you Patrick Mours
Changed status from 'Needs Developer To Reproduce' to: 'Archived'
Added subscriber: @ceecko
Changed status from 'Archived' to: 'Resolved'
I still experience the same issue.
Running with 2x NVIDIA
#4
on Debian 9 with NVIDIA drivers440.64.00
and Blender2.83-9607e5498583-linux64
Blender is stuck on this line for about 60 seconds
During this time 1 cpu thread is 100% utilized.
After 60 seconds the rendering continues as usual.
Running rendering again after it is finished does not make Blender stuck on
Cache miss
and rather starts rendering straightaway without any delay.I can easily replicate this if you need more debugging information.
Changed status from 'Resolved' to: 'Archived'
Sorry, the status changed on its own...
@ceecko, that sounds like it's compiling the PTX for the first time, and then reusing the cached item the next time. That's what I would expect to happen.
Sounds reasonable. I don't have experience with the compiling of cache. Maybe a stupid question:
Do you feel it's reasonable to expect compiling times of
~40sec
for117MiB
cache as in the logs AiSatan provided?Could it be maybe an issue of throughput?
We'd like it to be faster, but that's the expected time now.
Added subscriber: @CosmoMidias
Thanks brecht! That worked for me!
{meme, src=itsawesome}
(running POP OS, Linux. RTX 2070 with the 440.44 nvidia driver)
The location in Linux is /var/tmp/OpitxCache
I spent all day trying to fix it and I was about to fresh install the OS... you saved my day! Or at leat the rest of it...