search

BadDogSkyrim / PyNifly

Export/Import tools between Blender and the Nif format, using Bodyslide/Outfit Studio's Nifly layer. Supports Skyrim LE, Skyrim SE, Fallout 4, Fallout New Vegas, Fallout 76, and Fallout 3.
GNU General Public License v3.0
177 stars 16 forks source link

Feature Request: Import multiple nifs into separate collections #230

Open GRY4096 opened 3 months ago

GRY4096 commented 3 months ago

Currently multiple nifs imported together all combine together in one tree. I believe it be helpful to have each nif imported be automatically sorted into a separate collection.

Current state: 090724_mR6hD4eMXz

BadDogSkyrim commented 3 months ago

What's the use case? If you're importing all weapon parts together, doesn't it make sense for them to land in one collection? Each part/nif has a single root so you can export them without problem, even if they're in one collection.

Anyone else have opinions?

GRY4096 commented 3 months ago

in this case i am importing multiple weapon parts that occupy the same weapon muzzle attachment slot. so having them all be imported in one collection can be a bit messy. however i do understand having them all be in one collection if for example you are assembling the weapon in blender.

BadDogSkyrim commented 2 months ago

Huh. Okay, I agree the current behavior is a bit odd. Reason is that I'm hooking the weapon part connect points to the parent weapon, so I make them children of the parent connect point and that ends up making the root node of the part a child of the parent weapon, which is weird. Also when you import the weapon and the part, it doesn't necessarily put the weapon at the root of the tree. It's a bit of a mess, really.

As for importing each nif to its own collection, there are advantages to that. I've felt like it would lead to an explosion of collections but maybe it's better to have them cleanly separated. I could also use the filename as the collection name, which would preserve that bit of information.