You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2022. It is now read-only.
How feasible would it be to allow a configurable directory that assets are dropped into for exports, and referenced in the 3D models from there? Over the course of time, I have a metric tonne of duplicated files all over the place, which isn't a problem but also not ideal.
Ideal scenario would be something like...
Define an asset directory in config, such as D:\assets
All M2 objects that are exported go into D:\assets\m2 without their WoW directory structures.
All WMO objects that are exported go into D:\assets\wmo without their WoW directory structures, and drop child M2 objects into D:\assets\m2
All textures for M2/WMOs are exported into D:\assets\tex without their WoW directory structures.
For ADT tiles, export into D:\assets\adt under a single directory for the map, such as D:\assets\adt\expansion01\expansion01_43_12_29.png
While losing the organization structure that the exporting currently provides, it would be far more beneficial for the following reasons.
Stops duplicated texture/object files all over the place, which saves a lot of disk space.
Moves texture files away from objects, making the directory with the objects less cluttered.
Easier for sustained import usage to filter one single directory containing all M2 objects, rather than having to navigate the WoW directory tree to find every item, and makes it searchable using the Blender import directory as opposed to having to Windows search and then still manually navigate.
Speeds up exporting if existing files are not overwritten since more re-use?
The text was updated successfully, but these errors were encountered:
Definitely easily doable, would just need to make it a setting as there's a bunch of tools already built around the current way things are. Will mull this over a bit after getting the next version out.
Hey,
How feasible would it be to allow a configurable directory that assets are dropped into for exports, and referenced in the 3D models from there? Over the course of time, I have a metric tonne of duplicated files all over the place, which isn't a problem but also not ideal.
Ideal scenario would be something like...
While losing the organization structure that the exporting currently provides, it would be far more beneficial for the following reasons.
The text was updated successfully, but these errors were encountered: