Error at "Building OptiX acceleration structure" #72058

Closed
opened 2019-11-30 01:31:39 +01:00 by Anže · 9 comments

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28
CPU: i9-9900k
RAM: 32 GB

Blender Version
Broken: version: 2.82 (sub 2), branch: master, commit date: 2019-11-28 22:02, hash: 77c7440540

Short description of error
When I try to render my scene using Optix it fails at "Building accelerated Optix structure" and gives me this error:

OptiX error OPTIX_ERROR_INVALID_VALUE in optixAccelBuild(context, NULL, &options, &build_input, 1, temp_mem.device_pointer, sizes.tempSizeInBytes, out_data.device_pointer, sizes.outputSizeInBytes, &out_handle, NULL, 0), line 876

It works just fine in the live viewport render view

Exact steps for others to reproduce the error
I can't really share the blend file since it's a unreleased project for some filmmakers. But in short it crashes during this part of the process:
2019-11-30 01_18_50-Blender Render.png

Optix works fine in the deafult cube scene. The scene I'm rendering has 900k verts and at least 500k hairs. it includes hair dynamics and cloth physics.

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28 CPU: i9-9900k RAM: 32 GB **Blender Version** Broken: version: 2.82 (sub 2), branch: master, commit date: 2019-11-28 22:02, hash: `77c7440540` **Short description of error** When I try to render my scene using Optix it fails at "Building accelerated Optix structure" and gives me this error: OptiX error OPTIX_ERROR_INVALID_VALUE in optixAccelBuild(context, NULL, &options, &build_input, 1, temp_mem.device_pointer, sizes.tempSizeInBytes, out_data.device_pointer, sizes.outputSizeInBytes, &out_handle, NULL, 0), line 876 It works just fine in the live viewport render view **Exact steps for others to reproduce the error** I can't really share the blend file since it's a unreleased project for some filmmakers. But in short it crashes during this part of the process: ![2019-11-30 01_18_50-Blender Render.png](https://archive.blender.org/developer/F8179923/2019-11-30_01_18_50-Blender_Render.png) Optix works fine in the deafult cube scene. The scene I'm rendering has 900k verts and at least 500k hairs. it includes hair dynamics and cloth physics.
Author

Added subscriber: @koko_ze

Added subscriber: @koko_ze
Author

Ok so I have tried to render it without hair and it works fine. So I guess the hair is the problem.

edit: I tried rendering it with 2/3 of the hair and it worked.

edit2: Now that I have reduced the hair count by about 20% I can see that the peak memory usage is 9GB which is very close to the 11GB limit of my 2080ti.

So in conclusion I guess I ran out of memory.

edit3: does motion blur affect memory? Because I've had it turned on but felt that it was rendering too long so now I've switched to vector blur

Ok so I have tried to render it without hair and it works fine. So I guess the hair is the problem. edit: I tried rendering it with 2/3 of the hair and it worked. edit2: Now that I have reduced the hair count by about 20% I can see that the peak memory usage is 9GB which is very close to the 11GB limit of my 2080ti. So in conclusion I guess I ran out of memory. edit3: does motion blur affect memory? Because I've had it turned on but felt that it was rendering too long so now I've switched to vector blur

Added subscribers: @pmoursnv, @mano-wii

Added subscribers: @pmoursnv, @mano-wii
Patrick Mours was assigned by Germano Cavalcante 2019-12-02 19:59:07 +01:00

@pmoursnv, mind taking a look?

@pmoursnv, mind taking a look?
Member

Sounds like an out of memory, which would cause Cycles to hand a null pointer to optixAccelBuild and fail with that error. But the only way to be sure is to compile Blender with "WITH_CYCLES_LOGGING" enabled to get the full error explanation from OptiX. There is not much I can deduce from just the error code without a reproducer scene.

Sounds like an out of memory, which would cause Cycles to hand a null pointer to optixAccelBuild and fail with that error. But the only way to be sure is to compile Blender with "WITH_CYCLES_LOGGING" enabled to get the full error explanation from OptiX. There is not much I can deduce from just the error code without a reproducer scene.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

In this case, I'm closing the report because not enough information was provided to reproduce the issue.
It can be reopened if more information is provided.

In this case, I'm closing the report because not enough information was provided to reproduce the issue. It can be reopened if more information is provided.

Added subscriber: @LarryGill

Added subscriber: @LarryGill

Yep reducing some hair works thx for helping. it worked for me on 2.9 RTX 2060.

Yep reducing some hair works thx for helping. it worked for me on 2.9 RTX 2060.
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
4 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#72058
No description provided.