It's Helicopter Rescue! On the Odyssey2! Where every game ends in an exclamation mark! It might be compensating for something!
This is a multi-game cartridge. I only play the second game on it. The helicopter looks and sounds pretty cool for this console, otherwise it's not very interesting. I get as many points as apparently possible and end input as soon as possible. There don't seem to be any odd quirks to movement.
BizHawk and TASVideos use different framerates for O2. BizHawk uses 60 and TASVideos 60.05645306588193. Which one is correct?
nymx: Changing the branch to reflect goal of the game: Maximum Score
As for the run, nothing was missed in terms of optimization. I hate it that so much time was left over, but it couldn't be helped...there was no way to get another rescue with what's left. Ending input is the only option.
BizHawk and TASVideos use different framerates for O2. BizHawk uses 60 and TASVideos 60.05645306588193. Which one is correct?
According to the MAME XML funnies, the proper framerate for odyssey2 is ~59.826098 and for videopac is ~49.701460 (European version)
I don't know about exact values because BizHawk will always force O2Hawk and MAME doesn't want to start it because i8244/i8245 is missing
UPDATE: I eventually found the needed Intel files (they were in the BIOS section lol), and after mounting a cartridge (the BIOS again, don't ask me), mame-framerate.lua printed out the following:
89478485/1495643 (~59.8260982066) for odyssey2
89478485/1800319 (~49.7014612410) for videopac
Also a 4:3 display ratio for both, but it's probably obvious ;) UPDATE: mostly because the screenshot res is 320x240 lol
Maybe the AVI dump from BizHawk would display something else (I didn't check that yet), but (UPDATE: it's 60 FPS sharp), it's MAME that's the most correct here, I assume.
MAME's framerate is still an approximation because we have to reduce a 64-bit integer value of attoseconds that represent frame duration to something usable in video files. But over the course of many hours the framerate currently reported by User movie #638183669502074999 is accurate enough to rely on.
Before this we got different values out of MAME (60.056453065881932 and 49.970017989206475) because we relied on MAME's AVI dumping back then which I only recently fixed, but those were the values used by the site code. I didn't expect Alyosha to just use 60 there.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Which value should be used then? Should BizHawk be updated?
What BlackWinnerYoshi posted, and it should be used on site and hawk.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
