Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8 #61130

New Issue

Dirk Wallenstein · 2019-02-02T11:09:58+01:00

Dirk Wallenstein commented

2019-02-02 11:09:58 +01:00

System Information
Operating system: kubuntu 18.10
Graphics card: Nvidia GeForce GTX 750 Ti

Blender Version
Branch: master (git://git.blender.org/blender.git)
Hash: 141c6073ca
Date: 2019-02-02 04:23

Short description of error
in 2.7 there is the option to hide source-layers in the display of instances
(dupli-visibility). I can't find a way to do that in 2.8. The result is that
the proxy and the linked-armature overlap exactly, and selection through the
3D-viewport editor jumps haphazardly between the instance and the proxy (update:
locking modes prevents that).

The most apparent solution for the new collection system would be not having the
armature within the collection that gets instantiated. But in that case the
armature does not show up in the make-proxy prompt as an option. (Therefore,
I cannot make a proxy for it).

Files:

lib.blend bundles the armature within the cubeshape collection (linked

armature is visible)

lib-extarm.blend has the armature outside of the cubeshape collection (cannot

make proxy)

Reproduce:

Start a new blend
Link in: lib.blend -> Collection -> cubeshape
Create a proxy for "Armature"
Toggle the visibility of the instance and/or armature

Ohhhhhhh, I have to lock object-mode. Ok, that solves the selection problem
I guess. Well, I'll post it as it is. Just as a request for clarification.
How do I hide the bones when I'm not animating that instance?

lib.blend

lib-extarm.blend

**System Information** Operating system: kubuntu 18.10 Graphics card: Nvidia GeForce GTX 750 Ti **Blender Version** Branch: master (git://git.blender.org/blender.git) Hash: 141c6073ca39f0d59c67ebef89b094395b903a4a Date: 2019-02-02 04:23 **Short description of error** in 2.7 there is the option to hide source-layers in the display of instances (dupli-visibility). I can't find a way to do that in 2.8. The result is that the proxy and the linked-armature overlap exactly, and selection through the 3D-viewport editor jumps haphazardly between the instance and the proxy (update: locking modes prevents that). The most apparent solution for the new collection system would be not having the armature within the collection that gets instantiated. But in that case the armature does not show up in the make-proxy prompt as an option. (Therefore, I cannot make a proxy for it). Files: - lib.blend bundles the armature within the cubeshape collection (linked ``` armature is visible) ``` - lib-extarm.blend has the armature outside of the cubeshape collection (cannot ``` make proxy) ``` **Reproduce:** 1. Start a new blend 2. Link in: lib.blend -> Collection -> cubeshape 3. Create a proxy for "Armature" 4. Toggle the visibility of the instance and/or armature Ohhhhhhh, I have to lock object-mode. Ok, that solves the selection problem I guess. Well, I'll post it as it is. Just as a request for clarification. How do I hide the bones when I'm not animating that instance? [lib.blend](https://archive.blender.org/developer/F6484168/lib.blend) [lib-extarm.blend](https://archive.blender.org/developer/F6484088/lib-extarm.blend)

Dirk Wallenstein commented

2019-02-02 11:09:58 +01:00

Added subscriber: @d-egg

Dirk Wallenstein commented

2019-02-02 11:16:43 +01:00

Ugh, tried Armature layers once more shortly before posting. Can as well comment on that. Armature layer visibility is linked between library and proxy. And hiding it in the library before saving does not sound like a solution anyway

William Reynish commented

2019-02-02 11:22:53 +01:00

Added subscriber: @WilliamReynish

William Reynish commented

2019-02-02 11:22:53 +01:00

Changed status from 'Open' to: 'Archived'

William Reynish closed this issue

2019-02-02 11:22:53 +01:00

William Reynish self-assigned this 2019-02-02 11:22:53 +01:00

William Reynish commented

2019-02-02 11:22:53 +01:00

If you set disable the Armature viewport visibility in your lib file, it won't be visible in the main file either.

Dirk Wallenstein commented

2019-02-02 11:24:19 +01:00

Ok, this is now the right file

Dirk Wallenstein commented

2019-02-02 11:26:21 +01:00

Ah, didn't think such a coarse measure would be it. Okay, thanks for clarifying.

Dirk Wallenstein commented

2019-02-02 11:53:57 +01:00

To summarize because this wasn't apparent to me and maybe others:

keep "Lock objects mode" on, which you might have turned off during weight

painting

toggle armature-visibility through the proxy (Armature -> Skeleton -> Layers)

Mnja, actually I think it would be nicer to connect the visibility of the proxy
which you can toggle through the outliner with the linked armature. Maybe
Shift-m in pose mode works for me.

To summarize because this wasn't apparent to me and maybe others: - keep "Lock objects mode" on, which you might have turned off during weight ``` painting ``` - toggle armature-visibility through the proxy (Armature -> Skeleton -> Layers) Mnja, actually I think it would be nicer to connect the visibility of the proxy which you can toggle through the outliner with the linked armature. Maybe Shift-m in pose mode works for me.

William Reynish commented

2019-02-02 11:56:25 +01:00

You can just set the entire armature object to be invisible in in the Outliner using the viewport visibility toggle. No need to go to Armature -> Skeleton -> Layers, and no need to do anything with the mode.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8 #61130