Regression: Global Viewport Visibility no longer readable when object is appended from another file #111447

New Issue

ionut · 2023-08-23T21:22:20+02:00

ionut commented

2023-08-23 21:22:20 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-25 23:16, hash: rB32cc9ff03746
Worked: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-26 21:28, hash: rBd046a1f2fa46

Short description of error
Globally disable in viewports Bug. I just upgraded from version 2.9 to version 3.X I downloaded version 3.5.1 and noticed this problem, then I downloaded some other versions of 3.X and noticed the same problem, the same problem as in version 2. X I didn't have it.

When I create an object and then I disable the globally disable viewport option, and then I save the file, when I open another blender file and append to that object, it appears in the scene with globally disable viewport ON even if I saved it with this option to OFF. I know I can disable it, but this is very annoying when I append a rig and have to check that box 100 times on different meshes

Here is a video to understand better : https://youtu.be/AecByo8PYQw
I did that on 3.6.2 and 2.9.1 to see the differences.

Exact steps for others to reproduce the error

Open any 3.X version of blender.
Delete the camera and the sun, keep the cube.
Then disable the globally disable viewport option.
Save the file somewhere. Then close blender.
Open blender again (not the file you just saved) .
Then append the cube you just saved and you will see that it appears with globally disable in viewport ON, even if you saved it with off.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-25 23:16, hash: `rB32cc9ff03746` Worked: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-26 21:28, hash: `rBd046a1f2fa46` **Short description of error** Globally disable in viewports Bug. I just upgraded from version 2.9 to version 3.X I downloaded version 3.5.1 and noticed this problem, then I downloaded some other versions of 3.X and noticed the same problem, the same problem as in version 2. X I didn't have it. When I create an object and then I disable the globally disable viewport option, and then I save the file, when I open another blender file and append to that object, it appears in the scene with globally disable viewport ON even if I saved it with this option to OFF. I know I can disable it, but this is very annoying when I append a rig and have to check that box 100 times on different meshes Here is a video to understand better : https://youtu.be/AecByo8PYQw I did that on 3.6.2 and 2.9.1 to see the differences. **Exact steps for others to reproduce the error** 1. Open any 3.X version of blender. 2. Delete the camera and the sun, keep the cube. 3. Then disable the globally disable viewport option. 4. Save the file somewhere. Then close blender. 5. Open blender again (not the file you just saved) . Then append the cube you just saved and you will see that it appears with globally disable in viewport ON, even if you saved it with off.

ionut added the

labels 2023-08-23 21:22:21 +02:00

Iliya Katushenock changed title from ~~Globally disable in viewports Bug~~ to Regression: Global Viewport Visibility no longer readable when object is appended from another file

2023-08-24 02:04:52 +02:00

Iliya Katushenock added

and removed

labels 2023-08-24 02:05:13 +02:00

Iliya Katushenock commented

2023-08-24 02:08:43 +02:00

Hi @dfelinto , i can't find any notes about this in 3.0 release notes. Documentation is also not very detailed. I think the only clue to this behavior is: high-poly objects that need to be instanced in other files. But I don't see any clear descriptions of this exception. Can you say if this report should be opened?

Hi @dfelinto , i can't find any notes about this in 3.0 release notes. Documentation is also not very detailed. I think the only clue to this behavior is: `high-poly objects that need to be instanced in other files`. But I don't see any clear descriptions of this exception. Can you say if this report should be opened?

Pratik Borhade commented

2023-08-24 07:48:57 +02:00

visibility flags are removed purposefully by @mont29 in d7cf7d4048 https://projects.blender.org/blender/blender/src/branch/main/source/blender/blenkernel/intern/blendfile_link_append.cc#L551

    /* While in general the object should not be manipulated,
     * when the user requests the object to be selected, ensure it's visible and selectable. */

Commit message says "NOTE: This should be a non-behavioral change commit." but behavior has changed. 😅
I'll forward the report to devs before closing.

visibility flags are removed purposefully by @mont29 in d7cf7d4048289d49463a3ef8b9b2172d3c4d44b6 https://projects.blender.org/blender/blender/src/branch/main/source/blender/blenkernel/intern/blendfile_link_append.cc#L551 ``` /* While in general the object should not be manipulated, * when the user requests the object to be selected, ensure it's visible and selectable. */ ``` Commit message says "NOTE: This should be a non-behavioral change commit." but behavior has changed. 😅 I'll forward the report to devs before closing.

Pratik Borhade added

Status

Needs Info from Developers

and removed

Status

Confirmed

labels 2023-08-24 07:49:08 +02:00

Bastien Montagne commented

2023-08-24 10:10:55 +02:00

This code already existed before that refactor, in the instantiation code of readfile.c.

Not entirely sure why it was not 'expressing' itself in 2.9x (likely because append instantiation was already handled elsewhere?), but would rather consider that as a bug, than current behavior, which is expected according to comments.

The rational is that you do not want a selected but hidden object in your scene. Note that disabling the Select option when appending should 'solve' that issue.

This code already existed before that refactor, in the [instantiation code of `readfile.c`](https://projects.blender.org/blender/blender/src/commit/4fe8c62b56d738163902e9f38565a1891abc5a36/source/blender/blenloader/intern/readfile.c#L4512). Not entirely sure why it was not 'expressing' itself in 2.9x (likely because append instantiation was already handled elsewhere?), but would rather consider that as a bug, than current behavior, which is expected according to comments. The rational is that you _do not_ want a selected but hidden object in your scene. Note that disabling the [`Select option`](https://docs.blender.org/manual/en/3.6/files/linked_libraries/link_append.html#id3) when appending should 'solve' that issue.

Bastien Montagne added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Regression: Global Viewport Visibility no longer readable when object is appended from another file #111447