Volume rendering with GPU bug #50808
Labels
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#50808
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 10, Intel Core i7 5820K, 32GB, NVIDIA GeForce GTX 1070
Blender Version
Broken: 2017-02-25 02:12 Hash:
8c5826f
Worked: (optional)
Short description of error
Some CUDA errors like: cuCtxCreate: Launch failed
or corrupted image when switching volume on.
Exact steps for others to reproduce the error
Sorry, I am a beginner with blender
If I choose Volume (Glass BSFD) in world, CPU rendering is normal,
but GPU Compute fails with error or disrupted image.Volume.blend
Changed status to: 'Open'
Added subscriber: @Wigand
I can't see any issues with the attached file on GTX1080.
What are the exact steps reproducing the bug with the file attached?
Open Blender
Select World
Volume
Select Glass Bsdf
Render with Cycles on GPU
No Error if using CPU
Same with bmw27_gpu
Changed status from 'Open' to: 'Archived'
Had a look here. So far managed to reproduce on Windows, didn't see this error on Linux. Most likely it's because of different timeout policies on different platforms (those timeouts are dictated by driver and OS and out of our control). The issue is very similar to the one described in out manual - [x]. It is not solvable in general case for as long as the card is not dedicated for compute (aka, has monitor attached to it).
Some ongoing development which could improve situation here:
Using non-volume and non-emission BSDF for volume output is quite meningless and not supported by the renderer. It is more like a corner case which is allowed by the interface. Such issue is i'm trying to address in D2569.
Using automatic workload size for GPU. Currently the workload on GPU equals to tile size (which is 1024 for viewport render) which could be a bit too much. Some adaptive scaling of workload could help here.
For now i'd just suggest avoid having such a setups which confuses render engine or use CPU for a complex scenes or use a dedicated card for compute. There is really not much we can do about such issues.
Thanks for the report anyway.