Visibility differences when hiding from layer and object level properties #97524

New Issue

ManBlender · 2022-04-21T21:48:39+02:00

ManBlender commented

2022-04-21 21:48:39 +02:00

System Information
Operating system: Windows-10-10.0.18363-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-16 23:26, hash: 34d424fd64
Worked: (newest version of Blender that worked as expected)

Short description of error
Hiding collection/object from outliner with layer level property (eye icon) and object level property (screen icon) in nested releation
gives inconsistent results

Steps to Reproduce

Open attached file
Hide Collection A2 with eye icon
Now hide Collection A2 with screen icon

Refer video: https://recordit.co/r6yA5iDHdn
collections_bugs.blend

Original Report

Short Description
There are 2 cases where:

Watching viewport in rendering mode give different view in view-port and final render image or video

a ) it's happening due some not refreshed states from outliner on hide/show object and disable/enabled in render on vieport

b) it's especially observed problem around:

collections
moved collection to other
parent object from other collections

Watching viewport and animation
a) user operating object and all looks ok, then ruining animation and blender doing broken whole objects, relations and movements

Exact steps for others to reproduce the error
I can't save file that showing this, coz is unpredictable case for me when:

Refresh states not working automatically from outliner in some cases, save/open file again solving problem.

also suggestion is to hide all child objects in parent when parent status is changed to hide to not child one per one, or give to hide just this object (eg. contex menu by RMB)
this management can solve problems around operation as in point 1,b) issye

When refresh states not working on timeline and when just animation refreshing coordination **not when objects are moved,**etc. (just play changing eg. x,y,z on this same frame in case operations as move, scale, rotate not doing this - so backing to main frame when was operation, update etc. not giving effect, just play)

for both solution is suggestion to give option for viewport rendering as this same like final render, regarding the states and depth levels of parents/child/collections

Maybe is know issue, maybe some on meet this and can explain better than me, or some part of code can be checked to see relations for this type issues.

**System Information** Operating system: Windows-10-10.0.18363-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-16 23:26, hash: `34d424fd64` Worked: (newest version of Blender that worked as expected) **Short description of error** Hiding collection/object from outliner with layer level property (eye icon) and object level property (screen icon) in nested releation gives inconsistent results **Steps to Reproduce** - Open attached file - Hide `Collection A2` with eye icon - Now hide `Collection A2` with screen icon Refer video: https://recordit.co/r6yA5iDHdn [collections_bugs.blend](https://projects.blender.org/attachments/cc62fb16-1d23-4831-9e26-ec258c260dbc) <details> <summary> Original Report </summary> **Short Description** There are 2 cases where: 1. Watching viewport in rendering mode give different view in view-port and final render image or video a ) it's happening due some **not refreshed states from outliner on hide/show object and disable/enabled in render on `vieport`** b) it's especially observed problem around: - collections - moved collection to other - parent object from other collections 2. Watching viewport and animation a) user operating object and all looks ok, then ruining animation and blender doing broken whole objects, relations and movements **Exact steps for others to reproduce the error** I can't save file that showing this, coz is unpredictable case for me when: 1. Refresh states not working automatically from outliner in some cases, save/open file again solving problem. - also suggestion is to hide all child objects in parent when parent status is changed to hide to not child one per one, or give to hide just this object (eg. contex menu by RMB) - this management can solve problems around operation as in point 1,b) issye 2. When refresh states not working on timeline and when just animation refreshing coordination **not when objects are moved,**etc. (just play changing eg. x,y,z on this same frame in case operations as move, scale, rotate not doing this - so backing to main frame when was operation, update etc. not giving effect, just play) - for both solution is suggestion to **give option for viewport rendering** as this same like final render, regarding the states and depth levels of parents/child/collections Maybe is know issue, maybe some on meet this and can explain better than me, or some part of code can be checked to see relations for this type issues. </details>

ManBlender commented

2022-04-21 21:48:39 +02:00

Added subscriber: @ManBlender

Satish Goda commented

2022-04-21 21:55:47 +02:00

Added subscriber: @satishgoda1

Evan Wilson commented

2022-04-21 22:24:17 +02:00

Added subscriber: @EAW

Evan Wilson commented

2022-04-21 22:24:17 +02:00

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

Evan Wilson commented

2022-04-21 22:24:17 +02:00

You are using an alpha build that is 3 months old.

Please try the latest daily build: https://builder.blender.org/download/

You are using an alpha build that is 3 months old. Please try the latest daily build: https://builder.blender.org/download/

ManBlender commented

2022-04-22 12:20:21 +02:00

I also using:
Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: c77597cd0e
Worked: (newest version of Blender that worked as expected)

And meet this in older versions as 3.0. Rarely but sometimes biting me this around job.

I also using: **Blender Version** Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `c77597cd0e` Worked: (newest version of Blender that worked as expected) And meet this in older versions as 3.0. Rarely but sometimes biting me this around job.

ManBlender commented

2022-05-14 22:26:42 +02:00

https://blender.community/c/rightclickselect/4zxJ/ Other confirmation of this cases

Thomas Dinges commented

2022-12-15 16:57:58 +01:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2022-12-15 16:57:58 +01:00

Is this still happening in Blender 3.4 for you?

ManBlender commented

2022-12-15 20:16:34 +01:00

Not using yet 3.4 but on 3.3.1 yes. I will move to 3.4 now and I will see in next weeks in practice.

Thomas Dinges commented

2023-01-20 16:27:42 +01:00

We need a way to reproduce the issue with clear instructions and an example blend file. Please try to simplify this report with clear steps for us for investigation.

ManBlender commented

2023-01-20 17:11:31 +01:00

Still observing this problem around blender-3.5.0-alpha.
It's refresh problem with object around outliner and viewport, where watching viewport thinkig that I will be render what seeing, in fact when rendering, it's different coz something is refreshed but not on viewport, eg. movements around collection. The problem is coz restart blender give us new view as refreshed. Ofthe is problem around animation when restart moving all in to right positions regarding origins.
Soo.. I think that viewport need some case as "refresh" maybe as rendering have. It's not composition problem, etc. just pure render and especially around animation.

Still observing this problem around blender-3.5.0-alpha. It's refresh problem with object around outliner and viewport, where watching viewport thinkig that I will be render what seeing, in fact when rendering, it's different coz something is refreshed but not on viewport, eg. movements around collection. The problem is coz restart blender give us new view as refreshed. Ofthe is problem around animation when restart moving all in to right positions regarding origins. Soo.. I think that viewport need some case as "refresh" maybe as rendering have. It's not composition problem, etc. just pure render and especially around animation.

Pratik Borhade commented

2023-07-20 08:49:42 +02:00

Hi, thanks for the report (and sorry for the less attention)
I went through the rightclickselect post and above description, it seems the report is about visibility status of the object/collection instances.
Is it possible to share .blend file (so we'll have same reference)?

Hi, thanks for the report (and sorry for the less attention) I went through the rightclickselect post and above description, it seems the report is about visibility status of the object/collection instances. Is it possible to share .blend file (so we'll have same reference)?

ManBlender commented

2023-07-20 22:41:13 +02:00

Not have file, but can confirm that problem still exist with 3.5, 36
I recognized that problem exist more often with:

collection is huge,
collection was added to solve problem with origin relation (changes when moving some object)
when adding, changing something in collection
THEN.. THE CHANGES ARE NOT APPLIED IN COLLECTION, BUT REFRESHING BUTTONS FOR THE COLLECTION (viewport*, render) THAT AGGREGATING OTHER FIXING PROBLEM, so it's around states.

soo.. this is on case, when is multiplied situation (changes in many collection, that other collections have not refreshed states for instance giving problems), then hard to discover what is wrong, and especially if many scenes and linked

to precise problem on viewport shading on solid can be discovered this problem, not only final rending, but more complicated problem of course when post-processing on image via node

Not have file, but can confirm that problem still exist with 3.5, 36 I recognized that problem exist more often with: 1. collection is huge, 2. collection was added to solve problem with origin relation (changes when moving some object) 3. when adding, changing something in collection 4. THEN.. THE CHANGES ARE NOT APPLIED IN COLLECTION, BUT REFRESHING BUTTONS FOR THE COLLECTION (viewport*, render) THAT AGGREGATING OTHER FIXING PROBLEM, so it's around states. - soo.. this is on case, when is multiplied situation (changes in many collection, that other collections have not refreshed states for instance giving problems), then hard to discover what is wrong, and especially if many scenes and linked * to precise problem on viewport shading on solid can be discovered this problem, not only final rending, but more complicated problem of course when post-processing on image via node

ManBlender commented

2023-08-31 23:22:25 +02:00

I found new simple issue that can help solve problem I think.
https://recordit.co/r6yA5iDHdn
In this case looks multiplication of collection have some unpredictable inheritance behavior or not well documented this around this type operation how presenting.

I found new simple issue that can help solve problem I think. https://recordit.co/r6yA5iDHdn In this case looks multiplication of collection have some unpredictable inheritance behavior or not well documented this around this type operation how presenting.

collections_bugs.blend

856 KiB

ManBlender commented

2023-08-31 23:33:20 +02:00

Soo.. that finally can explain more around addons and scripts that grouping objects.. coz if this is bug, then normally that this type inheritance is repeated in root of collections. Then if woorking with big project, and using some of scripts and automation doing some of this operation like upper in video.. then can't manage correctly collections in big depth, especially if completed collections are shifted to other, etc. etc..

I hope that this can be solved, coz it's really hard do many job to control a "level" or "priority" around.
Other way is to made a "node" of objects and collections included to see the hierarchy around to fix some levels.
If I thinking how to find this type problem step by step in some of my project, then pass.. when soo many collections and very similar and build from other.

Soo.. that finally can explain more around addons and scripts that grouping objects.. coz if this is bug, then normally that this type inheritance is repeated in root of collections. Then if woorking with big project, and using some of scripts and automation doing some of this operation like upper in video.. then can't manage correctly collections in big depth, especially if completed collections are shifted to other, etc. etc.. I hope that this can be solved, coz it's really hard do many job to control a "level" or "priority" around. Other way is to made a "node" of objects and collections included to see the hierarchy around to fix some levels. If I thinking how to find this type problem step by step in some of my project, then pass.. when soo many collections and very similar and build from other.

ManBlender commented

2023-08-31 23:37:59 +02:00

One case I not repated here, the refresh case.. - the situation when collection is moved outside and should refresh other collection as disabled. Here in example and some test always working, in my experience only move not doing resfresh for states collections in other. Also in relation to keyframes or drive it's still hard recognize whats going here on the line of states inheritance roots. collections

Pratik Borhade added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-09-01 12:41:44 +02:00

ManBlender commented

2023-09-12 12:57:16 +02:00

@PratikPB2123 @ThomasDinges can You watch movie and confirm problem? Coz after time this can be deleted and issue is also complicated.

Pratik Borhade commented

2023-09-12 13:47:43 +02:00

@ManBlender hi, from video file, it seems different objects are hidden when clicked on eye icon and screen icon.
Did I understand the bug correctly which you've shown in the video? I can confirm in that case, I'll investigate this further.

@ManBlender hi, from video file, it seems different objects are hidden when clicked on `eye` icon and `screen` icon. Did I understand the bug correctly which you've shown in the video? I can confirm in that case, I'll investigate this further.

ManBlender commented

2023-09-12 21:29:37 +02:00

Right. From 20sec You can see the main issue as change around inheritance outside root collection that only applying hide to render. This can be big step to fix this bug.

Pratik Borhade changed title from ~~Differences betwen rendered view in viewport and render image and video~~ to Visibility differences when hiding from layer and object level properties

2023-09-14 10:55:06 +02:00

Pratik Borhade added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Visibility differences when hiding from layer and object level properties #97524