Page MenuHome

Datablocks and LibrariesProject
ActivePublic

Members (2)

Watchers

  • This project does not have any watchers.

Details

Description

Tag for Blender tasks related to datablocks, library linking, assets, overrides, and related topics

Recent Activity

Sat, Feb 16

Andrzej Ambroz (jendrzych) added a comment to T61209: Always write unused IDs on save.

@Brecht Van Lommel (brecht) - You ask, You get.

Sat, Feb 16, 7:42 PM · User Interface, Datablocks and Libraries, BF Blender

Wed, Feb 13

Fabio Roldan (fabioroldan) updated subscribers of T61209: Always write unused IDs on save.

I agree with @William Sitton (william) Reynish (billreynish) , a better user experience would be to manage everything from the asset manager.

Wed, Feb 13, 6:59 PM · User Interface, Datablocks and Libraries, BF Blender

Tue, Feb 12

Riccardo Gagliarducci (rickyx) added a comment to T61209: Always write unused IDs on save.

@William Reynish (billreynish) Ton suggested me to read The Humane Interface 12 years ago: super, you got it right away!

Tue, Feb 12, 11:52 PM · User Interface, Datablocks and Libraries, BF Blender
William Reynish (billreynish) added a comment to T61209: Always write unused IDs on save.

Nice Jef Raskin quote.

Tue, Feb 12, 11:02 PM · User Interface, Datablocks and Libraries, BF Blender
Riccardo Gagliarducci (rickyx) added a comment to T61209: Always write unused IDs on save.

"A computer shall not harm your work or, through inaction, allow your work to come to harm".

Tue, Feb 12, 10:58 PM · User Interface, Datablocks and Libraries, BF Blender

Mon, Feb 11

William Reynish (billreynish) added a comment to T61209: Always write unused IDs on save.

Those names would be fine with me too. And yes, I do understand the technical reason for the old name, but you have to have quite an intimate knowledge of the technical details for it to make sense.

Mon, Feb 11, 7:54 PM · User Interface, Datablocks and Libraries, BF Blender
Bastien Montagne (mont29) updated the task description for T61209: Always write unused IDs on save.
Mon, Feb 11, 7:46 PM · User Interface, Datablocks and Libraries, BF Blender
Bastien Montagne (mont29) added a comment to T61209: Always write unused IDs on save.

'Fake User' is actually an excellent example of naming that totally makes sense at the technical level (how it is implemented in code), but is absolute non-sense for any normal user. :) Regarding new name, I would not reference purge here, something as simple as 'always keep', or 'don't auto-delete', or in that area? Anyway, this is a bit detail for now ;)

Mon, Feb 11, 7:46 PM · User Interface, Datablocks and Libraries, BF Blender
William Reynish (billreynish) added a comment to T61209: Always write unused IDs on save.

Likwise, when deleting any ID, also delete its animdata's Action if not used anywhere else.

Mon, Feb 11, 7:32 PM · User Interface, Datablocks and Libraries, BF Blender
Ludvik Koutny (rawalanche) added a comment to T61209: Always write unused IDs on save.

Alright, I will wait and see how it works out in practice :)

Mon, Feb 11, 5:21 PM · User Interface, Datablocks and Libraries, BF Blender
William Reynish (billreynish) added a comment to T61209: Always write unused IDs on save.

Remember we are not talking about auto-purging, but manual purging inside the Outliner or Asset Browser.

Mon, Feb 11, 5:17 PM · User Interface, Datablocks and Libraries, BF Blender
Ludvik Koutny (rawalanche) added a comment to T61209: Always write unused IDs on save.

@Bastien Montagne (mont29) Ok, in that case I don't mind keeping the Fake User then. We could even probably rename it to 'Resist Purge' , 'Don't Purge' or 'Exclude from Purge'. Something like that.

The term 'Fake User' is also just a confusing name - both the term 'fake' and 'user' don't make any intuitive sense in this context at all.

Mon, Feb 11, 5:12 PM · User Interface, Datablocks and Libraries, BF Blender
William Reynish (billreynish) added a comment to T61209: Always write unused IDs on save.

@Bastien Montagne (mont29) Ok, in that case I don't mind keeping the Fake User then. We could even probably rename it to 'Resist Purge' , 'Don't Purge' or 'Exclude from Purge'. Something like that.

Mon, Feb 11, 2:25 PM · User Interface, Datablocks and Libraries, BF Blender

Fri, Feb 8

Bastien Montagne (mont29) updated the task description for T61209: Always write unused IDs on save.
Fri, Feb 8, 11:55 PM · User Interface, Datablocks and Libraries, BF Blender
Bastien Montagne (mont29) added a comment to T61209: Always write unused IDs on save.

@Andrzej Ambroz (jendrzych) think @Brecht Van Lommel (brecht) was more on general UI level: - to remove from lists (aka UI lists, like for vgroups, UVMaps, etc.), X and trashcan would be for IDs (unlink removes the ID usage represented by the IDTemplate UI, but does not remove used ID itself, while trashcan will fully delete that used ID). Also probably for historical reason it's better that way (we have used X to unlink IDs for ages).

Fri, Feb 8, 11:50 PM · User Interface, Datablocks and Libraries, BF Blender
Andrzej Ambroz (jendrzych) added a comment to T61209: Always write unused IDs on save.

The "-" (remove from the list) and "X" (unlink) - let's imagine, that the F-user toggle is demoted to the Outliner and all ID's are kept. What's the difference between both of those functions then? Wouldn't the "unlink" be enough? This part of the UI seems to be counterintuitive from my point of view..

Fri, Feb 8, 11:20 PM · User Interface, Datablocks and Libraries, BF Blender
Brecht Van Lommel (brecht) added a comment to T61209: Always write unused IDs on save.

I think Fake User could be removed, but only if we add options to the Purge operator to specify types of datablocks to delete. Because you still need a way to reclaim memory (at least until deeper design changes happen), but without deleting datablocks like materials.

Fri, Feb 8, 9:52 PM · User Interface, Datablocks and Libraries, BF Blender
William Reynish (billreynish) added a comment to T61209: Always write unused IDs on save.

@Bastien Montagne (mont29) As I understand, you proposal is to only display the Fake User toggle inside the Outliner. If Fake User must be kept, which I'm not sure it does, then I agree that demoting it to the Outliner is nicer. Because then at least the Fake User is not something most users ever have to worry about.

Fri, Feb 8, 8:53 PM · User Interface, Datablocks and Libraries, BF Blender
Bastien Montagne (mont29) added a comment to T61209: Always write unused IDs on save.

Edited task description to add suggestions from @Brecht Van Lommel (brecht), and to reflect work already done on Purge operator.

Fri, Feb 8, 7:00 PM · User Interface, Datablocks and Libraries, BF Blender
Bastien Montagne (mont29) updated the task description for T61209: Always write unused IDs on save.
Fri, Feb 8, 6:58 PM · User Interface, Datablocks and Libraries, BF Blender

Thu, Feb 7

Bastien Montagne (mont29) added a comment to T61209: Always write unused IDs on save.

I’d rather leave the asset thing outside of this discussion, though related, it's still kind of off-topic (and should not be used to do current .blend file management, IDs and assets are not the same things). :)

Thu, Feb 7, 3:10 PM · User Interface, Datablocks and Libraries, BF Blender
Ludvik Koutny (rawalanche) added a comment to T61209: Always write unused IDs on save.

Keep in mind that this needs to be managed on per-case basis, and some common sense needs to be used. Generally, the way this is handled should be aligned with general expectations of users. Let me show you two examples:

Thu, Feb 7, 2:58 PM · User Interface, Datablocks and Libraries, BF Blender
michael knubben (michaelknubben) added a comment to T61209: Always write unused IDs on save.

@William Reynish (billreynish) I definitely agree. Having the current file visible in the asset manager also means there's now an easy overview of all used materials, or all of your meshes, and an easy way to mark them for storage in the Asset Manager itself.

Thu, Feb 7, 11:51 AM · User Interface, Datablocks and Libraries, BF Blender

Wed, Feb 6

Bastien Montagne (mont29) changed Type from Bug to Design on T61209: Always write unused IDs on save.
Wed, Feb 6, 9:50 PM · User Interface, Datablocks and Libraries, BF Blender

Tue, Feb 5

William Reynish (billreynish) added a comment to T61209: Always write unused IDs on save.

Yes, the Orphaned Data in the Outliner is ok, but doesn't give very much information about who is using the data where.

Tue, Feb 5, 7:07 PM · User Interface, Datablocks and Libraries, BF Blender
Brecht Van Lommel (brecht) added a comment to T61209: Always write unused IDs on save.

The outliner already has an "Orphaned Data" view for this. Maybe it should be renamed to "Unused Data", or folded into "Blender File" somehow (which could also use a rename).

Tue, Feb 5, 6:58 PM · User Interface, Datablocks and Libraries, BF Blender
William Reynish (billreynish) added a comment to T61209: Always write unused IDs on save.

Good initiative to take a look at this. Here are my thoughts:

Tue, Feb 5, 6:40 PM · User Interface, Datablocks and Libraries, BF Blender
Brecht Van Lommel (brecht) added a comment to T61209: Always write unused IDs on save.

My main concern here is that we end up in a situation where users have to press Purge often to keep memory usage under control. And then if they learn to do that, they still end up accidentally losing data in the same way as before.

Tue, Feb 5, 5:47 PM · User Interface, Datablocks and Libraries, BF Blender
Bastien Montagne (mont29) triaged T61209: Always write unused IDs on save as Normal priority.
Tue, Feb 5, 3:13 PM · User Interface, Datablocks and Libraries, BF Blender

Sat, Feb 2

William Reynish (billreynish) added a comment to T61130: Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8.

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.

Sat, Feb 2, 11:56 AM · Datablocks and Libraries, BF Blender: 2.8
Dirk (d-egg) added a comment to T61130: Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8.

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)
Sat, Feb 2, 11:54 AM · Datablocks and Libraries, BF Blender: 2.8
Dirk (d-egg) added a comment to T61130: Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8.

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

Sat, Feb 2, 11:26 AM · Datablocks and Libraries, BF Blender: 2.8
Dirk (d-egg) added a comment to T61130: Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8.

Ok, this is now the right file

Sat, Feb 2, 11:24 AM · Datablocks and Libraries, BF Blender: 2.8
William Reynish (billreynish) closed T61130: Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8 as Invalid.

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

Sat, Feb 2, 11:23 AM · Datablocks and Libraries, BF Blender: 2.8
Dirk (d-egg) updated the task description for T61130: Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8.
Sat, Feb 2, 11:19 AM · Datablocks and Libraries, BF Blender: 2.8
Dirk (d-egg) added a comment to T61130: Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8.

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

Sat, Feb 2, 11:16 AM · Datablocks and Libraries, BF Blender: 2.8
Dirk (d-egg) created T61130: Linked-library/proxy: no (apparent) way to hide a linked armature in 2.8.
Sat, Feb 2, 11:10 AM · Datablocks and Libraries, BF Blender: 2.8

Wed, Jan 30

Bastien Montagne (mont29) closed T60957: ASSERT when reloading double-linked file as Resolved by committing rB534573f6b9dc: Fix T60957: ASSERT when reloading double-linked file..
Wed, Jan 30, 11:50 AM · Datablocks and Libraries, BF Blender
Bastien Montagne (mont29) added a comment to T60957: ASSERT when reloading double-linked file.

The assert is sort of harmless here, it simply means that material library is not flagged as 'directly linked' properly, when you duplicate the object (since this is making linked object local, so library used by that one become directly linked). Will check on it, but please do not call this 'a crash', crashing on asserts is not a good idea in Blender, we use them a lot a 'strong warning', not necessarily as deadly error.

Wed, Jan 30, 11:25 AM · Datablocks and Libraries, BF Blender
Philipp Oeser (lichtwerk) renamed T60945: Force field + hair dynamics not working in (linked) instanced collections from Force field + hair dynamics not working with linked library to Force field + hair dynamics not working in (linked) instanced collections.
Wed, Jan 30, 11:22 AM · Datablocks and Libraries, Physics, BF Blender
Philipp Oeser (lichtwerk) added a comment to T60945: Force field + hair dynamics not working in (linked) instanced collections.

@Bastien Montagne (mont29): thx for explanation

Wed, Jan 30, 11:20 AM · Datablocks and Libraries, Physics, BF Blender
Bastien Montagne (mont29) updated subscribers of T60945: Force field + hair dynamics not working in (linked) instanced collections.

@Philipp Oeser (lichtwerk) that assert should for sure never be triggered, but in that case, it is caused by issue with brushes being saved in double or more (from userpref, iirc, @Campbell Barton (campbellbarton) knows the details and fixed the issue some days ago). So in that specific case, it is harmless, just means that the library reading code is only aware of one of the two brushes IDs sharing the same name… Re-saving the library with a recent build will fix that problem.

Wed, Jan 30, 11:13 AM · Datablocks and Libraries, Physics, BF Blender

Tue, Jan 29

Philipp Oeser (lichtwerk) added a project to T60957: ASSERT when reloading double-linked file: Datablocks and Libraries.
Tue, Jan 29, 12:47 PM · Datablocks and Libraries, BF Blender
Philipp Oeser (lichtwerk) raised the priority of T60945: Force field + hair dynamics not working in (linked) instanced collections from Needs Information from User to Confirmed, Medium.

Can confirm now.

Tue, Jan 29, 12:31 PM · Datablocks and Libraries, Physics, BF Blender
Andrew Williams (sobakasu) added a comment to T60963: Hair dynamics: hair dynamics not rendered in animation mode when using a force field.

I tried to simplify the steps to reproduce by adding an instance of the collection in the same file like you suggested. Then blender crashes when I try to render the animation.

Tue, Jan 29, 12:16 PM · Datablocks and Libraries, Physics, BF Blender
Andrew Williams (sobakasu) updated the task description for T60945: Force field + hair dynamics not working in (linked) instanced collections.
Tue, Jan 29, 12:06 PM · Datablocks and Libraries, Physics, BF Blender
Andrew Williams (sobakasu) updated the task description for T60945: Force field + hair dynamics not working in (linked) instanced collections.
Tue, Jan 29, 12:06 PM · Datablocks and Libraries, Physics, BF Blender
Andrew Williams (sobakasu) updated the task description for T60963: Hair dynamics: hair dynamics not rendered in animation mode when using a force field.
Tue, Jan 29, 12:03 PM · Datablocks and Libraries, Physics, BF Blender
Andrew Williams (sobakasu) added a comment to T60963: Hair dynamics: hair dynamics not rendered in animation mode when using a force field.

Yes, sorry I should have mentioned I linked in the collection.
I have not tried changing the link options. I have instance collections turned on.

Tue, Jan 29, 12:02 PM · Datablocks and Libraries, Physics, BF Blender
Philipp Oeser (lichtwerk) added a comment to T60945: Force field + hair dynamics not working in (linked) instanced collections.

Or: are you linking the collection? (with Instance Collection option)
[see related comment in T60963]

Tue, Jan 29, 11:15 AM · Datablocks and Libraries, Physics, BF Blender