inselaffe on 25/4/2008 at 22:30
Okay, here are 2 problems that I am having with ss2 (and also thief gold if i remember correctly).
I use shift in my binds to run. Now something about the games doesn't like this, and even though the controls appear to be set right when you start the game, they are in fact not.
When I start the game I cannot run. It ignores my presses of shift+w. Instead I have to load my binds and then it works. Even though the binds I had set are exactly the same as the ones I have just loaded. I does this every time I start the game and it's really starting to become annoying. I also then have to go into the menu and adjust the mouse sensitivity, as loading my binds seems to automatically reset the sensitivity (I tried resaving the binds with a higher mouse sense but it didn't do anything, so obviously it's just resetting it on every bind load to a default value).
I think by default shift is used as a movement speed modifier - to slow you down - at least it is in thief gold. Anyway I think it might be resetting it to this or something without displaying it in the options.
The second problem is eax. I know for a fact this happens in thief gold as well. (Probably 2 as well but I ain't had that installed for ages). What happens is you have to go into the menu and turn eax off and then on again for it to actually be active within your game for some stupid reason.
All in all, these two problems mean that everytime I start the games, I have to go into the menus, load my binds, change the mouse sensitivity and turn eax on/off. At first it wasn't too much of a problem but now it's becoming increasingly annoying.
If anyone knows of a fix (I imagine it would be cfg and such related?) then I would much appreciate it. Thanks :)
Vlad Midnight on 27/4/2008 at 23:19
Sounds like to me your .bnd files are set to read only. That would explain why its not remembering your key prefrences. It will load whats in the .bnd on start and when you change the settings that is saved in the game only (RAM)
If thats not it, dont know what else to tell you.
inselaffe on 28/4/2008 at 00:08
Hmm I just checked and they are not set to read only :-/ It does pick up changes when I save things but it doesn't appear to like it when you set things to use shift (or maybe shift + something?).
Also, why would the having to turn on eax and turn it off again be to do with user.bnd or user2.bnd :S
Vlad Midnight on 28/4/2008 at 02:28
What if you opened the .bnd file in notepad and edit the file manually. The key settings it uses come from those files. There may be alot in there, but its pretty easy to understand.
bind w+shift +walkfast
bind w +walk
It would probably be the cfg004.bnd and the top line would be what you decided to call your saved binds
EX:
; My Binds
I found these in cam.cfg
They look like the boot settings to save for eax and other
skip_starting_checks
game_screen_flags 13
game_full_screen 1
sfx_vol_3d 0 ?
game_hardware 1
game_screen_size 1024 768
vmCenterY 0.5008818507
sfx_vol_2d 0
ambient_volume 0
game_screen_depth 16
vmCenterX 0.5004897118
sfx_channels 24
sfx_device 2 ?
master_volume -1
I lost eax when I "upgraded":erm: to Vista, so I know my setting is off above
inselaffe on 30/4/2008 at 13:43
ah yer thanks I managed to get the shift thing working by editing shock.bnd to add in the bind shift+w +walkfast
Not tried it for thief yet but it should be much the same thing (or I hope so as thief gold is an older version of the engine :erm:
I'm not sure what gets loaded when you start the game, cos a lot of binds in that file are different to what I had them as, but maybe it is a combination of this and another file. I don't know.
Anyway, I also discovered that the dark engine doesn't seem to differentiate between left and right shift? or does it? When I tried putting lshift and rshift it didn't seem to do anything. Unless they are called something different.
The only thing that's annoying is that when you run (with shift + w) and then walk (letting go of shift) and then try to run again (pressing shift again) the dark engine will not run again until you let go of w and repress it. I don't know if there is any way to fix this? I tried binding both shift+w and w+shift to see if it looked for one of the keys being pressed first and then the other, to see if that would fix it, but it doesn't. It's only a minor thing though, just curious as to whether it is fixable.
Hmm still not managed about the eax, no :S I set sfx_vol_3d to 1 but that didn't do anything. In fact I had to add it to my cam.cfg I don't have any of those values in there but I guess it's not a worry.
It seems a similar type of problem though, having to turn it off and then on again to get it working, so I am guessing it is a cfg / sometype of file like that problem as well.
Thanks for the help so far :)
