It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
In The First Encounter, a bug causes the lasergun fires at a slower rate and builds up to the intended rate at you progress. Its possible this is also in The Second Encounter and is affects the tommy-gun as well AFAIK. Does anyone know if theres a fan-made patch or something that fixes this issue?
Only Steam version is patched for this and other bugs...
Post edited August 05, 2018 by FulVal
avatar
FulVal: Only Steam version is patched for this and other bugs...
From what I've seen on the Steam forums, SS Revolution is buggy in many other areas and hasn't been updated for over a year. Thanks for mentioning it but it's not much of a solution :/.
SS classic, not SS Revolution
Post edited August 12, 2018 by FulVal
avatar
FulVal: SS classic, not SS Revolution
Ah, if thats true I see the issue...
I've found that playing on a local server doesn't affect the RoF. Unfortunately, you'll have to miss out on Croteam's oscar worthy cutscenes. Here's hoping there's a legit fix out there somewhere.
Was replaying the game (CD version) and immediately noticed the moment I picked up the Lasergun:

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

It apparently happens 4096 seconds after you start a new game. The only way to get rid of it is start a new game/level. Basically makes the game unplayable continually.

It also affects the Tommy Gun and Minor Biomechanoids. It's been almost 2 years since this thread. Anybody have any luck finding a fix? The game is not worth playing in this state to be honest.

I don't remember this happening when I played TFE and TSE on Windows XP. Really annoying and gonna stop playing for now. Also made a thread on the Steam forums for TFE classic to see if anyone had any luck (the issue is present in the Steam version too).
Post edited October 04, 2020 by idbeholdME
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. Once it happens, just find a safe spot, leave the game running for a bit over an hour and once the "game time" in Netricsa's statistics section reaches ~ 02:15:00, then resume playing.
Post edited December 30, 2021 by idbeholdME
https://files.seriouszone.com/

Here there are patches
avatar
FulVal: https://files.seriouszone.com/

Here there are patches
Patches are good and all, but this problem was never fixed. The bug happens on GOG, Steam and even on the CD version of the game. The waiting workaround is the only way how to get around it at the moment.
Bumping this because the cause and solution of the bug have been found.

decino made a video analyzing the bug and also offering potential methods of fixing it:

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

Hopefully, the hex editing method also works for the GOG and CD versions of the game.

EDIT:

Note that the addresses in the video are off. The correct addresses are:
TFE - 169860
TSE - 194CE0
See the attached screenshot, which shows the 1st Encounter. Replacing the first occurrence (green border) of 17B7 D138 with 0AD7 233D fixed the bug. Replacing the 2nd occurrence (red border, address mentioned in the video) does NOT fix the bug.

Same with TSE, replace the first occurrence at the 194CE0, NOT the one from the video at 194E2C.

The fix works both on the CD and GOG version too. Tested them both.
Attachments:
hex.png (31 Kb)
Post edited September 22, 2022 by idbeholdME