Weapon slow down bug. Any solution?

[InconspicuousBlackVan]

https://www.youtube.com/watch?v=kx9wgDa4LbQ&ab_channel=FramePlay-MediaConservatory

Was replaying the game (CD version) and the moment I picked up the Lasergun, I knew it was just wrong from what I remembered. I assume the same problem is in the Steam version too (author of the video claims it is the Steam version). Is there any fix for this? I don't remember this happening when I played on Windows XP.

It affects the Lasergun, Tommy Gun and even Minor Biomechanoids. The game is frankly unenjoyable/not worth playing because of this. Any fixes?

[Funny Rat]

This is a known bug in the engine.

I think Serious Sam Classics Revolution on steam fixed this but not sure

[UmbralPenumbra]

Originally posted by ♥♥♥ CRUSADER:

This is a known bug in the engine.

what causes this bug? im curious

[InconspicuousBlackVan]

Originally posted by ♥♥♥ CRUSADER:

This is a known bug in the engine.

I think Serious Sam Classics Revolution on steam fixed this but not sure

So why is it not fixed for the classics too? The Revolution is pretty much a different game from the original so playing that is really not a solution TBH.

Originally posted by PC Incompatible:

Originally posted by ♥♥♥ CRUSADER:

This is a known bug in the engine.

what causes this bug? im curious

My guess would be some kind of integer overflow since it happens exactly 4096 seconds after you start a new game and 4096 is 2^12. But still strange since I disticntly remember it not having this issue on Windows XP.

[UmbralPenumbra]

Originally posted by Caius Misus:

My guess would be some kind of integer overflow since it happens exactly 4096 seconds after you start a new game and 4096 is 2^12

I assumed that as well, however afaik no integer type is 12 bits, either unsigned or signed 8/16 most commonly, but im not a programmer so i cant say for sure. maybe the other 4 bits are used for something else or just not at all

the strangest part to me is I dont think ive ever noticed this happening. though i rarely used the laser gun. so its possible i just never was using it at the 4096 second mark so the slowdown wasn't obvious. i feel like i have a vague memory of thinking sometimes it shoots slower. id love to hear an official croteam explanation as to whats going on because it's a very peculiar bug

[InconspicuousBlackVan]

Just managed to test it on a 32 bit Windows XP PC and the bug does NOT happen there. No slowdown after 68 minutes. So this means it is probably caused by playing the game on 64 bit systems.

EDIT:
Nevermind. It still happens on a 32 bit system. Turns out I was looking at "playing time" instead of game time. Still happens at exactly the same time - 01:07:15. Time to play through the game in 67 minute segments with 67 minute idle times inbetween, I guess... :/

EDIT 2:
Good news. Turns out this bug happens only once. After the 67 minutes, the bug triggered. I left the game idle for another 67 minutes and the weapon speeds returned to normal. And they stayed that way forever. So I resumed playing at about 02:15:00 and everything worked fine until the end, where I finished the game at about 07:45:00 game time.

So this could be considered a solution.

[yetanjo]

https://www.youtube.com/watch?v=PpfpfDNFdvQ

This video goes into detail about the bug and offers a solution around the 7:30 mark.

[InconspicuousBlackVan]

Originally posted by yetanjo:

https://www.youtube.com/watch?v=PpfpfDNFdvQ

This video goes into detail about the bug and offers a solution around the 7:30 mark.

Incredible to finally have the bug exposed and even a way to fix it available. Wasn't even aware that the bug would repeat again at 18 hours. If you ever reached that point, then the "waiting it out" method would no longer be a viable option.

I hope the fix in the video (the hex editing method) also works on the GOG or the CD version. I think the engine.dll wasn't touched in any of the patches, so hopefully yes.

[LiL blade]

does the fix actually work? cuz it isnt working for me but i did already start a playthrough of the game so that might be the reason why

[аnŌn]

Originally posted by BLADE 69:

does the fix actually work? cuz it isnt working for me but i did already start a playthrough of the game so that might be the reason why

Addresses that are in the video are wrong, it should be 169860 for TFE and 194CE0 for TSE.

[UmbralPenumbra]

So technically this isn't a bug, it's just a byproduct of how floating point numbers work on computers using the IEEE754 floating point specification, and the developers didn't uses a sufficient epsilon. Interesting

Originally posted by аnŌn:

Addresses that are in the video are wrong, it should be 169860 for TFE and 194CE0 for TSE.

Well, he said "as of this video", so if the games got updates since then it might've changed

[InconspicuousBlackVan]

Originally posted by Unoriginal Name:

Well, he said "as of this video", so if the games got updates since then it might've changed

The addresses in the video point to an occurrence of the 17 B7 D1 38 value, but not the correct one. The ones in the previous post are correct. Same with both the CD and GOG version of the game.

There are 2 occurrences of 17 B7 D1 38 when looking at the file in a hex editor, the addresses of which are quite close to each other. You need to replace the first occurrence to fix the bug, but in the video, the addresses point to the 2nd occurrence, which does nothing when replaced with the new value.

Probably just an unfortunate mistake in the video.