I nowadays always do a run of the oblivion_optimize.bat. I find it very convenient. Yes it takes a long time to finish the 3 passes, but what is even more annoying is to track down bugs/crashes afterwards when you suddenly discover that this or that mesh is broken/absent etc. My working principles with PyFFI is "safety first" and KISS. I even sacrifice the one mod slot for DLCShiveringIsle.esp... too much potential pain for too little tangible gain, IMHO.

It was when the kit was released, but then Amorilia incorporated the functions the kit was performing into a later version of PyFFI, making it obsolete. Ideally the kit's download entry should get removed to avoid this potential confusion later, but that's up to ulrim.

Just about to give this a whirl again on my meshes (last time was with 2.1.9 and the trail of making sure we had the best of the optimization scripts from H20dk and Arthmoor) ...

Had a good read of this thread (again) and believe the OP is quite out of date.

We now just need ..

Pyffi 2.1.10 (I just grabbed the .2c30444 version of the installer)
Python 2.6.6 (check me out having to install Python again )

and the bat file included with Pyffi now incorporates the most up to date processing of all Oblivion files ?

Edit: NVM, just had a read of what the bat file does, calls all three omptimize ini's in sequence .. Nice Good to go here.

Is there any chance we`re going to see a standalone version that doesn`t require Python?

I think that is what NIFOpt is all about, a C++ version, haven't looked into it much really, and I dont know if the Oblivion Optimization ini's are part of it / work the same way.

I was just thinking because Wrye Bash has a standalone version too and I`m very happy about that.

Hmm, I'm sure I found a version 2.1.11 on the sourceforge site (not at my computer so can't check atm)

Thought it migh be worth mentioning that amorilla seems to have mentioned that any further development is gonna be happening on the python 3 branch (PyFFI 2.2.0) I've been using it for a while now and can say that it does seem to give faster results (and no repeatable crashes using them yet so PyFFI probably hasn;t borked anything yet)

Tip for Psymon - BSAOpt can use either a BSA or a Folder as its source AND destination, and keeps leading spaces

Before packing them up in a BSA use BSAOpt to source your Pyffi Out\ folder, and Destination your Pyffi In\ folder = Overwrites the the In\ files with the Pyffied Out\ files.

I just did a run of two sets of originals yesterday, Oblivion - Meshes and DLCShiveringIsles - meshes, prior to doing that I made two appropriately named empty folders in the Pyffi In\ folder, used BSAOpt to extract the bsa's in to each folder, Pyffied (wait lots) .. BSAOpt to do the copy of Pyffied files over the In\ folder .. And lastly BSAOpt to source the now complete set of files in the In\ folders to a destination new BSA for each of the sets.

Yep seen it and the 2.2.* versions, I decided to go with the latest Amorilia had notified us with here http://www.gamesas.com/topic/1172342-relzwipzpyffi-python-file-format-interface/page__view__findpost__p__18789013
I dont know if thats the latest Stable release, but Arthmoor has recommended it since that post which put the lid on the decision for me

I've been playing around with PyFFI 3K. It's niiiice - I just did the Meshes/Oblivion folder (86.7 MB) in 11 minutes. Some of that might be my new system (I just upgraded), but still - wow. It's also improved over 2.1.10; I tried out some meshes that I'd previously pyffied from Alive Waters - the folder was 4.03 before, and 3.92 after*. It still hogs 100% of your system resources, though... I wish they could fix that.

*Oops. Disregard that - I checked some other stuff, and there was no improvement, size-wise; it looks like I either did those with a really old version, or missed them entirely. Still, PyFFI 2.2 runs great, and it's very fast.

11 minutes? Now that's impressive. 2.1.10 still takes on the order of 2-3 hours for the entire vanilla mesh folder.

You also don't want them to "fix" it using your CPU at 100%. How do you think it got done in 11 minutes?

2.1.11 also gives some speed improvements over 2.1.10--mainly because the Python "garbage collection" step is skipped. (My understanding is that that step is only needed to free up system resources that are no longer needed by Python - it doesn't actually affect the final NIFs). Since Wrye Bash is only compatible with Python 2, I'll be sticking with it and 2.1.11 for the time being...

Python can have multiple installations in a machine. I have Python 3.2.2 for PyFFI and Python 2.7.2 for WB and everything works as intended

I've summarized PyFFI-3k's improvement in speed to around 25% faster than PyFFi's speed. Vanilla meshes took around 3 hours when it used to take 4.5 hrs with PyFFI 2.1.9

Post limit.