Hey,
Well here is an update. I've isolated as far as I can tell what is causing this. The only thing left would be to fix it (Outside of 2 big files)
For testing and everything, this is caused by having 2 gamedata blocks of code. As you already know, the -mod command does not load what you have in gamedat.ini, but instead loads what it has in the oringal .ini file. For some reason, I think the options are loaded after the first block is read, but before the second one that you've moved to a different location using the -mod command. When it opens the gamedata up again, even though there may be nothing in the code, it resets the game settings.
To make a long story short (too late!), the best way to demonstrate it would be to find where you have the gamedata block and remove it (temporarily) from the .big file. Load the game and the bug goes away. (At least it did for me.) I still need to play with different files to see if there is one file that will load it correctly, but at least for my mod I've found the root cause if not an answer to fix.
This would also explain why it only happens with the -mod command. No other approach tries to load 2 gamedata blocks.
Robert J.
Edited by robnkarla, 10 July 2007 - 06:04 AM.
