UV Editor doesn't work when GPU Subdivision in the Viewport is enabled #96372
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#96372
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.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79
Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash:
c77597cd0e
Short description of error
I was unwrapping a very simple model when I noticed a weird, unpredictable behavior in the UV Editor. Specifically:
I initially thought that some of my addons was causing this, so I've disabled them, but the problem persisted. After some time, I've realized that disabling the Subdivision modifier solved the issue and made unwrapping predictable again. Thus, I've finally come to the conclusion that the new GPU Subdivision setting is the culprit. I confirm that disabling this setting makes everything work fine again.
Exact steps for others to reproduce the error
I have also attached the file I was working on. I hope it can be useful for confirming this bug.
jar_model.blend
Added subscriber: @scopelma
#96628 was marked as duplicate of this issue
Added subscribers: @kevindietrich, @deadpin
Changed status from 'Needs Triage' to: 'Confirmed'
CC @kevindietrich
Added subscriber: @PratikPB2123
Added subscriber: @josemartinez-2
Added subscriber: @josephhansen
The Align X and Align Y operators for UV Editing don't work correctly either with GPU Subdivision on- you have to use each operator 20-30 times before it actually aligns correctly
This issue was referenced by
3bc0e39850
This issue was referenced by
612ec0ecdf
Changed status from 'Confirmed' to: 'Resolved'
I could not reproduce the corrupted data case.
@josephhansen this should be reported separately.
@kevindietrich hi, can this be backported to 3.1 corrective release?