Particle trails not working #65542

Closed
opened 2019-06-05 21:48:36 +02:00 by Salai Vedha Viradhan · 11 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-05 13:55, hash: 806d4fbc5e
Worked: (optional)

Short description of error
Particle trails are not working in the latest build of Blender 2.8.

If I copy the same object into Blender 2.79, everything is working perfectly.

I think recently the particle system got a patch for better handling of multiple threads and large simulations. May be, some issue with that. @juang3d

I have attached the blend file. particle_trails_not_working.blend (Blender 2.8)

Exact steps for others to reproduce the error
Just add a particle system to the default cube and try increasing the trail count.

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-05 13:55, hash: `806d4fbc5e` Worked: (optional) **Short description of error** Particle trails are not working in the latest build of Blender 2.8. If I copy the same object into Blender 2.79, everything is working perfectly. I think recently the particle system got a patch for better handling of multiple threads and large simulations. May be, some issue with that. @juang3d I have attached the blend file. [particle_trails_not_working.blend](https://archive.blender.org/developer/F7088697/particle_trails_not_working.blend) (Blender 2.8) **Exact steps for others to reproduce the error** Just add a particle system to the default cube and try increasing the trail count.

Added subscriber: @salaivv

Added subscriber: @salaivv

Added subscriber: @juang3d

Added subscriber: @juang3d
Member

Added subscribers: @brecht, @JacquesLucke

Added subscribers: @brecht, @JacquesLucke
Member

Did particle trails ever work in Blender 2.8? It looks like no code actually uses the trail_count variable currently.

Was it removed as part of 51b796ff15?

@brecht, Since the option is doing absolutely nothing right now, we can also remove it?

Did particle trails ever work in Blender 2.8? It looks like no code actually uses the `trail_count` variable currently. Was it removed as part of 51b796ff15? @brecht, Since the option is doing absolutely nothing right now, we can also remove it?

Remove it. It was never supported in Cycles or Eevee, and I would consider adding it there a feature rather than a bugfix.

Remove it. It was never supported in Cycles or Eevee, and I would consider adding it there a feature rather than a bugfix.

@brecht @JacquesLucke

But, the default render mode 'halo' is also not supported by Cycles/EEVEE. Anyway invariably we will have to add an object or collection to render the particles. Does it really have to be removed?

I was basically create a few vegetation assets. So, I was just using the trails as a visual aid. Because, otherwise we will have to bake the particles to actually see their path. I found using trails was more interactive and I could finally bake and convert the paths to editable geometry when I am happy with the simulation.

trails.JPG

002.jpg

Can it stay just as a visual aid?

@brecht @JacquesLucke But, the default render mode 'halo' is also not supported by Cycles/EEVEE. Anyway invariably we will have to add an object or collection to render the particles. Does it really have to be removed? I was basically create a few vegetation assets. So, I was just using the trails as a visual aid. Because, otherwise we will have to bake the particles to actually see their path. I found using trails was more interactive and I could finally bake and convert the paths to editable geometry when I am happy with the simulation. ![trails.JPG](https://archive.blender.org/developer/F7089959/trails.JPG) ![002.jpg](https://archive.blender.org/developer/F7089960/002.jpg) Can it stay just as a visual aid?

There is nothing against adding support for it in the new viewport, but it would not be handled as a bugfix. Until that happens, options that do nothing should be removed.

There is nothing against adding support for it in the new viewport, but it would not be handled as a bugfix. Until that happens, options that do nothing should be removed.
Member

Turns out there are a lot of options that don't seem to do anything anymore. Almost none of the flags in eParticleDrawFlag is used. But all the options are in the UI still.
I suggest for Blender 2.80 we just remove the python part of these options instead of removing the C code.
If necessary, the C code can be cut out later, or we wait with that until we can remove the entire particle code.

Turns out there are a lot of options that don't seem to do anything anymore. Almost none of the flags in `eParticleDrawFlag` is used. But all the options are in the UI still. I suggest for Blender 2.80 we just remove the python part of these options instead of removing the C code. If necessary, the C code can be cut out later, or we wait with that until we can remove the entire particle code.

In #65542#696251, @JacquesLucke wrote:
I suggest for Blender 2.80 we just remove the python part of these options instead of removing the C code.
If necessary, the C code can be cut out later, or we wait with that until we can remove the entire particle code.

Agreed.

> In #65542#696251, @JacquesLucke wrote: > I suggest for Blender 2.80 we just remove the python part of these options instead of removing the C code. > If necessary, the C code can be cut out later, or we wait with that until we can remove the entire particle code. Agreed.
Jacques Lucke self-assigned this 2019-06-06 14:24:59 +02:00
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Member

Particle trails are not supported currently. The settings for it are not in the ui anymore: 87fde57b63

Particle trails are not supported currently. The settings for it are not in the ui anymore: 87fde57b63
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#65542
No description provided.