Page MenuHome
Create Task
Maniphest T86220

2.92.0 - Can't enter viewport rendering with experimental feature set and device set to GPU
Closed, ArchivedPublic
Actions

Description

System Information
Operating system: Windows 10
Graphics card: MSI Nvidia 3090 Gaming Trio (using Optix)

Blender Version
Broken: 2.92.0

Short description of error
Can't enter viewport rendering with the default cube when feature set is set to experimental and device is set to GPU.

Exact steps for others to reproduce the error

  • Open Blender
  • Set Render Engine to Cycles
  • Set Feature Set to Experimental
  • Set Device to GPU
  • Enter viewport rendering
  • An error appears:
Failed to create CUDA context (illegal address)

Another bug that might be relevant
I found another bug that might be a part of this bug, the second one prints a file and a line in code, but I can't reproduce it from a blank file since I can't get past this one. The second scene includes having an adaptive subdiv on a plane that covers most of the viewport and a bezier curve with geometry->bevel->any depth. When I hide the plane while viewport rendering is on I get an error:

CUDA__ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:816)

When the plane is smaller the error doesn't appear. Should I create a separate report for the second one even tho I can't recreate the steps? I can send the file if you want to look into it. The file was created earlier using a 2.92 alpha version.

Event Timeline

Milan Spasic (milanrs) created this task.Mar 3 2021, 2:26 AM
Milan Spasic (milanrs) updated the task description. (Show Details)Mar 3 2021, 2:52 AM
Pratik Borhade (PratikPB2123) changed the task status from Needs Triage to Needs Information from User.EditedMar 3 2021, 10:47 AM
Pratik Borhade (PratikPB2123) added a subscriber: Pratik Borhade (PratikPB2123).

Thanks for the report , error does not appear on blender version 2.93.0 alpha . Can you try with latest build https://builder.blender.org/download/ ??

Another bug that might be relevant

Try latest build first, in case still getting the issue , create separate task .

Pratik Borhade (PratikPB2123) closed this task as Archived.Mar 14 2021, 1:30 PM

More than a week , no activity from author of ticket . As per the tracker policy we assume the issue is gone and can be closed.

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