Ah, I use Notepad++ for INI's. I'll switch to Notepad, see if that helps.

Yep. That was the problem. Thanks, Gratis.

For anyone who has run their meshes through both 2.1.7 and either 2.1.8 or 2.1.9b/b2/b3--
Do you see a subtantial difference? I just finished running every single mesh through 2.1.7 and am wondering if it's worth doing so again once the full 2.1.9 is released.

Nope. Not a substantial difference between the different versions.

Thanks. I was guessing not from the changelog - most of the recent updates don't sound like they would affect Oblivion that much.

That said, sometimes updates do make a difference. For example, some of the differences between 2.1.5 and 2.1.6 were huge.

Tell me if I did this right:

I created a INI for cleaning far_nifs. I named it "oblivion_cleanfarnif.ini"

This is what is in the INI:

[main]; run clean far_nif spellspell = CleanFarNif[options]

Is that right?

Nobody has any clue? Who originally wrote the batch script for cleaning far_nifs (even though the one linked in the OP doesn't work)?

If this is the one you are talking about:

"C:\Python26\python.exe" "C:\Python26\Scripts\niftoaster.py" --noninteractive opt_cleanfarnif --dest-dir= --source-dir= --pause --overwrite "%1" > "PyFFILog.txt"

Arthmoor wrote it. How is it exactly not working? I've tested both of his other batch scripts and they execute just fine. The cleanfarnif script isn't much different from those two, you know.

Yes. That's the script I'm talking about.

I input the correct paths for Python and PyFFI, I set a source and destination directory. When I run the script, the command line windows comes up for a second then closes, despite it saying to pause. Also, no nifs are output in the destination directory. And the PyFFI log is empty.

Did you try using the script unmodified? Set the proper directories for Python and the niftoaster, but leave the dest-dir and source-dir entries alone. You don't need to input any extra information into those scripts.

Yes, I did. If I leave it alone it just opens a command prompt window and shows the information in the batch file. No PyFFI information is shown. And the log file remains empty.

No, I'm wrong. It runs fine with it set at the original state. It even pauses. Sorry about that.

As I feared, I did encounter a few objects that fell right through the floor.

The first was an "Amethyst Geode" that was making a ruckus in the archaeology guild main hall as it bounced in and out of the floor before finally doing a Titanic and disappearing into the floor.

The second was a real quest breaker - the quest item itself, a "Metallic Shard" was nowhere to be found inside the first dungeon. An additem and dropping it confirmed that it went right through the floor.

Both meshes were PyFFIed using v2.1.8 Uploaded the files into a sourceforge artifact.

Maybe I'm missing something simple, but I've been lurking on these threads for a while and can't remember if anything like this came up, or where to find an answer.
I previously installed my pyffied meshes (218, using the batch scripts Arthmoor provided) with BAIN and that went fine, but decided to see for myself if repacking them in an uncompressed BSA made any difference. Tested it today with a brand new test character and I CTD on exiting the sewers - the tutorial plays fine. The vanilla BSA has me exiting without problems, so I have to assume the pyffied bsa fouls it up.
The folder structure of the pyffied BSA is sound & I'm pretty sure it has everything that should be in there, the leading space files have their leading spaces, the file date is set to 1/1/2006. Running my test on Win 7-64, with nothing but UOP (with supplement), USIP, FormIDFinder, and a bashed patch.
Does anybody have a clue what I may have overlooked? It's not that I mind re-pyffiing, or re-repacking, but after a few times you kinda want to know if it's going to make a difference before you do

Just a quick heads up that a new test build (2.1.9 beta4) has been published:

https://github.com/amorilia/pyffi/downloads

You don't need this unless you use PyFFI's (still very experimental!) scripts to make & apply patches: the 2.1.9 beta4 has a bugfix in patch_recursive_make/apply scripts for "deep" folder layouts (fixes issue #3193914 reported by xjdhdr).

@malonn: Not sure if I'm understanding your issue completely, but is the problem simply that the log remains empty? If so: this is a known issues with PyFFI 2.1.8 in some configurations. Do you have the same problem with 2.1.9 beta4?

@gratis_monsta: Thanks again! I'll look into these.

@doctasax: Sorry, no clue...

When I right-click a meshes folder and select "Optimize with PyFFI", the command prompt window opens and closes quickly and the meshes don't get optimized. I'm using 2.1.9 Beta 4.

Update for the OP:

-Moved an out of place section of text someplace where it made more sense to place it.

-Link to PyFFI Optimization Kit.

-Link and brief overview of PyFFI Patcher.

-Latest development release 2.1.9b4 recorded.

Problem solved with repyffiing & repacking. Guess I did something stupid that I didn't do this time around...

What problems can cause 64-bit python? Thx.

[img]http://img14.imageshack.us/img14/1364/oblivion201103070932575.jpg[/img]

Any idea went wrong? I am using QTP3. Thanks.

Message printed in console "No handlers could be found for logger pyffi.bla.bla" normal or is the problem x64 python?

EDIT: Hmmm... not. With x32 python too most.

EDIT2: I see only 2 variants of message: pyffi.utils.mathutils and pyffi.nif.nitribasedgeom

EDIT3 xD : Ohhh... i found answer in PiFFY opt Kit topic. But a question about x64 python remained.

Please read the FAQ, Python compatibility is covered there.

I read this. For this reason I have asked which problems can be.

Oh. Whoops, misread your post. :toughninja:

Unfortunately, I can't easily answer that because I don't have a 64bit system, leaving me unable to test this. Someone else will need to share what the problems might be (hopefully Amorilia can enlighten us, since this is his program and he knows it best).

@Zanderat: Did you grab the file name of that mesh? FormID Finder and (I think) RefSkope can do this for you. I say this because I think you should retry the optimization on that mesh, it may have just been a bad optimization. Stuff happens.

Will do. Just checking to see if this was a known issue. Will report back.

http://www.gamesas.com/index.php?/topic/1172342-relzwipzpyffi-python-file-format-interface/