A Land Far Away

From what I can tell, looks like patch 1.10 is more or less the same as patch 1.07 beta- quite a few people seem to be having trouble with it. I think most of the bug fixes for the 1.07b issues have been pushed back to 1.11, to be addressed after the MotB expansion is in place.

On the other hand, transitioning to 1.10 may help us prepare for MotB- so I'd like our builders to weigh in on the state of their essential plugins (again), so we can manage the switch without leaving anyone out to dry.

I'm fine to update asap. Sinplugin, Powerbar and Replug will be out soon...always within a week of the new patch, and any preparation time we can get for MotB is worth taking.

Guess I'll take the 2das and tlkedit2 with me when I head out of town this weekend to poke at while others are on Halo3 rampages.

We'll shoot for a shorter lag cycle before update this time around.

As per the discussion here:

http://www.alandfaraway.org/phpbbforum/ ... 044#444044

Sounds like we're leaning towards an immediate/soon patch for 1.10, and a delayed (oct 10th or 11th?) upgrade to MotB.

Does that sound reasonable?

AL, that's the message I'm getting when opening my module directory in 1.10. I've tried it on 2 computers with the same result.

It doesn't seem to be affecting anything except this script: acr_vfx_i, which is now not compiling. But stability seems the same and the areas I've tried opening seem ok.

So I'd love to work out what's causing the error. Any ideas?

Running on that vfx_i theory, can you try pulling that file out of the alfa_acr.hak with erffinder or nwn2packer and see if that clears your error? It'll likely cause other resources to fail to compile (missing #include) but it would at least give us a lead to follow up on.

on the off chance you don't have a copy, it's here:

http://nwvault.ign.com/View.php?view=NW ... etail&id=9

I've started a series of tests to see what t might be. Will keep you updated as I go. First test was to remove the script from the ACR, but the problem remained.

I exported all contents from my module in palette categories and reimported them into a new mod directory. I saved and reloaded before each new category.

The error didn't pop up on loading the directory, and all seems well.

Who knows what un-needed files were hanging around in the old directory. My guess is that it was some remnant. Fixed now.

The VFX file is not compiling though.

I'll look into the compile error on acr_vfx_i tonight if I can.

I've gotten that message when I had old 2DA files in my override folder. It happened because the 2DA formats changed and the parser unexpectedly reached the end of file - suffice it to say it's not the most graceful error message. Could well be the case here as well.

Indio- I did basically the same thing with the OAS2 directory and escaped those errors- once again mysterious, I'll just hope that they are an indication that the toolset is becoming less corruption-tolerant, which would be nice if it helps us catch these things early on.

Also, seems there is some reversion and re-patching of one of the spell constants between 1.06->1.10->MotB, so I've got a new alfa_acr.hak that compiles under at least the first 2 (I hear there is still something off with vfx_i under motb though).

As an aside: is it OK to upgrade the OAS to MotB? I'm assuming applicants will need it to play on live servers?
TnD

I guess at this point we might as well all upgrade when possible- I just picked up my copy of MotB, if we run into any problems it shouldn't be too long before we can work through them.

Unless anyone has a compelling reason to wait? Since we're not live by any stretch of the imagination, it's not the end of the world if we get somewhat out of sync as well.

Last night I got all the 2das in alfa_2da.hak updated to be compatible with MotB / v1.10116 - and the ACR is more or less compatible with it as well (though still needs some testing). We should be good to update/upgrade at will. I'll hold on releasing the new alfa_2da.hak until I can set out the new rows for additional Custom Content with GF, hopefully tonight.

MotB doesnt come out over here for another two weeks... should I bother patching now?