And I don't know why. I've had no trouble PyFFIing meshes, but when I downloaded some "nif.patch" packages and the scripts to make it happen, ApplyPatches.bat just spits out an error for every file it comes across. So I ran CheckOriginal-Patches.bat, and its "twin", and yep, they also come up with a whole lot o' nothin'.

I've checked the meshes and the patches - they are exactly the same, except one lot has ".patch" tacked on (as it should be.) The paths are identical, the folders were put in the right places (Original and Patches, that is.)

Is there something I'm not doing, doing wrong, or simply not realising? I have checked the documentation, such as it is. But perhaps I missed a vital detail or two...

Let me guess, Vista (or Windows 7)? If so then I'd like to join your question.

Yes: W7 x64... Hm, so it could be something to do with UAC? Might try a few workarounds for that then, I suppose.

"System cannot find the path specified" is the error, by the way (or something like that - it flies by so fast...) - and in the Optimized folder, it's a mess. No actual patched meshes, just lots of recursive and jumbled directories, basically.

Okay, this goes from funny to hilarious... if you're in the right mood. : \

So I tried switching off UAC, which did nothing. OK, then I tried telling Windows that the application (that being "xdelta") should be "Run as Administrator" (in the app's actual settings.) That seemed to work... except for the fact that for every single file, it would ask me to OK it. Gah - never setting things up like that again (well, for batches, anyway) ! Last of all, I tried both of the above. Seemed to work, and without the annoying pause+nag every second or so...

But I checked the Optimized folder after it had apparently done what it was supposed to do - same mess as before, still with no files whatsoever.

:brokencomputer: Or yeah, it probably isn't the computer's fault, but still, it seemed like the appropriate emoticon.

edit: No, it's not in a "protected area" like Program Files (x86) or the like. Yes, Oblivion (with LAA, obse and the lot) runs just fine on this machine.

edit2: Oh, wonderful - I checked the homepage (and google code page) for xdelta, and the windows executables there are labelled "windows XP"... this does not bode well. Or, more to the point, wouldn't have boded well if I'd seen it before trying. Anyway, armed with this info, I specified that xdelta (I even downloaded the slightly more recent version, and tried this with both) should run in "Windows XP SP3 compatibility mode". No luck, surprise, surprise. Exactly the same as before.

yeah the patching scripts you mention don't work in Vista or 7. svcks doesn't it.

It has something to do with the commands used in the bat script, somehow Vista/Win7 reads it differently than WinXP.

The scripts were made with an older version of PyFFI, so it makes more sense to PyFFI whatever you are trying to patch yourself.

As Tomglong said, the patches where created after comparing files after running an old version of pyffi. You will not get the benefit of the improvement made to the pyffi algorithm, so even the difference patch will still have junk data in the mesh.

Personally I'm waiting to pyffi my fresh fcom install when the next version comes out with collision mesh optimizing. Interested to see how this will affect performance, since collision meshes need to be very simple objects to reduce processing of the collision engine (basically finding the boundary volume where object cannot pass through each other (processor intensive).

Fortunately for you (unlike me, who already PyFFI-optimized my FCOM files) the new BSAs are already optimized.

Oh, good to hear!

I've already optmised a number of things too, but this is both my first attempt at an *all* (well, nearly all) BAIN installation of FCOM++*, and my first close contact with PyFFI. It's still going remarkably well, all things considered, but I am also constantly changing the mod list (and therefore Bashed Patch, and character too.) So, any new version of, well, anything I have (or don't have, even) shouldn't be a problem to install "over the top of" my current setup. Basically, anyway. This is (one of the areas) where I have found BAIN to be a godsend. The ability to easily and cleanly change whatever you want to change is just short of magical. :celebration:


* Actually, I'd never used BAIN before a few days ago, or so.

Welcome to the other side!