Regression: location override ignored when used in a shadertree (Texture Coordinates node, object coordinates) #99272
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#99272
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
Operating system: Windows 11
Graphics card: RTX 2060 mobile
Blender Version
Broken: 3.2.0, Caused by {1695d38989fd482d3c010dc9ba4b0cb8e07a7139}
Worked: 3.1.2
It seems the location override does not ripple down into the usage of the location in the
Texture Coordinate
object coordinates.Its coordinates are fine in the 3DView though.
Here is a simplified example:
#99272.zip
lib.blend
with an empty that controls a gradient position on a plane viaTexture Coordinate
object coordinatesmain_override.blend
with the collection fromlib.blend
linked, and the location of the empty overriden.expected:
observed:
Original report
The shading setup made in 3.1.2 yields an unexpected result in 3.2.0 and higher.
3.2.0_Result
3.2.1_Release_Candidate
3.1.2_CORRECT_VERSION
Exact steps for others to reproduce the error
PROJECT.zip
Added subscriber: @Jalmaries
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Confirmed'
I can confirm the problem.
Apparently the nodes in the linked material that return the position of Empties are not returning the correct position.
Certainly the file can be simplified further (I tried but for some reason the objects returned after reloading the file).
I'm investigating to find where the problem was introduced.
Added subscriber: @mont29
{1695d38989fd482d3c010dc9ba4b0cb8e07a7139} is the first bad commit
Author: @mont29
Added subscriber: @lichtwerk
OK, it seems the location override does not ripple down into the usage of the location in the
Texture Coordinate
object coordinates.Its coordinates are fine in the 3DView though.
Here is a simplified example:
#99272.zip
lib.blend
with an empty that controls a gradient position on a plane viaTexture Coordinate
object coordinatesmain_override.blend
with the collection fromlib.blend
linked, and the location of the empty overriden.Errors after updating from 3.1.2 to 3.2.0to Regression: location override ignored when used in a shadertree (Texture Coordinates node, object coordinates)This issue was referenced by
7f24d90f11
Changed status from 'Confirmed' to: 'Resolved'
Added subscriber: @noc2
You guys marked this as "Fixed" yet the bug persists. What gives???????
EDIT: Just found out now that the shader tree setup in the source library works as expected only if it is linked to the main scene from scratch and the scene file is saved. Yet, the result is as before when the original scene file is opened in 3.2.1 So, the whole scene needs to be assembled from scratch in this case??
This comment was removed by @Jalmaries
Tested the scene on 3.2.1 and the bug is still there. Did you actually test your bug fix on the scene that I sent you before marking the bug report as fixed? Any hope linking will be fixed on this version or will we have to wait for 3.3 and higher to be able to use library linking in production work.
EDIT: The problem occurs while upgrading version, linking from start in 3.2.1 works fine. While tresspassing in versions document corrupts.
Added subscriber: @LazyDodo
Bug is currently only fixed in master, you'd have to download a nightly 3.3 build from builder.blender.org to test it.
So this didn't actually make it into 3.2.1??? What's the point of having a bug fix release if such crucial bugs are fixed solely toward a main release? You guys came up saying that 3.2's file referencing was improved. Here's a really crucial bug with file linking and it only makes it into master. I'm stumped... :( :( :(
Also as a reminder, overrides of materials remain dodgy at best, and is not officially supported so far.