Motion in zero-velocity particle system #38563

Closed
opened 2014-02-09 21:03:22 +01:00 by Ignatz · 6 comments

Windows 7 Professional 64-bit w Service Pack 1
Nvidia GeForce GTX 760

Blender 2.69 - r60995

There appears to be an instability in the generation of particles. It can be seen in the attached .blend file.

In this file I arranged the particle system so that a moving object would generate a trail of particles. Each single particle has zero velocity, thus the stream should be completely stationary.

If the file is loaded and played only one time through there is nothing strange to be seen. On the second and all subsequent times through the animation, there is unexpected movement that can be seen in some of the particles. The particles first appear in a position somewhat 'behind' where they should be and then slide into place over the next frame or two. This visible and unexpected motion also ends up in the rendered animation. If the file is reloaded, the animation will be displayed (again) correct the first time through and then incorrect every time thereafter.

This may (?) have something to do with the algorithm of the subframes system. I say that because as one increases the particles settings subframes the amount and visibility of the unexpected particle motion also increases.

A second effect I have noticed is that the trail of particle objects that are being left behind the emitter are not immediately 'solid' when they appear. It is almost as if they have a one frame 'fade-up' into existence so that instead of being the assigned yellow color at the instant of the creation they are first gray in color and only one frame later do they attain their full yellow color. I do not know if this 'fade-up' behavior is supposed to be normal or not (or is some sort of trick of the eye) and so have not listed it in a separate bug report.

particle_emitter_bug.blend

Windows 7 Professional 64-bit w Service Pack 1 Nvidia GeForce GTX 760 Blender 2.69 - r60995 There appears to be an instability in the generation of particles. It can be seen in the attached .blend file. In this file I arranged the particle system so that a moving object would generate a trail of particles. Each single particle has zero velocity, thus the stream should be completely stationary. If the file is loaded and played only one time through there is nothing strange to be seen. On the second and all subsequent times through the animation, there is unexpected movement that can be seen in some of the particles. The particles first appear in a position somewhat 'behind' where they should be and then slide into place over the next frame or two. This visible and unexpected motion also ends up in the rendered animation. If the file is reloaded, the animation will be displayed (again) correct the first time through and then incorrect every time thereafter. This may (?) have something to do with the algorithm of the subframes system. I say that because as one increases the particles settings subframes the amount and visibility of the unexpected particle motion also increases. A second effect I have noticed is that the trail of particle objects that are being left behind the emitter are not immediately 'solid' when they appear. It is almost as if they have a one frame 'fade-up' into existence so that instead of being the assigned yellow color at the instant of the creation they are first gray in color and only one frame later do they attain their full yellow color. I do not know if this 'fade-up' behavior is supposed to be normal or not (or is some sort of trick of the eye) and so have not listed it in a separate bug report. [particle_emitter_bug.blend](https://archive.blender.org/developer/F76601/particle_emitter_bug.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @ignatz

Added subscriber: @ignatz
Member

Added subscriber: @LukasTonne

Added subscriber: @LukasTonne
Member

Looks like this is an artifact caused by the cache step feature. By default this only forces cache frame storage every 10 frames, which for some reason leads to interpolation errors in this case. Possibly the algorithm for detecting motion thresholds (which supposedly increases steps where needed) fails if the particle doesn't move at all ...

Simple solution is to lower the cache frame step to 1, which will store an accurate cache sample in every frame. Just note that it may increase the cache size drastically (only an issue for much larger particle numbers than in this file).

particle_emitter_bug.png

Looks like this is an artifact caused by the cache step feature. By default this only forces cache frame storage every 10 frames, which for some reason leads to interpolation errors in this case. Possibly the algorithm for detecting motion thresholds (which supposedly increases steps where needed) fails if the particle doesn't move at all ... Simple solution is to lower the cache frame step to 1, which will store an accurate cache sample in every frame. Just note that it may increase the cache size drastically (only an issue for much larger particle numbers than in this file). ![particle_emitter_bug.png](https://archive.blender.org/developer/F77253/particle_emitter_bug.png)

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2014-02-17 09:45:17 +01:00

Cache step of 10 frames works in simple cases but fails in more tricky setup. Don't think it's a bug, just a specific of current implementation. Added to the TODO list http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Particles so we could check on this later when improving the system.

Thanks for the report anyway!

Cache step of 10 frames works in simple cases but fails in more tricky setup. Don't think it's a bug, just a specific of current implementation. Added to the TODO list http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Particles so we could check on this later when improving the system. Thanks for the report anyway!
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#38563
No description provided.