OPTIX Structure Acceleration build fails #93820

Closed
opened 2021-12-07 15:27:37 +01:00 by Jonas Apessos · 7 comments

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
CPU: RYZEN 2700x 8-cores 16-threads
RAM: 32GB
Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 4GB NVIDIA Corporation 4.5.0 NVIDIA 497.09

Blender Version
Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: f1cca30557
Worked: (newest version of Blender that worked as expected)

Short description of error
Cycles will throw a exception for OPTIX_ERROR_INVALID_VALUE in opticAccelBuild() function during the building of the optix acceleration structure.

Exact steps for others to reproduce the error

  1. Set blender cycles to render using OPTIX drivers
  2. Change Device render to Graphics
  3. Add Two Subdivision modifiers
  4. Set the first one to 3 and the second to maximum (the problem might depend on the objects original geometry as well)
  5. Render Scene

More Info
In my scene i use subdivision modifier for a sea mesh with the first iteration in render mode to 3 and the second to 6.
Basically two subdivision modifiers.

Should a exception be thrown for VRAM out of memory error? thats why there was a failure to build the acceleration?

There is a high chance that this error is caused by out of memory for the vram.

i suspect that the pointer to the compacted_data.device_pointer is null and there is a synchronization issue with my graphics card, or internally the function calls for a memory size that the system does not have and it is not checked so that it does not throw or catch the exception.

I am just guessing here...

Media
2021-12-07 16-10-01.mp4

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits CPU: RYZEN 2700x 8-cores 16-threads RAM: 32GB Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 4GB NVIDIA Corporation 4.5.0 NVIDIA 497.09 **Blender Version** Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: `f1cca30557` Worked: (newest version of Blender that worked as expected) **Short description of error** Cycles will throw a exception for OPTIX_ERROR_INVALID_VALUE in opticAccelBuild() function during the building of the optix acceleration structure. **Exact steps for others to reproduce the error** 1) Set blender cycles to render using OPTIX drivers 2) Change Device render to Graphics 3) Add Two Subdivision modifiers 4) Set the first one to 3 and the second to maximum (the problem might depend on the objects original geometry as well) 5) Render Scene **More Info** In my scene i use subdivision modifier for a sea mesh with the first iteration in render mode to 3 and the second to 6. Basically two subdivision modifiers. Should a exception be thrown for VRAM out of memory error? thats why there was a failure to build the acceleration? There is a high chance that this error is caused by out of memory for the vram. i suspect that the pointer to the compacted_data.device_pointer is null and there is a synchronization issue with my graphics card, or internally the function calls for a memory size that the system does not have and it is not checked so that it does not throw or catch the exception. I am just guessing here... **Media** [2021-12-07 16-10-01.mp4](https://archive.blender.org/developer/F12704532/2021-12-07_16-10-01.mp4)
Author

Added subscriber: @JonasApessos

Added subscriber: @JonasApessos

Added subscriber: @iss

Added subscriber: @iss

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

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

Should a exception be thrown for VRAM out of memory error? thats why there was a failure to build the acceleration?

Currently out of memory situations may not be handled gracefully and program can crash or hang or throw unrelated errors. This is currently not considered to be a bug.

Please check if this happens when you reduce memory requirements like subdivision level. If you can look at used memory, check if there is enough free space. Also upload .blend file so we can reproduce the issue

> Should a exception be thrown for VRAM out of memory error? thats why there was a failure to build the acceleration? Currently out of memory situations may not be handled gracefully and program can crash or hang or throw unrelated errors. This is currently not considered to be a bug. Please check if this happens when you reduce memory requirements like subdivision level. If you can look at used memory, check if there is enough free space. Also upload .blend file so we can reproduce the issue
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

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

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

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Sign in to join this conversation.
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
3 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#93820
No description provided.