Blender->Edt->Preferences->Add-ons->Install from file…
Define path and select Marmoset Toolbag 3 executable file
Do not forget to uncheck the relative path option when selecting the Marmoset Toolbag 3 executable file.
How to: Rename OPS:
These operators are using naming rules from Marmoset Toolbag 3 QuickLoader( toolbag-baking-tutorial )
LowPoly/HighPoly buttons (operators) based on the active object name, like for one object and for multiple.
Clean suffixes - Works on selected objects and cleans only names with _low and _high
Baker OPS:
All functions here are based on the active collection at the outliner. Add BakerGroup button:
Should be active object selected with _low suffix
Automatically generates collection with two sub-collections (for high and low poly objects) inside an active collection. Like marmoset toolbag baker and baker groups
Select LowPoly/HighPoly buttons:
Select all objects with corresponding suffixes inside an active collection
Export OPS:
A path for export folder
Export active collection. The name for the FBX file is active collection.
Export selected objects. The name for the FBX file is an active object.
Run Toolbag3
Material OPS:
Select LowPoly object for baker and press create material after baking at the marmoset toolbag. It automatically creates new material and imports all baked textures in it. Still, work in progress.
Marmoset toolbag 3:
Addon automatically creates Baker and Textures folder based on the export path and name for output textures based on the exported filename.
For now, the user has to use QuickLoader manually because there is no API interface for it, but toolbag guys promise to make it accessible in the next version of the marmoset toolbag. So if they realize it loading process will be fully automated.
So after some research, if you link object to group you can’t change a name of it, because it’s a link(instance) and in this case user have to put linked object manually in TB3 baker group, until they implement API functions for quickLoader. But anyway i will add link button. Thanks!
@anphung: could you describe cases when you need a link to baker group?
When modeling, I usually put my lows in collection 1, highs in collection 2. Adding to a BakerGroup currently move them out of those collections & into the BakerGroup collections.
Though after some thoughts, I don’t actually need to use the BakerGroup feature. Just need the proper names.
Very cool, but still I can not understand the logic of work.
The object is not renamed to high suffix, although the status line says that the operation has been completed.
Can you record a quick demo on primitives, otherwise it’s confused in 4 buttons = ((
