Particles: remove Halo, Line and Path render options #108231
No reviewers
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#108231
Loading…
Reference in New Issue
No description provided.
Delete Branch "lichtwerk/blender:80197"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For emitter particle systems, these were never rendered anyways, Path is
kept for hair systems of course.
As a consequence, the new default for particle systems is:
collection)
When changing to Hair type, this automatically gets set back to
Changing back to emitter, will use points as display again (and render
as None -- same here, users have to explicitly set this to object/
collection)
Not sure if this is still for 3.6, patch is for 4.0 for now.
"Fixes" #80197
Let's do this in 4.0 since it's also breaking the Python API.
Note: I reverted this because it broke the
ParticleSystemTest
inphysics_particle_system.py
.Reason was that it is not enough to specify the
'render_type': "OBJECT"
, you now have to additionally specify'display_method': "RENDER"
before applying the particle system.Question: is it "allowed" to tweak the test like this?
Of course this also raises the question in general: Is it OK to have the default viewport display as Point? -- this requires the user to also change
Display As
toRendered
when changing theRender As
from None to e.g.Object
to see the object in the viewport.I would say this is OK, but it is an additional -- though logical -- step.
Just double-checking before committing with the tweaked test...
Hm, good point. It's a bit annoying. I wonder if we could fall back to displaying points when
Display As
is set toRendered
, butRender As
is set toNone
.Hm, it is a possibility, but this could lead to confusion (after all you would be getting something different than the UI advertises). It is trying to be smart where I would think simplicity would be preferred. No super-strong opinion here though.
@brecht : opinions?
The proper solution here would be to have a particle system render as a point cloud by default. But not sure it's worth investing much time in this, if we want to remove the old particle system sooner than later.
Maybe it's better to have the default render method be object, and viewport be rendered. And then if no object is specified, it can still display points in the viewport, as a kind of stand in until the user specifies an object or changes the settings.