Scene duplicate particle system bug. #45843

Closed
opened 2015-08-19 07:52:50 +02:00 by Eric Leo · 11 comments

System Information
iMac 2.66 Ghz Intel Core i5
ATI Radon HD 4850 512MB
OS X 10.8.5

Blender Version
2.75a

Short description of error
Particle system will not render in full copy of a scene..

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

create main object (cube), create particle object (sphere).
create particle system, set particle object
render and use

Make a full copy of the scene

render scean duplicate bug.blend

scean duplicate bug.blend

**System Information** iMac 2.66 Ghz Intel Core i5 ATI Radon HD 4850 512MB OS X 10.8.5 **Blender Version** 2.75a **Short description of error** Particle system will not render in full copy of a scene.. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps create main object (cube), create particle object (sphere). create particle system, set particle object render and use Make a full copy of the scene render [scean duplicate bug.blend](https://archive.blender.org/developer/F225237/scean_duplicate_bug.blend) [scean duplicate bug.blend](https://archive.blender.org/developer/F225238/scean_duplicate_bug.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @stargazer

Added subscriber: @stargazer
Author

I also tried the same sample scene on 2.74 and it seemed to do the same thing. i am sure it shouldn't be working like this.

I also tried the same sample scene on 2.74 and it seemed to do the same thing. i am sure it shouldn't be working like this.

Added subscriber: @sindra1961

Added subscriber: @sindra1961

It thinks that setting is wrong.
When scene was copied fully, the setting of particle system is copied.
Sphere object reproduced in new scene exists.
However, original Sphere object is set by the setting of reproduced particle system.
Because there is not original Sphere object in new scene, it is not drawn.

It thinks that setting is wrong. When scene was copied fully, the setting of particle system is copied. Sphere object reproduced in new scene exists. However, original Sphere object is set by the setting of reproduced particle system. Because there is not original Sphere object in new scene, it is not drawn.

Added subscriber: @mont29

Added subscriber: @mont29
Lukas Tönne was assigned by Bastien Montagne 2015-08-20 15:10:38 +02:00

Think BKE_object_relink should call some BKE_particlesystem_relink on all its psys, but this does not seems to exist currently. Lukas, this is your area, will let you decide whether it’s worth spending some time adding relink func to particles, or if we consider that as known limitation/TODO for now.

Think `BKE_object_relink` should call some `BKE_particlesystem_relink` on all its psys, but this does not seems to exist currently. Lukas, this is your area, will let you decide whether it’s worth spending some time adding relink func to particles, or if we consider that as known limitation/TODO for now.
Lukas Tönne removed their assignment 2015-08-20 15:37:01 +02:00
Member

Added subscriber: @LukasTonne

Added subscriber: @LukasTonne
Member

Sorry, i'm done with particles.

Sorry, i'm done with particles.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2015-08-20 16:53:20 +02:00

sigh Starting investigating this, but particles are not my area, and it looks like their copying is rather primitive (e.g. psettings ID are never actually duplicated it seems when copying an object’s particle system, etc.). Addressing this is way out of scope of a bug, so will close this as TODO for now (added note ot our TODO list). Thanks for the report.

*sigh* Starting investigating this, but particles are not my area, and it looks like their copying is rather primitive (e.g. psettings ID are never actually duplicated it seems when copying an object’s particle system, etc.). Addressing this is way out of scope of a bug, so will close this as TODO for now (added note ot our [TODO list](http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Particles)). Thanks for the report.
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
4 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#45843
No description provided.