Displacement in diagonal direction #54013

Closed
opened 2018-02-06 16:09:02 +01:00 by filip mond · 7 comments

System Information
OS X 10.12.6, NVIDIA GeForce GTX 780M 4096 MB

Blender Version
Broken: 2.79 ce3e0afe59 (daily build)
Worked: 2.79 (official release)

Short description of error
Checker map texture used for displacement does not direct to straight up.
(adaptive sudivision)

v2.79 (official release)
v2.79.jpg

v2.79 (daily build - 6.2.2018)
v2.79 (daily build) copy.jpg

test_Displace_Checker.blend

**System Information** OS X 10.12.6, NVIDIA GeForce GTX 780M 4096 MB **Blender Version** Broken: 2.79 ce3e0afe597 (daily build) Worked: 2.79 (official release) **Short description of error** Checker map texture used for displacement does not direct to straight up. (adaptive sudivision) v2.79 (official release) ![v2.79.jpg](https://archive.blender.org/developer/F2146600/v2.79.jpg) v2.79 (daily build - 6.2.2018) ![v2.79 (daily build) copy.jpg](https://archive.blender.org/developer/F2146601/v2.79__daily_build__copy.jpg) [test_Displace_Checker.blend](https://archive.blender.org/developer/F2146754/test_Displace_Checker.blend)
Author

Added subscriber: @FilipMond

Added subscriber: @FilipMond

Added subscriber: @brecht

Added subscriber: @brecht

You need to use a Displacement node now:
https://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.80/Cycles#Subdivision_and_Displacement

.blend files created with previous versions are supposed to be automatically converted, is that not the case for you?

You need to use a Displacement node now: https://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.80/Cycles#Subdivision_and_Displacement .blend files created with previous versions are supposed to be automatically converted, is that not the case for you?
Author

Yeah it works now :) Thank you

Note: On page is written "This node will be automatically inserted into existing .blend files."
From "automatically inserted" I understood - if I try to connect texture directly to displacement, this "Displacement" node will be inserted in between nodes automatically.
Is that correct? Because it doesn't happen right now.

Also adding this node on string (between texture and output node), lets blender connect texture into "Normal" socket thats not correct for greyscale images.
It should be "Height" for greyscale.
Is that something that can be solved by blender?
For texture like checker node that is seen as RGB probably not, but for greyscale texture?

I know its not the topic of this thread, sorry. Just if you see it reasonable to ask for changes like that.

Yeah it works now :) Thank you Note: On page is written "This node will be automatically inserted into existing .blend files." From "automatically inserted" I understood - if I try to connect texture directly to displacement, this "Displacement" node will be inserted in between nodes automatically. Is that correct? Because it doesn't happen right now. Also adding this node on string (between texture and output node), lets blender connect texture into "Normal" socket thats not correct for greyscale images. It should be "Height" for greyscale. Is that something that can be solved by blender? For texture like checker node that is seen as RGB probably not, but for greyscale texture? I know its not the topic of this thread, sorry. Just if you see it reasonable to ask for changes like that.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2018-02-06 18:26:49 +01:00

It will be automatically inserted in existing .blend files that already have displacement. Not when connecting a texture to displacement, since we don't know if you're using Displacement, Vector Displacement, or something custom.

About what happens when inserting a new node between, this system is not all that clever, since you had originally connected it to a vector output it assumed that's the type you wanted it connected to. We can try to make that smarter, but would not consider this a bug for now.

It will be automatically inserted in existing .blend files that already have displacement. Not when connecting a texture to displacement, since we don't know if you're using Displacement, Vector Displacement, or something custom. About what happens when inserting a new node between, this system is not all that clever, since you had originally connected it to a vector output it assumed that's the type you wanted it connected to. We can try to make that smarter, but would not consider this a bug for now.
Author

OK, I get it.
Thanks for patience :)
From word "existing" wasn't clear it's saved/open blend file (or file from previous versions) for me.
"Existing" .blend file is also current file I'm working on for me.
(Caused probably by my english?)

Auto Height/Normal connect question wasn't meant as a bug of course, mostly proposal on wrong place.

OK, I get it. Thanks for patience :) From word "existing" wasn't clear it's saved/open blend file (or file from previous versions) for me. "Existing" .blend file is also current file I'm working on for me. (Caused probably by my english?) Auto Height/Normal connect question wasn't meant as a bug of course, mostly proposal on wrong place.
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
2 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#54013
No description provided.