Cumbria, England(Record kept here since I cannot now find Activity Log) I edited the rule defining timing start which was inaccurate and ambiguous, to reflect gain of control. petaQ 27/10/21
As I understand it no emulator runs Rev 00 correctly. Just don't use Fusion. Idealy Bizhawk because it has a native frame counter and is a more known quantity (at least for me). Tako or other observers can you help me confirm an understanding here?
When I've modded other emu-primary leaderboards with Bizhawk runs I've done (frame count) / vsync (59.92274) - is that a sufficient equivalent to console RTA or does it fail to account for lag properly regardless?
I'm not sure what memory variables you'd like - but I have access to the money area, parts levels, and win/losses, things like that. An autosplitter would simply need to take account of the change of opponent after each series of races, so it could flick depending on opponent memory value.
For now I'll say that emulator runs would be branched off from console, but depending on responses we may be able to bodge it.
Cecil, can you confirm whether you wanted to run Original Mode on emulator or console?
Shime, what do you mean by apply the same thing? ^^ The plan is to use RTA for Original Mode, to be clear.
Yeah one thing I could easily do in the next few days is auto-test a number of things by doing a hack where I fix track position and remove collision, and race the same course at the same speed each time but changing different parts to see what works best. My thinking with early crash upgrades is that the sooner we get top accel, handling and speed, the advantage multiplies through every other race we do in the run. I would be very interested to see you submit some Arcade times! There's a bounty on Africa right now so just submitting any runs before new year could win you $30 up to $100. If you'd like to add me on Discord feel free, I'll start tinkering in the next few days and we can post significant results here to encourage competition.
Hey! Welcome in. <3 I started a tutorial a while ago, I would love your feedback on what is good and bad about it.
The Rom with Rev A is showing up as Rev 01 when I load it. The two versions handle differently and have some cosmetic changes. Rev 00 is the one with Morobare/Bridalstone signs; Rev 01 has Soroban/Genesis signs instead. Almost all top runners prefer Rev 00 for the way it handles: its frame rate is uncapped meaning there is speedup/slowdown depending on traffic, which effectively gives you a bit more reaction time in difficult areas. Rev 00 also has more responsive steering. The two feel very very different, but both are permissible for runs. In fact emulators have a really hard time with Super Hang-On and a console tends to run slower, though again most top players have found using emulator has sharpened their skills.
There is no autosplitter because the in-game timer is what we use, and it's bugged: subseconds carry over between sectors so currently we have to manually retime runs. Because of problems with emulator timing accuracy, nobody has yet done a speedrun of Original Mode. It would have to be done on console therefore. It would be a giant, giant pain to route and would likely take hours, but if you want to do such a run I would welcome it.
You can also find a tutorial on Original Mode mechanics here: https://gamefaqs.gamespot.com/genesis/586503-super-hang-on/faqs/15481
If you are set on running that mode let me know and we can work on routing together. I imagine there will be pinch points where we want to repeatedly abuse the break bike/retire function to get lots of money and do massive upgrades.
Any further questions please ask away!
I was requested by SRC to ask for the addition of GBC Marbles manually through you guys in the series. The initial run is linked here:
As of 29/8 ShimeGabriel has taken first place in the new run bounty with a 3'19"26!
As of 23/8/28 the new run bounty has Gustavo_Kennedy in first place, and Shime in second at 3'21"960. Nobody has a third place run yet!
Hi, welcome in! The difficulty level affects how much time you're given, but because we're holding 2 all the way through, it's literally only one frame per level per diffculty step. So to go from 0 to 1 saves 6 frames, etc.
We are in the process of retiming all runs past and present for leaderboard consistency and to include milliseconds owing to the shortness of the game and tightness of the board. Please bear with us while we do this as there are some complications due to different video frame rates. When you submit runs in future please show frame counter if using an emulator. If you have any questions or issues with retiming just let us know, since we want this to be transparent and a one-time edit so that everything is clear for future runs.
I appear to have found a reason for the negative split inconsistency: if I repeatedly press pause on the route select screen it speeds the game loading up. So for clarity's sake we can advise the use of -5.51 still but always time from the first frame the screen fades in. This should not be the first frame Batman moves as it is common for players to deliberately wait until they see/hear the screen for timing purposes. Similarly, any movement or weapon use after killing Penguin can lag the game. So it makes sense to keep the final frame as being loss of control. Since you haven't retimed any runs I propose we use the true vsync so that console runners are not disadvantaged. That is, an emulator run's limits are now defined as: (First frame of screen fade in to Loss of control) / 59.922751013551. For this to work we will need to specify that captures should be 60fps raw where possible. Other communities I am in have at times requested raw video files to be emailed to a mod for this same reason- Youtube outputs only at 30fps so retiming runs from there as the source will be a tad inaccurate and should be avoided in the future, though I propose we retime all existing and obsolete runs to this precision now to be consistent. I'd be happy to do that with your approval. I'm lucky I've encountered precisely this sort of stuff before.
This post was edited to remove faulty information
(Edited to remove faulty info and add new info) We don't have to be super specific as long as we do something consistent. So I'll add in milliseconds for all past runs. Taking Marble Madness as a precedent, some runners lower down choose to add the ms in but most are just marked by a second barrier. It's only in the 2:55- category that all runs are retimed.
Radioactive_Man, when you retime SMS runs for boards you mod, are you just using a video frame counter such as yua, or do you take emu frame count and divide? I've been using n/60 for a long time in games I run, whereas I find info that the SMS frame rate is 59.922751013551. That's a small difference but I would be curious to hear what your experience is so I know whether I should look at migrating to a more correct use. I know many NES and GB communities use absolutely different divisors so this is more a curiosity than anything.
NB on millisecond runs: when you fill in an MS column you must fill it in to 3 decimal places or the site will mistakenly add a 0 in the leading column. I believe then that Sacrieon's run should be filled in as '120' in ms as it currently shows as '012'.
I just looked at the negative split also. I read that timing starts from the frame batman is loaded. When I pressed 1 on frame 1000, Batman appeared at frame 1325 though, and that would correspond to 5.43/4 seconds. Do you have the original source info for the use of 5.51? I figure if we're taking care of the board we can wrap this up all in one go and avoid any future confusion. I also timed out the final hit from penguin (marking the first frame where explosion animation appears on ducky) to loss of control as 223 frames in case this helps anyone for future.
Thanks! I'd be glad to be a mod if you'd like someone to help run the board 👍
This post will be updated as time goes by to show the current standings of the leaderboard for this bounty.
As of 12/7/21 the new run bounty has one leader:
Gustavo_Kennedy 3'20"260
$310 for the next person to break below 3'11, time limit of 310 days. This bounty will end Tuesday 3 May 2022 at 12.30pm BST. Should nobody achieve it in this time, it will roll over to something else in future. From experience, 3'10- is a whole other level to 3'11 so this one has to be properly earned. I'm currently grinding for 3'10 or 3'09 but it won't invalidate the bounty if I get there.
$190 total, for the fastest three new runs, time limit until 1/1/2022 at 12.30pm GMT:
$100 for 1st, $60 for 2nd, $30 for third.
(Edited) This bounty excludes the current top 4* players on the Africa course since the other 2 are already at 3'12. JkL has an old PB well below 3'16 and is grinding the top prize. Any other player is eligible.
Rules:
Play using emulator at 60fps. Console runs a tad slower, so I want to somewhat even out the fairness, though I will still accept and encourage all new runs from consoles outside of bounty. Ideally use Bizhawk or RetroArch. Fusion goes nuts on SHOG, you would be seriously disadvantaging yourself with that. Please use a physical 3/6-button controller if you can. Feel free to stream your attempts, I would love to be around to watch and support you, our little game needs more love stream-wise.
!Other emulators may not be reliably accurate. Please research and ask if in doubt, because if an emulator is significantly slow your run may not count for the bounty.
You can use Rev00 or Rev01. Almost all top runs prefer Rev00 - it has more responsive steering, and an uncapped frame rate, leading to speedups/slowdowns in the course of play - this can be particularly helpful in trafficked sections. By contrast Rev01 has a smoother framerate, but the steering isn't tight so it's better suited for beginning runners.
Unsure which version you have? https://tcrf.net/Super_Hang-On_(Genesis) will explain more.
Use the standard bike, do not use any passwords, savestates, or time hacks. Do your runs on the default normal time and difficulty. All runs will be verified by me then cross-verified, and we have experience of rooting out cheats.
Good luck to all!
Oh I understand, because previously there was a discovered glitch that was also banned. On that basis I'll continue my attempts presuming the clip is valid, but hopefully we will get confirmation soon either way..
