» Wed Mar 30, 2011 9:28 am @andalaybay
The advantage of this kit is
Lets see if I can understand your point of view:
When applying PyFFI over meshes I'm selecting individually, I don't really need the skip list unless I'm not sure if they should be skipped at all. Provided the mesh has a sensible name of its type to compare to the list - i.e. helmet.nif - it may not be worth optimizing but checked for some particular operation - like fix_texturepath or similar. PyFFI is getting better each version - hopefuly to allow me to stop worrying about such cases. Nevertheless I see the usefulness of a customized optimization here.
When applying PyFFI on a folder with a complex structure, what you'd like to do is to let the meshes be skipped appropriately on the spot. For this, the only difference being the place where the folders are, I can try to make a custom right-mouse button command.
However, there may be a time when you want to do some specific optimization and the standard PyFFI command is still preferred.
Don't forget about testing and how the PyFFI project can progress to help us mortal mod users let go of all this care. :foodndrink:
The advantage of this kit is
- to be able to apply PyFFI in a large set of files or complex directory structure,
with the safety of the skip list,
not bypassing meshes that could be optimized,
not bypassing meshes that could be checked for other PyFFI fixes,
and applying several optimization passes at once(case of _far.nif).
Lets see if I can understand your point of view:
When applying PyFFI over meshes I'm selecting individually, I don't really need the skip list unless I'm not sure if they should be skipped at all. Provided the mesh has a sensible name of its type to compare to the list - i.e. helmet.nif - it may not be worth optimizing but checked for some particular operation - like fix_texturepath or similar. PyFFI is getting better each version - hopefuly to allow me to stop worrying about such cases. Nevertheless I see the usefulness of a customized optimization here.
When applying PyFFI on a folder with a complex structure, what you'd like to do is to let the meshes be skipped appropriately on the spot. For this, the only difference being the place where the folders are, I can try to make a custom right-mouse button command.
However, there may be a time when you want to do some specific optimization and the standard PyFFI command is still preferred.
Don't forget about testing and how the PyFFI project can progress to help us mortal mod users let go of all this care. :foodndrink:
Actually in my case, the issue is that I don't have the first clue as to what PyFFI does, I just know that it's something I should do
So I run the process on all my meshes when I release a new version of my mod. But often I just create a new mesh and want to optimize that specifically as I add it to my mod. So being able to right-click and select optimize is easier than copying to the in folder. Are you saying that I shouldn't be using your four-pass optimization against a single file? From my point of view, I would just switch to using your scripts for all my optimizations. I don't want to worry about the details. I'm not a modeller, so I don't really understand all the details of NIF's. I'm pretty good at collision and physics, so I understand those parts of a NIF, but telling me that I should remove unused verticals or something like that is meaningless 
I would say that if something is unused, it should be removed, but I wouldn't be in a position to judge the impact of doing that - other than if seeing the results in game. 
Not sure if it helps any, but most of my work has been to take vanilla meshes, rescale them and convert the collision from static to havoked. Or to create a new static collision mesh for the smaller version of the object. So I want to optimize those meshes because by the time I'm done with them, they probably need a good cleaning
