Particle system behaves inconsistently in viewport and render when instance object visibility is disabled #81973

Open
opened 2020-10-22 19:27:55 +02:00 by Trevor Anderson · 9 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Quadro P2200/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20

Blender Version
Broken: version: 2.91.0 Beta, branch: master, commit date: 2020-10-21 22:57, hash: b0f34eee30
Worked: The behavior was different in 2.80

Short description of error
When the instance object of a particle system is disabled in the viewport the particles are also disabled in the viewport. However when the instance object is disabled in render they still appear in the render.

Exact steps for others to reproduce the error

  1. Open the default scene.
  2. Create another object (B).
  3. Create a particle system modifier on the default cube (A).
  4. Set Particle Settings to Hair (A).
  5. Set Render -> Render As to "Object" (A)
  6. Set the Instance Object to the other object (B).
  7. Disable the object (B) in viewport and render
  8. Render the scene, observe that the object has particles rendered
    particle_visibility_bug.blend
**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Quadro [P2200](https://archive.blender.org/developer/P2200.txt)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20 **Blender Version** Broken: version: 2.91.0 Beta, branch: master, commit date: 2020-10-21 22:57, hash: `b0f34eee30` Worked: The behavior was different in 2.80 **Short description of error** When the instance object of a particle system is disabled in the viewport the particles are also disabled in the viewport. However when the instance object is disabled in render they still appear in the render. **Exact steps for others to reproduce the error** 1. Open the default scene. 2. Create another object (B). 3. Create a particle system modifier on the default cube (A). 4. Set Particle Settings to Hair (A). 5. Set Render -> Render As to "Object" (A) 6. Set the Instance Object to the other object (B). 7. Disable the object (B) in viewport and render 8. Render the scene, observe that the object has particles rendered [particle_visibility_bug.blend](https://archive.blender.org/developer/F9036737/particle_visibility_bug.blend)

Added subscriber: @tanderson

Added subscriber: @tanderson

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

Worked: The behavior was different in 2.80

How different?

Here is the same file adapted for blender 2.79.
particle_visibility_bug_279.blend
The behavior appears to be the same.

It is normal for instances to be affected in the same way as the original object. I don't think this is a bug.

> Worked: The behavior was different in 2.80 How different? Here is the same file adapted for blender 2.79. [particle_visibility_bug_279.blend](https://archive.blender.org/developer/F9053705/particle_visibility_bug_279.blend) The behavior appears to be the same. It is normal for instances to be affected in the same way as the original object. I don't think this is a bug.

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'

Oops, I misunderstood the problem.
I can confirm that it is different.
And in fact the behavior in the render and viewport should be consistent.

Oops, I misunderstood the problem. I can confirm that it is different. And in fact the behavior in the render and viewport should be consistent.

Added subscriber: @zeauro

Added subscriber: @zeauro

To be clear, disabling rendering of emitter and original object, instanced as particles, is the most common thing you want to do to render only particles.

Problem in 2.79 was that Viewport was not able to hide the sphere without hiding particles although they were rendered.
Nobody wants to render a unique big instance overlapping all the other tiny instances. Nobody wants a return to that situation.
If you ower

Now, we can disable rendering of the cube and the sphere in viewport and in render without disabling rendering of particles.
For that, we have the local temporary viewport display corresponding to Eye icon.
Use that Eye button instead of the Screen button to hide Sphere and everything will be fine.

Screen button, described as Globally Disabling the objects in all Viewports, is there to check object dependencies through collections and file linking, not to fine tune visibility in Viewport.

Check the file.
particle_visibility_wanted.blend

To be clear, disabling rendering of emitter and original object, instanced as particles, is the most common thing you want to do to render only particles. Problem in 2.79 was that Viewport was not able to hide the sphere without hiding particles although they were rendered. Nobody wants to render a unique big instance overlapping all the other tiny instances. Nobody wants a return to that situation. If you ower Now, we can disable rendering of the cube and the sphere in viewport and in render without disabling rendering of particles. For that, we have the local temporary viewport display corresponding to Eye icon. Use that Eye button instead of the Screen button to hide Sphere and everything will be fine. Screen button, described as Globally Disabling the objects in all Viewports, is there to check object dependencies through collections and file linking, not to fine tune visibility in Viewport. Check the file. [particle_visibility_wanted.blend](https://archive.blender.org/developer/F9111363/particle_visibility_wanted.blend)

That makes a lot of sense to me. So the eyeball and the render toggle are consistent here and the monitor/screen allows you to go further in the viewport but there's no analogous option for renders.

I ran into this when an object was being linked in and used in a particle system but it was then hidden in the source file, so the particles were only showing up in renders. Pretty much the situation you described.

For the previous problem with the visibility couldn't that have been resolved by just putting the original object in a collection and hiding that collection?

Thanks for the response.

That makes a lot of sense to me. So the eyeball and the render toggle are consistent here and the monitor/screen allows you to go further in the viewport but there's no analogous option for renders. I ran into this when an object was being linked in and used in a particle system but it was then hidden in the source file, so the particles were only showing up in renders. Pretty much the situation you described. For the previous problem with the visibility couldn't that have been resolved by just putting the original object in a collection and hiding that collection? Thanks for the response.
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#81973
No description provided.