Suggestions & feature wishlist
- Michaleczeq
- Posts: 147
- Joined: 12 Dec 2013 23:02
- Location: Poland, Sanok
- Contact:
Re: Suggestions & feature wishlist
... I completely forgot about this.
Thanks for explain.
Thanks for explain.
Re: Suggestions & feature wishlist
No problem.
-----
Today's update got me thinking: The download size for SCSBT is ~108MB. The size of the addon itself is <5MB (most is the example files). The example files don't change with every release, and even then advanced users may not need/want them. Would it be possible to have an addon-only download option? So there would be BlenderTools-1.6.zip (108MB) and BlenderTools-addon-only-1.6.zip (~5MB) without the data subdirectory.
-----
Today's update got me thinking: The download size for SCSBT is ~108MB. The size of the addon itself is <5MB (most is the example files). The example files don't change with every release, and even then advanced users may not need/want them. Would it be possible to have an addon-only download option? So there would be BlenderTools-1.6.zip (108MB) and BlenderTools-addon-only-1.6.zip (~5MB) without the data subdirectory.
Re: Suggestions & feature wishlist
When importing PIM files from within the base path, could the root object(s)' export filepath be set with the relative path of the imported PIM(s)? Possibly with a toggle in the import settings?
There are two cases where this would be useful:
There are two cases where this would be useful:
- Set base path to extracted base → import desired models for project (relative export paths are set for root objects) → set base path to project base → ...do stuff... → export
- PIM models are in an existing hierarchy → set base path → import ALL the things (relative export paths are set for root objects) → ...do stuff... → export
Re: Suggestions & feature wishlist
Do you have good name for this setting? Please bring it onSmarty wrote:When importing PIM files from within the base path, could the root object(s)' export filepath be set with the relative path of the imported PIM(s)? Possibly with a toggle in the import settings?
Re: Suggestions & feature wishlist
"Inherit Export Path"
"Preserve Export Path"
"Use Source Export Path"
"Path to Destruction"
"Thing #1001 Smarty Asked For"
Ok, I think my morning coffee has kicked in.
"Preserve Export Path"
"Use Source Export Path"
"Path to Destruction"
"Thing #1001 Smarty Asked For"
Ok, I think my morning coffee has kicked in.
Re: Suggestions & feature wishlist
and I've got a winner: "Preserve Path for Export"
- Mohegan13
- Global moderator
- Posts: 19285
- Joined: 05 Jul 2013 09:44
- Location: West Yorkshire; Mars
- Contact:
Re: Suggestions & feature wishlist
I was gonna suggest 'flippity floppity magic things' but i guess I was too late.
[ external image ]
I reserve the right to be 100% wrong.
Something isn't right, nothing feels the same.
Everyone around me Is a different shade of grey.
I reserve the right to be 100% wrong.
Something isn't right, nothing feels the same.
Everyone around me Is a different shade of grey.
- Mohegan13
- Global moderator
- Posts: 19285
- Joined: 05 Jul 2013 09:44
- Location: West Yorkshire; Mars
- Contact:
Re: Suggestions & feature wishlist
Would it be possible to have a secondary import path similar to b2scs?
Basically the main path is as it is right now, the work folder for your mod. The secondary path being the base content. Mods, particularly ones previously made in b2scs, often used SCS files rather than exporting them to a new location. vehicle_reflection being a common one.
Also since it is preferred that mods contain all needed files, it would also make sense to have a tick box option to automatically move these files in the mod on export, possibly with a custom path so the mod files don't overwrite default games ones.
Sure all of this can be done manually, but having options within the tool to do this would cut down on mod time (particularly for first time mods) as well as making it a little more user friendly.
Basically the main path is as it is right now, the work folder for your mod. The secondary path being the base content. Mods, particularly ones previously made in b2scs, often used SCS files rather than exporting them to a new location. vehicle_reflection being a common one.
Also since it is preferred that mods contain all needed files, it would also make sense to have a tick box option to automatically move these files in the mod on export, possibly with a custom path so the mod files don't overwrite default games ones.
Sure all of this can be done manually, but having options within the tool to do this would cut down on mod time (particularly for first time mods) as well as making it a little more user friendly.
[ external image ]
I reserve the right to be 100% wrong.
Something isn't right, nothing feels the same.
Everyone around me Is a different shade of grey.
I reserve the right to be 100% wrong.
Something isn't right, nothing feels the same.
Everyone around me Is a different shade of grey.
Re: Suggestions & feature wishlist
Once again: http://modding.scssoft.com/wiki/File:Mo ... ow_new.png
Now I understand you don't want to create this "base" folder for every mod of yours. Well it's enough if you create link to extracted base
Now I understand you don't want to create this "base" folder for every mod of yours. Well it's enough if you create link to extracted base
Who is online
Users browsing this forum: No registered users and 4 guests