ParticleInstance: crash with hidden particle system + children #32887

Closed
opened 2012-10-16 06:12:57 +02:00 by xxxxx xxxxx · 5 comments

Relates to: #32058

%%%win7 x64, tested with both official 2.64a and 51350

this is a slight variant of bug #32058

anyway, follow the same steps, but before saving and reloading the file, enable child particles for the particle system, and enable the children option in the particle instance modifier.

boom, crash on reload!

attached is an offending file%%%

**Relates to**: #32058 %%%win7 x64, tested with both official 2.64a and 51350 this is a slight variant of bug #32058 anyway, follow the same steps, but before saving and reloading the file, enable child particles for the particle system, and enable the children option in the particle instance modifier. boom, crash on reload! attached is an offending file%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%Lukas, seems to be just matter of adding check for DM != NULL, but not sure where it'll be the best place for this. Since you've looked into related issue think it'll be much easier for you to look into this issue too?%%%

%%%Lukas, seems to be just matter of adding check for DM != NULL, but not sure where it'll be the best place for this. Since you've looked into related issue think it'll be much easier for you to look into this issue too?%%%
Member

%%%Yes, checking for DM != NULL is simple, but unfortunately the problem is rooted deeper:

Particle Instance modifier depends on a different object with the Particle System modifier, which is handled nicely by the depsgraph. However, disabling the System modifier usually leaves the psys in an invalid state ... This is unlike real modifiers, which simply use the unchanged input DM.

Next to the missing DM pointer (accessed from the cached psmd data) we found at least one other variable that causes trouble (lazy-initialized frand array). Finding all potential invalid variables etc. is almost impossible due to the convoluted code, i would rather not attempt major changes here.

Simple solution: never disable the particle system modifier! I will try to implement a way of preventing "disable" of that modifier. It is an ugly hack to fix a broken design, but guess we all know that by now ...%%%

%%%Yes, checking for DM != NULL is simple, but unfortunately the problem is rooted deeper: Particle Instance modifier depends on a different object with the Particle System modifier, which is handled nicely by the depsgraph. However, disabling the System modifier usually leaves the psys in an invalid state ... This is unlike real modifiers, which simply use the unchanged input DM. Next to the missing DM pointer (accessed from the cached psmd data) we found at least one other variable that causes trouble (lazy-initialized frand array). Finding all potential invalid variables etc. is almost impossible due to the convoluted code, i would rather not attempt major changes here. Simple solution: never disable the particle system modifier! I will try to implement a way of preventing "disable" of that modifier. It is an ugly hack to fix a broken design, but guess we all know that by now ...%%%
Member

%%%Fixed in SVN.

Note that the Particle Instance modifier will now be disabled automatically if the Particle System modifier is disabled. This is the only sane way to ensure it doesn't try to access invalid data. So in this case you need to re-enable the Particle System modifier to make the instancing work!%%%

%%%Fixed in SVN. Note that the Particle Instance modifier will now be disabled automatically if the Particle System modifier is disabled. This is the only sane way to ensure it doesn't try to access invalid data. So in this case you need to re-enable the Particle System modifier to make the instancing work!%%%
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
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
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#32887
No description provided.