hmmm...
Yes K-mod is another mod that this was built on top of.
It should work if you put the Fallout TTW folder (the one in the zip) into the BTS mod folder... it is strange that it doesn't. Can you explain what you mean by not work?
For example:
Does it crash?
Does it not load at all?
Does it not appear in your mods list when you play Beyond the Sword?
I have never used the steam version, so I am not sure if it has a quirk to it..
hmmm...
have you tried any other mods?
Do the mods that come with Bts show up?
Did you put it in the folder that has those base mods (did you even find the folder that has those base mods?)
I am not sure what will happen without admin permission as BUG needs admin permission to work, no idea how it works with steam..
have you got any mods to work?
If not I suggest asking in one of the tech help threads about installing mods with steam version, as I can't help with that for Bts.
I haven't tried any other mods. I put the fallout mod in the base mod folder with the default mods. I found out how to run as admin(had to go to the install folder and run the exe in there) and still nothing showed up.
for iOption in xrange(GraphicOptionTypes.NUM_GRAPHICOPTION_TYPES, GraphicOptionTypes.NUM_GRAPHICOPTION_TYPES + 4):
CyUserProfile().setGraphicOption(iOption, gc.getGraphicOptionsInfoByIndex(iOption).getDefault())
That line looks quite wrong.
Say we have 10 graphics options (I don't know the actual number, doesn't matter)
The first line sets the upper limit to 10+4=14. The lower limit is 10. In other words the loop will run 4 times with iOption set to 10, 11, 12 and 13.
The next line calls the info from the game vector. This vector has the same length as the number of options, which mean valid arguments are in the range 0 to 9. Any arguments outside that will cause problems.
It is possible that somebody added more options without updating GraphicOptionTypes.NUM_GRAPHICOPTION_TYPES, but that would be really bad coding. Now the question is what is it supposed to do and how can it be made to do as intended. Clearly the current code is quite broken, both by design and by what it does.
That's actually a pretty good argument for coding like this. I was right that it was due to a broken design, but it was the broken mac DLL support rather than this piece of code.It is neither broken by design nor by what it does, because it is designed precisely that way for pure python mods, as mac users cannot have modified dll.
I wouldn't be surprised if that is precisely what happened here. It would be nice if it could be checked somehow and fail with a proper error message. However it doesn't look like vanilla has any getNumGraphicOptionsInfos(), which mean a proper python only test could be quite tricky.Obviously if lib copied the codes blindly without adding the extra graphic options which were added, the codes will fail.
In C++, that would be written771A2D94 mov dword ptr [eax],esi
esi = *eax;