Shader Image Mapping Issue #88410
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#88410
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: Mac OSX High Sierra
Graphics card: NVIDiA GeForce
Blender Version
Broken: (example: 2.92 Master
02948a2cab
Worked: N/A
Short description of error
It seems the mapped image is not applying to an object that's linked by Object Data
Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
repro2.blend
In this file, just going in and out of editmode causes the the (rendered) UVs to not be consistent (they appear fine in the UV Editor):
Original report:
modular.blend
Look at the image reference in the shader for the second to last vehicle. All other vehicles with similar bodies are linked and are following the map except the second to last object. After linking the body of that vehicle, the object appears to follow the map until you render the image.
Added subscriber: @Gary-1
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs User Info'
First of all: the image is missing. Please pack that into the file an reupload the .blend file (or attach the image here)
Having said that, the reproduction steps are not entirely clear to me:
That means their meshes have multiple users, right? Just making sure we are talking about the same things
What exatly does "linking" mean here? should the
Cube.001
share its mesh with another object? which one? Please be more specific.And then after rendering what happens? Does it display pink?
First of all: the image is missing. Please pack that into the file an reupload the .blend file (or attach the image here)
should we already see the issue when opening that file? Does this not show the texture? Is it pink?
The texture shows the whole texture image. Take a look at the two front wheels of the second to last vehicle from the left in the screenshot.
Here's a screenshot.
What exatly does "linking" mean here? should the Cube.001 share its mesh with another object? which one? Please be more specific.
And then after rendering what happens? Does it display pink?
All the wheels are linked by material so they should all be showing the same mesh. Interestingly the wheel in question renders fine.
Changed status from 'Needs User Info' to: 'Needs Triage'
Changed status from 'Needs Triage' to: 'Confirmed'
Hm, can actually reproduce (sorry this has been lying around for so long)
repro2.blend
In this file, just going in and out of editmode causes the the (rendered) UVs to not be consistent (they appear fine in the UV Editor):