Bug while moving vertices with mirror & subdivision modifier #73952
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#73952
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 64-bit
Graphics card: ATI Radeon HD 5670
Blender Version
Broken: 2.82
Worked: at least 2.8
Short description of error
When I try to move a vertice it seems like the mirror modifier gets applied in an odd way. The result even changes when moving the camera or hide one of the images I use for reference. In fact it becomes distorted when hiding the images.
The following link is a recording of my screen:
https://drive.google.com/file/d/1nMcav4BC-5rgHh4AyBaelUOIKxwbE-p5/view?usp=sharing
I encountered this bug only recently. The file itself is older and I do not remember which version I used (since I use it via Steam I did not pay attention to the automatic patches).
Exact steps for others to reproduce the error
system-info.txt
Added subscriber: @publicStupidity
Added subscriber: @ideasman42
Changed status from 'Needs Triage' to: 'Needs User Info'
I can't redo this error in 2.82 release or master
ca72ff599a
.I opened the file in 2.80 without any sightings of this bug.
Loading factory settings in my current Steam version wouldn't change anything yesterday or today and I even installed it anew but the bug still exists. It looks like everything is normal on startup but as soon as I change visibility of the mirror and subdivision modifiers it goes back to what you can see in the video.
@publicStupidity please upload the file at the point where transforming fails.
It's possible something you're doing causes the issue to fail, which I'm not doing.
Also, check if this error exists in 2.81.
It's not really a transforming failure I realized. I just need to change some options for the modifiers and it does weird things to the selected vertices without me moving them, if I move them though it starts to get as messy as in that video.
File.blend
These screenshots are all made in 2.81 with the current state of the file. 2.8 loads it without these weird lines to the center of the object.
When loading it in my Steam version it starts out with the same weird lines but as I change the visibility options for the subdivision modifier they vanish. Here it seems to bug out at random though after going through different settings (multiple times for both mirror and subdivision).
I'm not sure though if the new file will make a difference for you since "Bugged Project" already looked like this for me on startup (screenshot also taken in 2.81). This file also looks normal on startup in 2.8 (meaning the line going to the right side with a vertice I never placed there is gone).
I should note this is what I see with the images disabled, once I make them visible the vertices get placed to a certain spot in relation to the image axis or something like that (as seen as in the screenshot of "Bugged Project"). You could see in the video what happens when I move the vertices along the Y axis: the whole object turns transparent and the regular gray object appears rotated in correlation to one of the images.
To me it seems like the mirror modifier is broken. At least with On Cage enabled for this modifier it looks broken.
Note that this report is still missing exact steps to redo the bug, which would be good to list so others can be sure they're checking the same issues.
However this may be spesific to your hardware, since we would be getting a lot of reports if it was common issue.
Both 2.82 release & master work here.
The graphics card driver is up to date as the graphics card I stated in the first post is rather old. It would be unfortunate if that is the cause of this bug but at least I do not encounter this in 2.80...
It in fact worked fine on another computer with the current Steam version of 2.82.
That's what I already did as it's not possible to chose a version through Steam as far as I know (and I had checked the 2.82 version there as well)
It's a similar result there as well for my computer.
I tried it with a cube: This only happens with an image loaded into the scene, doesn't matter if it was inserted through Empty -> Image or Image -> Reference / Image -> Background. For some reason there is a cube around the image with the initial cube right inside of it. This cube vanishes once switched to edit mode though and won't affect normal editing of the vertices in any way. However as soon as I cut the cube in half and add mirror on it every vertice of the cube is attached to a vertice of the cube that got created by inserting the image. It's not visible when adding the mirror but as soon as I move any vertice of the actual cube the attached vertice of this "image cube" that shouldn't be there will move as well but not always into the same direction as apparently the axis of that object is rotated.
If this is in fact mainly a hardware issue then I'm sorry if this was just a waste of time but it's kinda odd to me that this suddenly happens after 2.8.
Thanks for the feedback, the transform code doesn't use the GPU, so it's strange that an image causes the vertex to be transformed differently.
Ultimately, unless a developer can redo this issue, we may have to close this task.
It would be good if someone on Windows with an ATI Radeon HD 5670 (or similar GPU modal) could test.
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscribers: @fclem, @Jeroen-Bakker, @mont29
Here with current master, debug build + ASAN, just opening that file crashes immediately with following backtrace:
@fclem, @Jeroen-Bakker rings any bell?
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
It is still doing that in current master, however resaving that file from a release build in current master results in not asserting anymore...
Stack trace is quite easy to understand what is happening.
Assigning to myself and increase the priority.