3 replies to this topic

[Jarno Mikkola]

Anyone has an idea what can cause this or how to repair it?

Well, if you wish to find the culprit... Just run the --change-log function in WeiDU:

If you do not have the "- SoA" at the end of the game directory...
Go to the game directory.
Make a directory called "results".
Run the WeiDU.exe, and if you don't have one, make it from one of the setup-*modname.exe's by copying and renaming it as WeiDU.exe, and then run it.
Push about 10 time Enter and a console appeares.
Insert this:

--change-log spwi909.spl --out results --out results/log.txt

If you do have the "-SoA" at the end...

Try opening a cmd window (on Vista, run "cmd.exe" in the start search, on XP I think it's MD-DOS Command Prompt under Accessories), then use "cd c:\games\BGII - SOA\" replacing c:\games\BGII - SOA\ with the exact path of where you installed BGII.

Then, run "weidu.exe --change-log spwi909.spl --out results --out results/log.txt"

These will make few files appear into the results directory just made, you should post the log.txt, and then there is the unchanged spwi909.spl backup files for each mod component that changed the spell that you can try to replace the current one in the override folder... but make a back up of these files first.

Edited by Jarno Mikkola, 21 May 2009 - 04:07 AM.

[Jarno Mikkola]

I assumed that LR has most likely nothing to do with it, SCS2 is the more likely candidate.
I used the backup file from the SCS2 backup folder as you suggested and now it works again!
Thanks for your quick and competent assistance

Yeah... Now that you know which component messed it up, as the components backup you used that works is the one that messes it up, could you post it here.