UV Map node not fully working #39808

Closed
opened 2014-04-20 14:50:53 +02:00 by Gwenael Le Page · 13 comments

Blender 2.70, buildbot from the 20/4 regular win 64 build. Hash b4cb467

I am not sure what to think about that, it may well be me doing something wrong…

I was playing with todays buildbot build and noticed the UV Map node. Very handy to input a UV map, more logical that the "Attribute" node.

But i couldn't use the UV for displacement.
You'll find a very very crude file here:
Bug_UVMaps_input.blend

Go to rendered view, and select the "UV Map" node as input for your UV, and the displacement won't work, whereas it works with Attribute or Texture coordinates nodes.

It will work if you use the image for the color info though…

Blender 2.70, buildbot from the 20/4 regular win 64 build. Hash b4cb467 I am not sure what to think about that, it may well be me doing something wrong… I was playing with todays buildbot build and noticed the UV Map node. Very handy to input a UV map, more logical that the "Attribute" node. But i couldn't use the UV for displacement. You'll find a very very crude file here: [Bug_UVMaps_input.blend](https://archive.blender.org/developer/F85400/Bug_UVMaps_input.blend) Go to rendered view, and select the "UV Map" node as input for your UV, and the displacement won't work, whereas it works with Attribute or Texture coordinates nodes. It will work if you use the image for the color info though…

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @gwentiv

Added subscriber: @gwentiv

Added subscribers: @brecht, @kevindietrich

Added subscribers: @brecht, @kevindietrich

I did the implementation of that node, and "displacement" wasn't included, so it seems more like a feature request than a bug.

@brecht: what do you think about that ? I could do it :) (just assign this to me)

I did the implementation of that node, and "displacement" wasn't included, so it seems more like a feature request than a bug. @brecht: what do you think about that ? I could do it :) (just assign this to me)

Added subscriber: @willi-2

Added subscriber: @willi-2

Confirmed. Strange indeed. If you connect the UV map node to an emission shader, the result is the same as if you connect the Vector node of the Attribute node to the emission shader. This indicates there should be no difference.
Internally, there must be something global that is not passed through as expected if the Displacement pin is used, I think.

Confirmed. Strange indeed. If you connect the UV map node to an emission shader, the result is the same as if you connect the Vector node of the Attribute node to the emission shader. This indicates there should be no difference. Internally, there must be something global that is not passed through as expected if the Displacement pin is used, I think.

Yes kevindietrich, I wasn't sure as well, that's why i started my post this way.

But why should it make a difference if you want to use a UV Map for a color or a displacement ?
I think it should behave just like the other nodes with UV output sockets do.

Yes kevindietrich, I wasn't sure as well, that's why i started my post this way. But why should it make a difference if you want to use a UV Map for a color or a displacement ? I think it should behave just like the other nodes with UV output sockets do.
Kévin Dietrich self-assigned this 2014-04-20 18:25:34 +02:00

Sorry, I downloaded your file but forgot to test it, I see what you mean now.

I didn't included the displacement because, by looking at the code (for the other nodes), it felt different than what it is actually doing and also, to me, the displacement was supposed to be no different than color info (if you know what I mean).

Anyway, guess I have no choice but fixing this. I'll try to have a patch for this ASAP.

Sorry, I downloaded your file but forgot to test it, I see what you mean now. I didn't included the displacement because, by looking at the code (for the other nodes), it felt different than what it is actually doing and also, to me, the displacement was supposed to be no different than color info (if you know what I mean). Anyway, guess I have no choice but fixing this. I'll try to have a patch for this ASAP.

Added subscriber: @mont29

Added subscriber: @mont29

This issue was referenced by blender/blender-addons-contrib@83988b6cdd

This issue was referenced by blender/blender-addons-contrib@83988b6cdd181fb572b2f4dd078c165a583497fd

This issue was referenced by 83988b6cdd

This issue was referenced by 83988b6cdd181fb572b2f4dd078c165a583497fd

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Closed by commit 83988b6cdd.

Closed by commit 83988b6cdd.
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#39808
No description provided.