Main > Software Forum
Cheat options (overclock) from command line (adding to derivative)
Tiger-Heli:
For anyone following this thread, I just tested (kinda) on a P4 1.8 Ghz with these values:
:crusnu21:65004000:00000000:00003333:00000000
:crusnu21:65004000:00000001:00001999:00000000
:crusnu21:65004000:009C4000:00001999:00000000
This corresponds to a CPU1 overclock of 10% and a CPU0 overclock of 20% for 40 seconds and 10% thereafter.
In-game framerates were fluctuating between 83% and 114% with the average around 88%, so it's not full speed but very playable.
I also dropped the CPU overclock down to 9% and the game re-booted even after the hardware initialization, so I guess we know this is about the minimum CPU capable of handling this game!
EDIT: Fixed the time delay value in the code above.
fignutz32:
It works great for Crusin USA but how can I get it to work for other games?
Tiger-Heli:
--- Quote from: fignutz32 on May 18, 2004, 12:23:13 pm ---It works great for Crusin USA but how can I get it to work for other games?
--- End quote ---
Ok, what part didn't you understand?
Basically, the steps are -
1) Start the game with the "-cheat" option enabled.
2) Type F11 so you can see how fast the game is running.
3) Press the Tilde key and underclock/overclock each processor to see which settings give you the desired framerate. (Note the in-game speed may be different than attract mode). Write down settings.
4) Convert to hex and add an entry to the cheat.dat file.
5) Start the game and see if it runs with that setting. If it re-boots continuously, add a delay to get past the initialization screens, then underclock (by less than the final amount) to get these faster.
BTW, I posted an announcement about this on the MameWorld Submit News board and got responses anywhere from "It's not arcade authentic and screws up the game logic" to "Not this Lameness again."
I feel that I should point out that by doing this, you are changing the game physics similar to skipping frames.
I also feel that I should point out that Cruisin' at 88% speed with underclocked CPU's is a lot more playable than Cruisin' at 15% speed with non-underclocked CPU's.
And for everyone else that thinks this is a bad idea - It's an OPTION (and not a particularly easy one to implement). If you don't want to use it, just ignore it.
Howard_Casto:
I think your efforts should be commended, but just a quick question/comment....
It's not just me, underclocking totally screws up the audio right?
If that's the case with everyone, then what exactly is the point? Say what you will, but a game with bad audio is just as unplayable as a game that's too slow.
Tiger-Heli:
--- Quote from: Howard_Casto on May 18, 2004, 02:17:38 pm ---I think your efforts should be commended, but just a quick question/comment....
It's not just me, underclocking totally screws up the audio right?
If that's the case with everyone, then what exactly is the point? Say what you will, but a game with bad audio is just as unplayable as a game that's too slow.
--- End quote ---
Ermmmn, dunno - I don't think I'd say it totally screws up the audio, I'd say it doesn't fix the audio, but I only tested it on two computers - P4 1.8 Ghz with audio working but speakers off (just tested with speakers on - distorted audio) and a Duron 850 with audio that can only hit about 55% speed with full overclock, so is basically unusable.
The audio sounded pretty poor at 15% of full speed with non-oveclocked CPU's, so I'm not sure you've lost anything, and the graphics flow better.