Generated texture coordinates incorrect on file load in presence of modifiers #73944

Open
opened 2020-02-17 20:58:34 +01:00 by Nathan Vasil · 11 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7
Also broken: 2.83 alpha, hash f6d5a95513

Short description of error
Generated texture coordinates are using modified vertex position on file load, apparently until those modifiers are edited, for rendered preview (only). Actual rendering appears to use generated texture coordinates from unmodified vertex position.

Exact steps for others to reproduce the error
Here's a file with a candy stripe material using generated texture coordinates, with a simple deform/twist modifier:

gentest.blend

Open it up, don't change anything, and switch to a rendered preview:

image.png

Render and compare:

renderedgen.png

Editing the twist angle on the modifier updates the generated coords to work appropriately, and can be considered a work-around, but it's painful to do this on every file load, for every deformed object using generated texture coordinates.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: `77d23b0bd7` Also broken: 2.83 alpha, hash f6d5a9551380 **Short description of error** Generated texture coordinates are using modified vertex position on file load, apparently until those modifiers are edited, for rendered preview (only). Actual rendering appears to use generated texture coordinates from unmodified vertex position. **Exact steps for others to reproduce the error** Here's a file with a candy stripe material using generated texture coordinates, with a simple deform/twist modifier: [gentest.blend](https://archive.blender.org/developer/F8345664/gentest.blend) Open it up, don't change anything, and switch to a rendered preview: ![image.png](https://archive.blender.org/developer/F8345647/image.png) Render and compare: ![renderedgen.png](https://archive.blender.org/developer/F8345654/renderedgen.png) Editing the twist angle on the modifier updates the generated coords to work appropriately, and can be considered a work-around, but it's painful to do this on every file load, for every deformed object using generated texture coordinates.
Author

Added subscriber: @vasiln

Added subscriber: @vasiln
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

I can confirm that the generated coordinates on the object are different when comparing the viewport and a render. This is true for Cycles and Eevee.

I can confirm that the generated coordinates on the object are different when comparing the viewport and a render. This is true for Cycles and Eevee.
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

@JacquesLucke is this also related then #73956 ?

@JacquesLucke is this also related then #73956 ?
Member

I don't know if it is related. The issue you linked does not have enough information to determine that yet.

I don't know if it is related. The issue you linked does not have enough information to determine that yet.

Added subscriber: @fclem

Added subscriber: @fclem

The workaround does not even seem to work now. I guess it's a bug in the modifier stack evaluation that think it can skip ORCO since we are in solid shading mode at first.

This happens for all deforming modifiers.

The workaround does not even seem to work now. I guess it's a bug in the modifier stack evaluation that think it can skip ORCO since we are in solid shading mode at first. This happens for all deforming modifiers.

Added subscriber: @AaronBeller

Added subscriber: @AaronBeller

Hey everybody,
I was about to write a new bug report when I found this open task. I was running into the same issue when using the array & curve modifiers. I couldn't reliably reproduce the bug though. Sometimes (not every time) the generated coordinates are scrambled when loading the file. One time changing the shading from flat to smooth would change the displayed coordinates. Changing the position of the subsurf modifier in the stack back an d forth solved the issue most of the time but again not always.
Wrong coordinates
wrongCoordinates.jpg
Right coordinates
rightCoordinates.jpg
Here's my system information just in case:
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-05-29 16:16, hash: f5d14e36e8

And here's the file:
GeneratedCoordinates_Bug.blend

I'm not sure if this adds any new information to the case but I figured it might help. So thank you for looking into it and keep up your amazing work!
Best regards
Aaron

Hey everybody, I was about to write a new bug report when I found this open task. I was running into the same issue when using the array & curve modifiers. I couldn't reliably reproduce the bug though. Sometimes (not every time) the generated coordinates are scrambled when loading the file. One time changing the shading from flat to smooth would change the displayed coordinates. Changing the position of the subsurf modifier in the stack back an d forth solved the issue most of the time but again not always. Wrong coordinates ![wrongCoordinates.jpg](https://archive.blender.org/developer/F10149054/wrongCoordinates.jpg) Right coordinates ![rightCoordinates.jpg](https://archive.blender.org/developer/F10149056/rightCoordinates.jpg) Here's my system information just in case: **System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-05-29 16:16, hash: `f5d14e36e8` And here's the file: [GeneratedCoordinates_Bug.blend](https://archive.blender.org/developer/F10149061/GeneratedCoordinates_Bug.blend) I'm not sure if this adds any new information to the case but I figured it might help. So thank you for looking into it and keep up your amazing work! Best regards Aaron
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#73944
No description provided.