seanas

it can't be done within the game engine: both the paladin and the ranger are hardcoded to Fall when their reputation falls. the only solution is TDD's workaround, which is to always reset yr reputation to be 10 whenever it diverges from 10. there is simply no other way around this limitation.

it would seem as if teh Fixpack has altered a file that BP is looking for to patch (and BP is using a kludgy old weidu routine to do it too), so that when BP comes to look for it to patch, the file (as BP is expecting to find it) is not there. the long term solution, as in all such incompatibilities, is for BP to be updated to account for the Fixpack's changes.

the short-term solution is, as was said at G3, to comment out the offending lines in BP's tp2 file (and as for why the Fixpack is altering those files: i have no idea ^^ ). the functional effect of commenting out the BP lines is that the script is not patched... which is exactly what is happening at the moment with the warning notice. unless i'm mistaking something and the BP install is failing at that point, those warnings can be safely ignored.

sorry, my BGII knowledge is a bit rusty at the minute, but isnt this:

~SETUP-NEJ2.TP2~ #0 #10 // Areas & Sounds
~SETUP-NEJGUI.TP2~ #0 #0 // GUI registrar for Never Ending Journey
~SETUP-NEJ2V602.TP2~ #0 #0 // Never Ending Journey v6.02 (cummulative patch)
~SETUP-BD-TOB.TP2~ #0 #0 // Baldurdash Fix Pack for ToB, v1.5 WeiDU
~SETUP-SOS.TP2~ #0 #0 // Shadows Over Soubar, v1.11
~SETUP-SOS.TP2~ #0 #1 // Remorhaz walking speed adjustment (for ENGLISH version .EXE ONLY!!!)
~SETUP-TDD.TP2~ #0 #0 // The Darkest Day,  v1.11
~SETUP-TDD.TP2~ #0 #1 // TDD Character Kits
~SETUP-BGT.TP2~ #0 #0 // Baldur's Gate Trilogy - Core 1.01
~SETUP-BGTNEJ2.TP2~ #0 #0 // BGT-NeJ2 Compatibility Patch

a disaster waiting to happen?

NEJ2 first (even installing NEJ2 with a mega install...) THEN an old BD THEN SoS and TDD and BGT AND THEN NEJ2 compatibility? isn't there an entire array of errors there? i would have thought the question was 'why have you had so few errors?'.

merged as per request, and i'm glad to hear it was sorted. we don't necessarily need yr weidu log DogCavalry, but i'm curious to know the order you've got TS-BP, TDD, etc - i strongly suspect, as i said above, that TS-BP has to come after TDD (and any other mod that alters animations, altho there arent many of those) in order to avoid this crash.

on a lighter note: i will finally be able to get my stuff out of storage in about a month's time, so work will be able to recommence on a final BP release (and apologies for the absences). let's work on the end of June as a deadline; i'll update the workroom buglist in the middle of June with progress to date.

Hmmm, i had started a new BG1 game, and could barely afford normal arrows/boots. The bags/scroll cases etc, had less than 20 items, i had no boots of speed/rings of regen, and i had sound turned off completely and graphics at a minimum, but nothing made a difference.

Once i dumped the bags/cases it went back to normal.

i doubt very much that i was trying to do too much, the problem happened when the bags/cases was in my invent, and stopped when they weren't.  That,  imho,  means the bags/cases are to blame.

there are some mods - and i can't remember which ones at the moment, i'm afraid - which continually check yr inventory, including containers, for specific items (to alter/remove/modify them), which when combined with the unlimited bags mods that everyone has installed, means that the script engine is perpetually checking yr bags on the off chance that item x is there when it wasn't 0.15 seconds previously. from memory, again, these mods dont typically show slowdowns on non-Mega Mod installs, which is all they were ever tested on. on Mega mods installs, however, they cause death by slowdown. as i said, i cant remember which mods these are, so i'm not of great help, but that's why some ppl get the bag-slowdown and others dont - you could always try removing the unlimited bag mods; altho this is drastic, it should offer a workaround - unless someone else cn identify the actual mod doing the constant inventory checking.