Regression: Selection Fails to Highlight in Edit Mode (with restposition and modifier/shapekey displayed in editmode), also crash switching to wireframe or x-ray #109432
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#109432
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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.22621-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 770 Intel 4.5.0 - Build 31.0.101.3959
Blender Version
Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash:
c7fc78b81ecb
Worked: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash:
e1ccd9d4a1d3
Caused by
82ca3d3604
Short description of error
When selecting vertices, edges or faces in either of the attached example files, there is no visible indication of the selection in the 3D viewport.
Exact steps for others to reproduce the error
Selection Bug.blend
Selection Bug.blend
Selection Bug B.blend
Thanks for the report. I can confirm.
broke between
bd86e719ab91 - 993d24c1749c
@lichtwerk , can you check further?
Guess this is related to
82ca3d3604
Selection Fails to Highlight in Edit Modeto Regression: Selection Fails to Highlight in Edit ModeChecking...
Yep, caused by
82ca3d3604
Regression: Selection Fails to Highlight in Edit Modeto Regression: Selection Fails to Highlight in Edit Mode (with restposition and modifier/shapekey displayed in editmode)Thanks :D
@HooglyBoogly ^
This will be fixed in 4.0 by #108637. But I'll try to split out the smallest change that fixes this issue too, so it can be back-ported to 3.6.
Actually, I suggest we just revert that commit in
82ca3d3604
or consider this a known issue in 3.6. "Add rest position" is quite a new feature that is only really helpful for the new hair system anyway. I've been trying to split off some smaller changes from #108637 that might fix this, but haven't found anything yet, that change isn't really safe enough to backport.#109591 the report is also caused by this, but there is also a crash.
Regression: Selection Fails to Highlight in Edit Mode (with restposition and modifier/shapekey displayed in editmode)to Regression: Selection Fails to Highlight in Edit Mode (with restposition and modifier/shapekey displayed in editmode), also crash switching to wireframe or x-rayI am just curious why fix goes to 4.0, but not in LTS? Isn't that it should be more stable than regular?
The fix is a relatively large refactor that might cause other bugs, so unfortunately it's not quite that straightforward.
But this bug creates stable reproducible crash which is in LTS and only in LTS. Shouldn't #107190 be reverted then?
I'm not following the logic here--the new hair system was a major feature in 3.5 and something that a lot of artists have been waiting for for years. The "Add rest position" feature is critical for an animated hair/fur workflow and was included in 3.5, then broken in 3.6. It seems strange to me that we would have an LTS release that breaks an existing feature.
As far as crashes go, I get lots and lots of crashes in general and I chalk them up to Blender being blender when I have lots going on in a scene, but now I'm going to look more closely and see if #109591 has been the root of my most recent issues.
Well, that's definitely one of the crashes I've been hitting lately. I feel frustrated that something that was working fine in 3.5 is broken in 3.6 LTS, which is supposed to be more stable. Users who want a stable, animation-ready hair system will have to wait until the next LTS release. Will the fix be backported from 4.0? I don't know what a "critical fix" is as described on https://www.blender.org/download/lts/
Just to clarify on 3.6 being LTS: the thing broke between 3.5 and 3.6. We dont guarantee 3.6 LTS being more stable than 3.5, what we should guarantee is that 3.6.X is more stable than 3.6.0.
That being said I certainly hope something will get backported, but for that this task is still open with High Priority. And because of this being High Priority, I would urge @HooglyBoogly , @JacquesLucke ( and maybe @brecht ) to make a decision soon if we
82ca3d3604
(meaning rest position would be broken in 3.6LTS)The first two really seem suboptimal to me.