Crash by hiting "tab" after sculpting with dyntopo. #65200
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#65200
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: Win 10
Graphics card: 950m
Working with mouse. Graphics software updated.
Blender Version
Broken:
d525c76003
Worked: (optional)
Short description of error
If you click "tab" after any change of mesh in dyntopo (relative) mode, blender crash (more often if you add detail). However if you manualy change mode in bottom. There is hight chanse to avoid crash.
I have trouble with ctrl-z too, even if blender somehow manage to not crash. He have tendency to broke after some edit of mesh without dyntopo and clicking a few times ctrl-z. Sorry i can't give much more information obout ctrl-z. It generaly starts glitching in my other projects as well over the last .. month ?
Exact steps for others to reproduce the error
Just folow short video.
2.8_human_body_only.blend
VID_20190527_221007.mp4
Added subscriber: @zukson
#65321 was marked as duplicate of this issue
#65356 was marked as duplicate of this issue
#63872 was marked as duplicate of this issue
#63866 was marked as duplicate of this issue
#65150 was marked as duplicate of this issue
Added subscriber: @Gvgeo-1
when dyntopo finish, there is a problem in
build_pbvh_from_regular_mesh
.When it sends
BKE_pbvh_apply_vertCos(pbvh, v_cos, totvert);
if (totvert != pbvh->totvert) {
BLI_assert(!"PBVH: Given deforming vcos number does not natch PBVH vertex number!");```
Added subscribers: @Sergey, @mont29
@zukson Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Videos and/or links to external sites etc. are not acceptable as bug report (they can be provided as additional information only).
This is a complex model, I cannot reproduce it from scratch with a dummy cube it'd seem…
@Gvgeo-1 Please do not assign randomly reports to people, that is not especially my area…
@Sergey issue here is that in
BKE_sculpt_update_mesh_elements()
(which is called when switching dyntopo off just before leaving sculpt mode), the orig mesh of the object is updated from final state of sculpt session, while the evaluated one is still based on mesh before the sculpt session (I think, at least that's what its number of verts suggests).Thing is, I tried to force-update depsgraph (hackish
DEG_on_visible_update()
call insculpt_update_after_dynamic_topology_toggle()
before callingBKE_sculpt_update_mesh_elements()
, but am still getting anme_eval
with wrong (old) number of verts.Assigning to you, at least to get some hits, am feeling a bit lost in that code…
Note that bug can be triggered as well by just trying to disable dyntopo after sculpting a bit, no need to go to Edit mode.
@mont29 Certainly not random, I saw commit
934b9e80
that catches the problem and3e86bb2d
.@mont29, i don't think this is anything to do with depsgraph or evaluation, this is something to do with sculpt mode attempting to do deformed sculpt on a dynamic topology. This isn't going to work: dynamic topology only exists in sculpt mode and is not accessible in modifier stack.
Basically,
BKE_pbvh_apply_vertCos()
is not to be used when dynamic topology is used. Not sure why it's fine when you enable dynamic topology and why is it only becoming a problem later on.P.S. Dynamic topology was never supported for deformed sculpting, you can see this in a simple attached file. Open in 2.79, go to sculpt mode, enable dynamic topology. deformed_dynamic_topology.blend
@mont29, bad news is: got slightly diverged into a wrong direction of investigation. Good news is, now i know what's going on and have some patch to be discussed.
Basically, we indeed need to ensure object is fully evaluated prior to re-creating the PBVH. That puts all the required bits into a nice consistent state.
We can not use
DEG_on_visible_update()
since that only tags for updates, it does not to actual update.The naming is confusing, comes from some legacy history, and is probably be changed.
Here is a patch which works, but which probably required extra pair of eyes and brain to go through:
P985: (An Untitled Masterwork)
P.S. Noticed after submitting the patch. The recalc flag is also to include
ID_RECALC_PSYS_RESET
.BKE_ptcache_object_reset()
might be fine, since the cache is supposed to be shared.@mont29 HI sory but how ?-? this could be posible to describe this in other way (i already reported some bugs when i use video as addisional help) ? I mention CTRL-Z becouse i found that conected with this error. Short video max20 sek with clear view of what i'm doing from opening file to error without any unnessesary steps. Of course i try recreate that with simple cube or ecosphere bit i failed so i have to report with this complicated to analize model. I WILL be better next time with more precise description of the error. Thank you all for your work.
Added subscribers: @megabouda, @JacquesLucke
Added subscribers: @ostapblender, @ZedDB
Added subscriber: @rcuddy
This issue was referenced by
455e14eccd
Changed status from 'Open' to: 'Resolved'
Added subscriber: @AhmedNassef
Added subscribers: @gurralol, @brecht, @DanielBystedt
Hello,
I read that the issue is "resolved". What is process from here, do we wait for a future update release for blender which will include the patch? I just tried and the issue is still happening.
Thanks and regards,
Hard to tell why this the issue is still happening for you since we don't have information about your build hash, platform and things like that.
Current builds which are available on builder.blender.org should have this issue resolved. If the bug is still happening for you, make a new report following the bug report guidelines.
Anyway, usual process is simple:
Indeed, my build was outdated. Downloading the latest build solved the issue.
Thanks !