Incorrect Auto Texture Space in both viewport and render, and with and w/o modifiers #64739
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
10 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#64739
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-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31
Blender Version
Broken: version: 2.80 (sub 68), branch: master, commit date: 2019-05-16 17:17, hash:
3076544c8c
Let me know if it's better to split these into multiple bugs. They're just very related, like different expressions of the same problem, and I wanted to show them all at once
Short description of error(s)
A) During render and with a modifier on a mesh, even with Auto Texture Space (ATS) OFF, it will behave as if ATS is ON, and not even in the shape of the original mesh, but one that stretches and bounds the entire modified mesh (eg if a mesh has a mirror modifier, the bounds of the Texture Space is a wide as the final mesh, something that doesn't happen in 2.79) (I haven't tested every modifier)
B) If you were using ATS OFF with custom bound values, and then turn it ON back again, the values of the bound won't update to reflect it until you reload the file or undo. (In 2.79 you could simply enter into edit mode and the values would update) But this has weird consequences for that period in which ATS is ON but the values don't reflect it:
C) During render, and without a modifier, even with ATS ON, it will render with ATS OFF and the old bound values. But if it has a modifier, bug A) happens
D) On the Lookdev viewport however, you can see the correct ATS on the material as soon as you turn it ON, even on meshes with modifers and even though the values of the bound still won't updated. But you realize that it's not truly working when you render and bugs C) and A) happen, or when you enter and exit edit mode and see the old custom Texture Space still working instead of the ATS that we want
All in all, bug C) and bug D) would disappear if bug B) got fixed to update the values more instantly. But that still leaves bug A) Meshes with modifiers during render won't use either the custom texture space nor the ATS of the original unmodified mesh (render engine doesn't seem to matter)
Exact steps for others to reproduce the error
[Based on the default startup or an attached .blend file (as simple as possible)]
Use lookdev or rendered shading mode
To observe bug A) open the file and just render F12. The entire column of objects with modifers will have the wrong texture space
To observe bugs B) C) and D), since these get cured as soon as a file is reloaded, you have to turn off Auto Texture Space on the last two rows of objects, input custom texture space bound values (like Loc0,0,0 Scale 1,0.2,0.2 to use the same I used) and then turn ATS on again. You have to enter and exit edit mode on the last row too and this should replicate the images attached. Observe how the bound values remain the same still.
To observe the ATS updating the bounding values, Save and Reload.
I hope the checkmarks gives you an idea on how things should look properly. With and without modifier, with and without ATS, and the same across viewport and render with no differences
texture space bug.blend
Added subscriber: @moisessalvador
#69949 was marked as duplicate of this issue
#69285 was marked as duplicate of this issue
#68614 was marked as duplicate of this issue
#68336 was marked as duplicate of this issue
#67569 was marked as duplicate of this issue
#67211 was marked as duplicate of this issue
#66129 was marked as duplicate of this issue
Added subscribers: @fclem, @ZedDB
I can confirm that the result differs between viewport and render for both eevee and cycles.
@brecht, @fclem any ideas?
Added subscriber: @brecht
Added subscriber: @JonathanLampel-4
Added subscriber: @mano-wii
Changed status from 'Open' to: 'Resolved'
Fixed on
8a1552545a
Added subscriber: @VilemDuha
Changed status from 'Resolved' to: 'Open'
this isn't still fixed, see the file below, where still about half of the generating (mesh changing) modifiers switches back to auto:
bugbug.blend
@brecht, even with your fix, some modifiers continue to affect the
Texture Space
.For example the boolean in the file attached in the comment above.
Added subscriber: @CMC
Added subscriber: @NahuelBelich
Added subscriber: @MassimilianoPuliero
Added subscriber: @careaux
Added subscribers: @MikeFutcher, @lichtwerk
Added subscriber: @Consta
list of affected modifiers in #69285 (Manual generated texture coordinates are overwritten by auto-generated ones when certain modifiers are applied)
It is reported often, and since it is a regression, I dare setting this to High prio.
Removed subscriber: @fclem
@brecht : I have added this to 2.81 milestone (since it was set to "High"), mind checking again?
This issue was referenced by
a168c3d282
This issue was referenced by
e7a514369f
Added subscriber: @bernardoiraci
Changed status from 'Open' to: 'Resolved'
This issue was referenced by
7926e8ea4c
Changed status from 'Resolved' to: 'Open'
The fix caused another bug, reverted for now, will look at it again next week.
Changed status from 'Open' to: 'Resolved'
Thank you guys!
PS: I am new to the developers commit system, so if this kind of comments are not welcome due to unnecessary notification and crowding, please let me know. I just felt like expressing my gratitude for looking into this)