In "UV Editor", the movement of UV objects in pixels of an open texture map stopped working when using the [g]+[x/y] keyboard shortcuts (Blender 2.91) #83352
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#83352
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: all
Graphics card: all
Blender Version
Broken: 2.91, 2.92; Bisecting points to
4eda60c2d8Worked: 2.83.9, 2.90.1
Short description of error
In "UV Editor", the movement of UV objects in pixels of an open texture map stopped working when using the - [x]+[x/y] keyboard shortcuts.
Exact steps for others to reproduce the error
Bottom line: the offset is not in pixels! In version 2.90.1 it works correctly!
Added subscriber: @Qwer
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Archived'
This comment was removed by @rjg
In case I've misunderstood your report, please leave a comment and we can reopen the ticket.
Changed status from 'Archived' to: 'Needs Triage'
I've misread the report, the transformation is not applied in pixel units.
This comment was removed by @rjg
This comment was removed by @rjg
I'm very sorry for making all my mistakes on this ticket today. Apparently 2.92 is also affected by this problem.
I can confirm this issue in 2.91.0 and 2.92.0. The commit that broke this happened somewhere between
cf0ba59e31(good) and63f525bae3(bad).Changed status from 'Needs Triage' to: 'Confirmed'
Mistakes happen, it's not a big deal. I was a little scared when I found out that it didn't work. Now I'm glad that this will probably be fixed. I can still use 2.90.1.
Added subscriber: @mano-wii
It seems that this was caused by
4eda60c2d8@mano-wiiThis issue was referenced by
8de98d68c2This issue was referenced by
f3b08af24cChanged status from 'Confirmed' to: 'Resolved'