Vanilla BG 1, how do you increase the slow walking speed?
sarevok57
Member Posts: 6,002
So I've noticed that in vanilla BG1 the walking speed seems to be quite slow, even at frame rate 60, is there a way I can crank it up a bit without using the tutu/trilogy mod and without using that boot mod?
I would prefer if I could actually go into the game files itself somewhere and increase the speed for everyone ( baddies included)
or am I just going to have to accept that there is really no other solution?
I would prefer if I could actually go into the game files itself somewhere and increase the speed for everyone ( baddies included)
or am I just going to have to accept that there is really no other solution?
0
Comments
I suppose that it is hard coded. But I am only guessing, as tutu/trilogy use the BG2 engine and afaik no mod exist to do what you want in the BG1 engine. I am no expert in this kind of things.
He's alright in my book!
its funny really, even back in 2010ish I never noticed the walk speed being so slow, maybe its because I was still playing it at 640x480 res, but at that res I cant even see anything
the only reason why I don't want to install the trilogy/tutu mods is because I don't want my bg1 game to look like bg2 and I don't want class kits in my bg1 game
the reason why I don't do the boot mod is because then I will be significantly faster than all the monsters when I shouldn't be ( and even though im not one for kiting) I don't want to have an unfair advantage against them
plus I would have to sword coast keeper every character I made to match up with the baddies
Too bad it's an invasion of privacy. No can do.
So...
What's that "Defiler.net" thing you got there?
speaking about that @belgarathMTH if you increase your path finding to 400000 you will notice a huge difference in how well your dudes will be at path finding, granted they cant "push" each other out of the way ( since that was implemented in SoA) but its still a lot better than nothing
Not sure how well that would work in practice. But that's about the only way to do it.
Oh, and look! Someone already did the hard part:
https://forums.beamdog.com/discussion/48165/testers-wanted-tweaks-is-dead-long-live-tweaks
The "Use BG Walking Speeds" component does exactly this. Except even slower.
Here's the relevant code, annotated and slightly changed by yours truly:
BACKUP ~myMovementMod/backup~ // location to store files for AUTHOR ~up for grabs~ // email address displayed if install fails VERSION ~1.0~ // below code taken from "The Tweaks Anthology" found here: // https://forums.beamdog.com/discussion/48165/testers-wanted-tweaks-is-dead-long-live-tweaks /////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\ /////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\ ///// \\\\\ ///// Use BG Walking Speeds \\\\\ ///// \\\\\ /////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\ /////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\ //BEGIN @121000 DESIGNATED 1210 //GROUP @13 BEGIN ~Modified Movement Speed~ DESIGNATED 1 REQUIRE_PREDICATE NOT GAME_IS ~bg1 totsc iwd how totlm iwd2 pst~ ~incompatible game~ // For every installed creature COPY_EXISTING_REGEXP GLOB ~^.+\.cre$~ ~override~ // read its animation type READ_SHORT 0x28 "anim" ELSE 0 // patch the creature if it is a humanoid playable race PATCH_IF ( ("%SOURCE_FILE%" STRING_COMPARE_CASE "charbase.cre" = 0) OR ("%SOURCE_FILE%" STRING_COMPARE_REGEXP "^AERIE[0-9][0-9]?\.cre$" = 0) // aerie comes as a ogre, so gets missed OR ("%anim%" = 0x5000) OR ("%anim%" = 0x5001) OR ("%anim%" = 0x5002) OR ("%anim%" = 0x5003) OR ("%anim%" = 0x5010) OR ("%anim%" = 0x5011) OR ("%anim%" = 0x5012) OR ("%anim%" = 0x5013) OR ("%anim%" = 0x5100) OR ("%anim%" = 0x5101) OR ("%anim%" = 0x5102) OR ("%anim%" = 0x5103) OR ("%anim%" = 0x5110) OR ("%anim%" = 0x5111) OR ("%anim%" = 0x5112) OR ("%anim%" = 0x5113) OR ("%anim%" = 0x5200) OR ("%anim%" = 0x5201) OR ("%anim%" = 0x5202) OR ("%anim%" = 0x5210) OR ("%anim%" = 0x5211) OR ("%anim%" = 0x5212) OR ("%anim%" = 0x5300) OR ("%anim%" = 0x5301) OR ("%anim%" = 0x5302) OR ("%anim%" = 0x5303) OR ("%anim%" = 0x5310) OR ("%anim%" = 0x5311) OR ("%anim%" = 0x5312) OR ("%anim%" = 0x5313) OR ("%anim%" = 0x6000) OR ("%anim%" = 0x6001) OR ("%anim%" = 0x6002) OR ("%anim%" = 0x6003) OR ("%anim%" = 0x6004) OR ("%anim%" = 0x6005) OR ("%anim%" = 0x6010) OR ("%anim%" = 0x6011) OR ("%anim%" = 0x6012) OR ("%anim%" = 0x6013) OR ("%anim%" = 0x6014) OR ("%anim%" = 0x6015) OR ("%anim%" = 0x6100) OR ("%anim%" = 0x6101) OR ("%anim%" = 0x6102) OR ("%anim%" = 0x6103) OR ("%anim%" = 0x6104) OR ("%anim%" = 0x6105) OR ("%anim%" = 0x6110) OR ("%anim%" = 0x6111) OR ("%anim%" = 0x6112) OR ("%anim%" = 0x6113) OR ("%anim%" = 0x6114) OR ("%anim%" = 0x6115) OR ("%anim%" = 0x6200) OR ("%anim%" = 0x6201) OR ("%anim%" = 0x6202) OR ("%anim%" = 0x6204) OR ("%anim%" = 0x6205) OR ("%anim%" = 0x6210) OR ("%anim%" = 0x6211) OR ("%anim%" = 0x6212) OR ("%anim%" = 0x6214) OR ("%anim%" = 0x6215) OR ("%anim%" = 0x6300) OR ("%anim%" = 0x6301) OR ("%anim%" = 0x6302) OR ("%anim%" = 0x6303) OR ("%anim%" = 0x6304) OR ("%anim%" = 0x6305) OR ("%anim%" = 0x6310) OR ("%anim%" = 0x6311) OR ("%anim%" = 0x6312) OR ("%anim%" = 0x6313) OR ("%anim%" = 0x6314) OR ("%anim%" = 0x6315) OR ("%anim%" = 0x6500) OR ("%anim%" = 0x6510)) BEGIN // patch starts here READ_BYTE 0x33 fx_flag READ_LONG 0x2c4 fx_off READ_LONG 0x2c8 fx_num WRITE_LONG 0x2c8 (fx_num + 1) // fix offsets after inserted effects PATCH_FOR_EACH offset IN 0x2a0 0x2a8 0x2b0 0x2b8 0x2bc BEGIN READ_LONG offset offset_val PATCH_IF (fx_off <= offset_val) BEGIN WRITE_LONG offset (offset_val + 0x30 + (fx_flag * 0xd8)) END END // RELEVANT PART STARTS HERE INSERT_BYTES fx_off (0x30 + (fx_flag * 0xd8)) WRITE_SHORT (fx_off + (fx_flag * 0x08)) 176 // opcode: Movement Rate Bonus 2 WRITE_BYTE (fx_off + 0x02 + (fx_flag * 0x0a)) 1 // target: self // WRITE_LONG (fx_off + 0x04 + (fx_flag * 0x10)) 0xfffffffd // not noob-friendly WRITE_LONGS (fx_off + 0x04 + (fx_flag * 0x10)) -3 // value: -3 >> CHANGE THIS VALUE << WRITE_BYTE (fx_off + 0x0c + (fx_flag * 0x10)) 9 // timing: permanent WRITE_BYTE (fx_off + 0x12 + (fx_flag * 0x12)) 100 // chance: 100% // This adds a permanent effect to the creature, lowering its movement speed by 3 points. // Simply replace "-3" with "4" if you want +4 movement speed, for example. // DONE. // technical side note: // 0xfffffffd (used in original unsigned version) is simply the hexadecimal // big-endian two's-complement representation of -3. I changed the code // to use a signed operation instead, which makes it less complicated to input // new values regardless of the sign. END BUT_ONLYTo actually install that code, get yourself a WeiDU.exe, rename it to "Setup-myMovementMod.exe" and put it inside your BG directory. Create a new directory called "myMovementMod" inside your BG directory. Inside the new folder, create a new text document, paste the above code into it, change the value "-3" to the desired modifier, save it and rename it to "Setup-myMovementMod.tp2".
Now all you need to do is run "Setup-myMovementMod.exe".
The base creature speed is 10. So don't go crazy. Stay in the single-digits.
Oh, btw: I HAVE NOT ACTUALLY TESTED THIS! Use this at your own peril...
I appreciate the effort and time put into this, but this looks like a lot of thinking and fanciness, maybe some time in the future I might give this a try if the walking speed continues to give me that unscratchable itch
thanks for the input
The first part, the one that ends before // patch starts here, automatically apply the pach to every humanoid in the game, enemies and NPCs. and has not to be changed.
The following part is the patch itself and need only to change that value, that @klatu has left unchanged to let you chose how much you want to speed up the humanoids.
the parts after // are comments for those who have to change the code and are inactive.
You are 10 minutes far from having what you want, all the work has been already done by the original coder and klatu.
But: setting it too high values made the game ignore this setting and fall back to 30 default (60 may be too much). I well remember running the game at 40 or 44 fps usually, actually speeding all things up significantly.
This all I'm very sure for bg2 vanilla, but I can't remember bg1 vanilla settings exactly.
It looks like you are left with two options: Slow walking speed in BG1 or Tutu/BGT/BG1EE for a faster walking speed.
The OP was clear about why he don't want to do it, their effect is not to speed the game, but to unbalance it.
Even people that do it because they are bored to see the party walking slowly through areas should be aware that they unbalance the game and make it quite easier. Unless they unequip the boots before each battle, that is a very annoying thing to do.
I am not saying that is wrong to do it, as I think that nothing can be wrong in our personal gaming, if it make us happy. But I say that being unaware that boots of speed do much more than let you walk fast through the areas is being not informed about what they really do, or eventually being informed but cheat with themselves.