![]() * Number of rounds: The community uses the "best of 3" format. The submission rules say that this is allowed so I'm leaning towards doing the highest unlockable difficulty. However, there are button combinations that can unlock higher difficulties. * Difficulty: The community uses Champion difficulty, which is the highest you can set it without codes. The game now runs at about the same speed as the other speedruns, but if you have a different opinion on this let me know. I used a DOS benchmarking utility in DOSBox with their configuration and then fiddled with the CPU divider in JPC-rr until I matched the DOSBox benchmark. The speedrun community has a standard of 14500 cycles in DOSBox, which seems to be a good watching speed. I did a test run at the default CPU divider and found it to be a little too fast for my liking. OMF2097 is highly influenced by CPU speed - just go into DOSBox and play around with cycles to see how extreme it is. * Game speed: I think I have this one about figured out, but feedback is welcome anyway. The only reference I have is the page, in which they've recently taken interest in the game and set up some standards (some I agree with, some I don't) I'm looking for feedback on a few things. The problem with the amount of customizability is that it's tough to nail down a good standard for how to set it up. If you're not familiar with it, it's a highly customizable fighting game with giant robots. But here's the thing I learned from that experience: if you can help it, do not tamper with the CPU cycles while the game is running, don't get me wrong, I still tamper with it while the game is running, but now I give the initial CPU cycle boost before I launch the game to avoid similar situations.I've been looking into doing One Must Fall 2097, which works now that the DOS extender crap has been figured out. Thankfully, not all games are like that, in fact it was the very first time I saw something like that happen in the ten or so years I've used Dosbox. But when I first cranked the speed all the way to 8000 cycles, and then launched the game, the game functioned correctly and normally and I could enter that certain location just fine. One last note: Very recently I replayed Innocent Until Caught, an old adventure game by Psygnosis, and I noticed something very peculiar, basically, when I launched the game and then bumped the emulator's speed to 8000 cycles as the intro credits were rolling, it became impossible for me to enter a certain location later on, no matter how many time I clicked on the door. Otherwise, if it is a more recent game, like 90s recent, and the game feels slow, bump it up progressively until it plays smoother, but not so much that the music stutters, and be wary, if you feel a game is too hard because it is playing too fast for your reaction speed, then maybe it is experiencing timer issue and you should slow down the cycles a bit, just in case. So yeah, if you're playing a very old game, like 80s old, leave it at 3000 cycles and it should be fine. Then I changed computer and updated Dosbox and 8000 cycles became my new sweet spot. More than 12500 cycles and the in-game sound and music stuttered, indicating that it was running too fast. ![]() Less than 12500 cycles and the game lagged a tiny bit. I had a computer where I could (and had to) push it all the way to 12500 cycles if I wanted the game to run smoothly. And at that point it depends from one computer to another. When a game doesn't have those timer issues, then typically I found that the more speed the better. And there was also another scene, in the same game, during an arcade sequence where you drive from one location to another while dodging rocks on the way, and if your computer was too fast, you would dodge rocks during five seconds and reach the destination, but if your computer was too slow, you would have to dodge rocks for minutes before you were done with the arcade sequence. I recall a scene in the remake of Space Quest I, when you are stranded on the desert world of planet Kerona, if your computer was too fast, you would have to drink water every ten seconds else you would die from thirst. Sierra point and click adventure games were like that, where if your computer was too fast during arcade sequences or timed puzzles, it would be impossible to solve them in time because the hazard or the danger would simply kill you before you had the time to react to it. There are some games that have timer issues, meaning if your computer is too fast or too slow, the game will be easier or harder, sometimes even impossible. It depends on the game and on the computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |