Cycles Displacement node makes Blender prone to crash #53978
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#53978
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
Mac OS 10.13.2 ; iMac Retina 5K (late 2015) 16GB RAM ; AMD Radeon R9 M395X 4GB
Blender Version
Broken: 2.79 builds that include the Cycles Displacement node ; all 2.80 so far (Feb 1).
Worked: 2.79 of Jan 20th, 2018.
Short description of error
Character with many Cycles materials, including some with displacement, makes Blender crash if I try to render.
Exact steps for others to reproduce the error
Open attached .blend file; try to render. DisplacNodeCrash.blend
[THANK you!]
Added subscriber: @ttelos
#53987 was marked as duplicate of this issue
Added subscriber: @MaiLavelle
This was caused by
7261d675e6. Nothing to do with displacement, but rather bad memory access in OSL code.This issue was referenced by blender/cycles@9a66368033
This issue was referenced by
b2dc0e6970Changed status from 'Open' to: 'Resolved'
THANK YOU!
How long until your commit shows up in https://builder.blender.org/download/ ?
Builds are done nightly, so look for it tomorrow.
Added subscriber: @FloridaJo
Feb 02 builds work like a charm! Thank you, again.
But, what is the purpose of the Displacement node?
Here is a test render of an Oryx-style horn, done with Blender 2.79 dated February 2nd,
that inserts a default Displacement node automatically,
and where I have set the material’s Displacement Setting to “Bump Only”:
Here is the same, set to “Displacement Only”:
It retains the detail of “Bump Only”, and adds some true displacement. Good.
But when I choose Bump and Displacement, I lose detail:
A pre-Displacement-node render, done with a Blender 2.79 dated January 20th,
using Displacement=Both:
gives me a better result than Bump and Displacement with the Displacement node active.
What am I misunderstanding, here?
Added subscriber: @brecht
The displacement issue should be opened as a separate task for organization purposes.
I want to say its because the feature is still experimental and we haven't gotten everything sorted out yet, but apparently that's no longer the case... @brecht, do you want to fix this?
Displacement + Bump worked well in my tests. So please create a new report with a .blend attached, and I'll fix it.
THANK you, gentlemen!
The difference I see, occurs with my complete WIP, but disappears when I reduce my .blend file to just one horn,
so the bug, if any, is truly arcane. I shall report it if I discover a minimal set of circumstances that triggers it.
Again: thank you!
Ok, we want to fix bugs that happen in more rare situations as well though. So if you want to attach the more complicated .blend, I'd be interested to fix it.
THANK you, Brecht!
My WIP has become rather cluttered, so it’s overdue for some Spring Cleaning, which I am in the process of.
If, after that, the problem still persists, I shall definitely show you some details. ^_^
So far, so good: https://sta.sh/21968qcn7oqe
Your Cycles is a marvel, Brecht. I used to be a fan of LuxRender,
but the Cycles nodes, and OSL, and Blender integration, and oh-so-FAST, even without CUDA!
That’s it for me. I’m not even looking at another renderer.