12/19/2023 0 Comments Blender 2.93 asset browser![]() Give users quick access to important transforms and settings for object/collection placement. Why: Current drag & drop with snapping is great, but limited. #90199 (Placement Tool for Objects and/or Collections) Basic indexing is merged but disabled, pending IDProperty support which is in late review stages. blend files, loading time can be quite annoying in production repositories it can take minutes. Why: Asset library loading doesn't scale well currently. #91406 (AssetBrowser: Indexing Asset Library) It's of stratigical importance that this gets dealt with before too long, but it's not really urgent. Who: that there is no big issue with delaying this to 3.2 if needed. Status: Basic design & code architecture support it, but details need to be figured out and actual support be implemented. blend files together with CDFs isn't possible. Why: Single CDFs ask for editing conflicts when asset libraries are shared across multiple users Simple drop-in of asset. #93755 (Support Multiple Catalog Definition Files) ![]() how to handle instancing?) and implementation. Collection support is very important, especially in more professional environments. Why: The lack of collection support is a major limitation of the current Asset Browser. Order roughly reflects importance, so that towards the bottom, items become more nice-to-have targets - that is, in terms of asset project strategy.įor each target there is a rationale explaining why this is something that should or can be addressed for the next release or in short time.īcon1 End Date: 29 December 2021 Bcon2 End Date: 26 January 2022 3.1 Targets ![]() In a way this is a feature-fix release (like C++14 was to C++11 ) ) Use 3.1 (and to some degree 3.2) to further polish the basic Asset Browser experience, before moving to the next big goals.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |