Cycles OptiX portal area light toggle error #85023

Closed
opened 2021-01-24 19:25:10 +01:00 by ZahoTo · 9 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09

Blender Version
Broken:
version: 2.90.1
version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash: 0f45cab862
version: 2.92.0 Beta, branch: master, commit date: 2021-01-22 18:24, hash: a1f44e43a2
version: 2.93.0 Alpha, branch: master, commit date: 2021-01-17 11:35, hash: 4ef0654449
version: 2.93.0 Alpha, branch: master, commit date: 2021-01-24 23:16, hash: cf6d17a6aa
Worked: Never

Short description of error
When Area light portal toggle is switched on, while using Cycles with OptiX and Rendered Viewport shading, error occurs:

OPTIX_ERROR_INVALID_VALUE in optixLaunch(pipelines[PIP_SHADER_EVAL], cuda_stream[thread_index], launch_params_ptr, launch_params.data_elements, &sbt_params, task.shader_w, 1, 1) (device_optix.cpp:1136)

After that you can just switch to other Viewport shading and back to Rendered and it works normally.
Works with CUDA renderer, so it's just OptiX specific.
Also, when I disable my GeForce in OptiX properties and enable Intel Core, the everything works properly. It might be connected with Nvidia cards or GTX 1050ti.

Exact steps for others to reproduce the error

  • Make sure OptiX is selected in Preferences/System/Cycles Render Devices and Cycles is selected as Render Engine
  • Create Arealight
  • Turn on Rendered Viewport shading
  • Toggle Portal option in Light Properties
  • Error occurs
**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09 **Blender Version** Broken: version: 2.90.1 version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash: `0f45cab862` version: 2.92.0 Beta, branch: master, commit date: 2021-01-22 18:24, hash: `a1f44e43a2` version: 2.93.0 Alpha, branch: master, commit date: 2021-01-17 11:35, hash: `4ef0654449` version: 2.93.0 Alpha, branch: master, commit date: 2021-01-24 23:16, hash: `cf6d17a6aa` Worked: Never **Short description of error** When Area light portal toggle is switched on, while using Cycles with OptiX and Rendered Viewport shading, error occurs: > OPTIX_ERROR_INVALID_VALUE in optixLaunch(pipelines[PIP_SHADER_EVAL], cuda_stream[thread_index], launch_params_ptr, launch_params.data_elements, &sbt_params, task.shader_w, 1, 1) (device_optix.cpp:1136) After that you can just switch to other Viewport shading and back to Rendered and it works normally. Works with CUDA renderer, so it's just OptiX specific. Also, when I disable my GeForce in OptiX properties and enable Intel Core, the everything works properly. It might be connected with Nvidia cards or GTX 1050ti. **Exact steps for others to reproduce the error** - Make sure OptiX is selected in Preferences/System/Cycles Render Devices and Cycles is selected as Render Engine - Create Arealight - Turn on Rendered Viewport shading - Toggle Portal option in Light Properties - Error occurs
Author

Added subscriber: @ZahoTo

Added subscriber: @ZahoTo

#85108 was marked as duplicate of this issue

#85108 was marked as duplicate of this issue

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

Added subscriber: @ChrisGraz

Added subscriber: @ChrisGraz

Added subscribers: @pmoursnv, @brecht

Added subscribers: @pmoursnv, @brecht

@pmoursnv, toggling the portal means requested_features.use_background_light changes, and I see the OptiX kernels being reloaded in response to that. But somehow it still gives an error.

It's not clear to me why this fails, while adding e.g. SSS or an AO node seems to reload the kernels without error. Maybe background shader evaluation is different because it happens as part of scene update rather than rendering.

@pmoursnv, toggling the portal means `requested_features.use_background_light` changes, and I see the OptiX kernels being reloaded in response to that. But somehow it still gives an error. It's not clear to me why this fails, while adding e.g. SSS or an AO node seems to reload the kernels without error. Maybe background shader evaluation is different because it happens as part of scene update rather than rendering.
Brecht Van Lommel changed title from Portal Area light toggle Error to Cycles OptiX portal area light toggle error 2021-01-27 17:55:53 +01:00
Member

@brecht I don't see requested_features.use_background_light changing when toggling portal. The problem appears to be that kernels are reloaded before the background light is enabled again (which happens in LightManager::test_enabled_lights, which is called after the kernel reload):

Starting with Portal off

  • background light always enabled by sync_background_light

  • load_kernels with use_background_light = true

  • LightManager::test_enabled_lights disables background light

  • [...] (camera is modified in the meantime, so another update + reload is triggered)

  • load_kernels with use_background_light = false

  • actual rendering begins
    Now turning Portal on

  • background light is still disabled from before

  • load_kernels with use_background_light = false

  • LightManager::test_enabled_lights enables background light because portal is used!

  • LightManager::device_update_background is called and kicks of shader evaluation task .... (without kernels being reloaded and therefore the last load was with use_background_light = false)

@brecht I don't see `requested_features.use_background_light` changing when toggling portal. The problem appears to be that kernels are reloaded before the background light is enabled again (which happens in `LightManager::test_enabled_lights`, which is called after the kernel reload): Starting with Portal off - > background light always enabled by `sync_background_light` - > `load_kernels` with `use_background_light = true` - > `LightManager::test_enabled_lights` disables background light - > [...] (camera is modified in the meantime, so another update + reload is triggered) - > `load_kernels` with `use_background_light = false` - > actual rendering begins Now turning Portal on - > background light is still disabled from before - > `load_kernels` with `use_background_light = false` - > `LightManager::test_enabled_lights` enables background light because portal is used! - > `LightManager::device_update_background` is called and kicks of shader evaluation task .... (without kernels being reloaded and therefore the last load was with `use_background_light = false`)

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Brecht Van Lommel self-assigned this 2021-11-05 23:05:31 +01:00

Appears to be solved in Blender 3.0.

Appears to be solved in Blender 3.0.
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
5 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#85023
No description provided.