Page MenuHome

Error at "Building OptiX acceleration structure"
Closed, ArchivedPublic

Description

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: rB77c744054062

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:

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.

Details

Type
Bug

Event Timeline

Anže (koko_ze) added a comment.EditedSat, Nov 30, 12:41 PM

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

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.

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.