Page MenuHome

Particle System as flow source doesn't work
Confirmed, NormalPublicBUG

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013

Blender Version
Broken: version: 2.90 (sub 1), branch: master, commit date: 2020-05-14 02:19, hash: rB1fadda344ca5
Worked: blender-2.83-c26f470cfeea-windows64

Short description of error
Particle System as flow source doesn't work. Smoke is always emitted from mesh.

If file is opened in version that worked, smoke starts flowing from particles correctly. File doesn't have to be even re-saved in working version.

Because example file is reproducible only once, here are
Steps to create example file

  1. New General template
  2. Add UV Sphere
  3. Add particles to cube
  4. Particle Properties > Emission > Number = 50
  5. Particle Properties > Render > Render As = Object
  6. Particle Properties > Render > Instance Object = Sphere
  7. Particle Properties > Render > Scale = .6
  8. F3 > Quick Smoke
  9. Select Cube again
  10. Physics Properties > Flow Source > Flow Source = Particle System (doesn't invalidate cache)
  11. Physics Properties > Flow Source > Particle System = ParticleSettings (doesn't invalidate cache)

Exact steps for others to reproduce the error

  1. Open file
  2. Play animation

Event Timeline

I managed to reproduce the problem the first time.
But after I updated some property, it recalculated and I can not repro again:

I managed to reproduce the problem the first time.
But after I updated some property, it recalculated and I can not repro again:

It should work right away in any case.
To reproduce again you need to create new file. I guess that with new file, cache must be incorrectly initialized somehow. I add how to create example file to report description .

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.Tue, May 19, 3:05 PM
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".

I can confirm that in steps 10. and 11. the cache is not invalidated.
I cannot confirm, in step 8, that the path does not exist. In my case it exists.

I can confirm that in steps 10. and 11. the cache is not invalidated.
I cannot confirm, in step 8, that the path does not exist. In my case it exists.

Re-tried and can't reproduce as well... In any case that would be not related to this bug if the cache was actually invalidated, so I will remove that.