Regression: Global Viewport Visibility no longer readable when object is appended from another file #111447
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
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-25 23:16, hash:
Worked: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-26 21:28, hash:
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.
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?
visibility flags are removed purposefully by @mont29 in
/* 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.
This code already existed before that refactor, in the instantiation code of
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.
When selecting multiple options I don't think the selection option should "override" the object "selectability" and "visibility".
When appending individual objects (specially if we do it via the asset shelf/asset browser) I think it is reasonable to force them to be visible and selectable.
Short of making different rules (for assets and regular append) I think we could just archive this. I wouldn't oppose to different behaviours though (as long as assets can be appended via asset shelf/browser as they do now).
No due date set.
No dependencies set.
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?