Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: manwiththemachinegun on June 05, 2016, 02:38:03 pm
-
3.7.4 RC2, though this was in prior versions of FS2.
Intermittent bug, I have no idea what triggers this, possibly since I have a multiprocessor CPU but that shouldn't matter since I assume most people have one. Basically, if you crank time compression up to X4 or higher, and then drop it down to X1, the game still runs at a significantly higher speed. Before anyone asks, yes I was SURE it was reading X1 and the game engine still ran super fast. Weapons and enemy fighters move at a blistering pace, far more than the relatively "normal" speed of combat, the only thing that seems to fix it is quitting the game completely and trying again. It carries over between missions and quitting to menu.
Has anyone ever run into this before? And is there an FPS limiter for the FS Open engine?
-
FPS should be limited to 120 by default. The only way to disable it should be by using the -no_fps_capping flag.
-
Messing with some options, set processor affinity to config value seems to be working. But I have no idea beyond that.
-
FPS should be limited to 120 by default. The only way to disable it should be by using the -no_fps_capping flag.
Which you shouldn't do, by the way; it ****s things up and we don't officially support its use.
It carries over between missions and quitting to menu.
If you change missions without changing time compression, does it still run faster than normal?
Because time compression gets set to the same value regardless of whether or not it was set to anything else.
-
Yeah, it's still running fast. Last mission it was working fight "Love the Treason" and the next it was 1920s talkie speed.
The frustrating thing is it isn't CTD so I can't generate an error log. Last time I played with FPS on it showed it was capped at 50.
-
The frustrating thing is it isn't CTD so I can't generate an error log.
Debug logs are generated every time a debug build is run, not just whenever it crashes. That being said, the effect being described doesn't seem physically possible (https://www.youtube.com/watch?v=xdEqIbX50DE&t=247); set_time_compression(1.0f) multiplies that 1.0f by 65536.0f, converts to a "fix" (an integer type) and then assigns the result to Game_time_compression. The starting value of Game_time_compression is 65536. I cannot imagine how this bug could be happening unless your computer either doesn't know how to multiply floating point numbers or doesn't know how to convert them to integers, in which case I'd expect there to be far more drastic effects than "time compression doesn't set right".
-
Well, to start with, the debug log if you please.
-
Well, to start with, the debug log if you please.
Not sure how to do one of those table things, but here's the debug file.
Got the error reproducable on Vassago's Dirge during the mission where you have to use the Lemnos to shield an Aeolus from the Vassago and a bunch of fighers. The mission plays SO FAST even at X1 speed, it's not possible to complete it.
[attachment DELETED!! by Strong Bad]