Glitch:Sped up timer
|Sped up timer
|A glitch in||Carmageddon|
|The title of this article or section is conjectural.|
This means that it's not an official name.
Back when the first game was released, mid-90s machines had just enough power to run the game at a playable speed. Unfortunately, since then technology has come on leaps and bounds: Modern computers can run Carmageddon easily... too easily. The normal framerate can reach speeds of over 250 FPS, and Carmageddon's timer runs according to it.
The only things needed to witness this glitch is a modern computer. Anything with a Pentium III processor or above is enough.
The timer should run way faster than normal. About 3 timer seconds should be elapsed in a real second, making races really difficult.
As explained above, the timer runs according to the frame rate, for some reason. So, when the game is running at ~60FPS, the timer practically works well. But if the frames reach around 300...
Strangely, all other timers, like the powerups' time period, do not depend on the game's speed. To make matters worse, there doesn't seem to be any patch on the Internet to fix this problem. There are some workarounds, though.
The best solution is to make use of the cnc-ddraw library. Drop ddraw.dll into the Carmageddon folder. When the game is started, a ddraw.ini file will be created and can be fully configured. Setting the maximum FPS to something less than 30 can solve the problem as well as make the game less CPU-intensive, and prevent the need to use DOSBox when using the IWANTTOFIDDLE code (because of the framerate on modern systems, the important text files can quickly re-encrypt themselves).
Speaking of DOSBox, one can use it to run the game and throttle the speed, allowing for normal play.
Alternately, there are some minor solutions. Purposely lagging the game can make it run slower, and thus, make the time run slower. Some ways to do this include setting all the options to their highest parameters (some of them can even be changed in the game's files to allow values far greater than the limit) or attach some CPU consuming applications to Carmageddon's process.