Retiming Announcement
7 years ago
North Rhine-Westphalia, Germany

There have been a few runs of the Any% category in this hack lately, i noticed that there were a few runs that seemingly aren't timed as properly as they should be. Until today there weren't really retiming for the runs. This category has pretty low differences between all the runs, mostly only a few frames so it's quite necessary to have exact timings. Therefore moderators will probably retime more runs in the future so don't be afraid if someones time will change and he eventually loses/wins a few positions on the leaderboard.

Now RaveTuba made a compilation () of almost all the current PBs and retimed them. I've decided to replace the current timings with his ones. The reason for that is that the leaderboard isn't really accurate at all atm and that the retimings look quite accurate.

Also there will now be exact timing rules: The timing will start from the frame where the black star cut-out leaves the screen and it will end on the frame where mario touches the "finish-line". Please try to pay attention to that as much as possible.

Also some people are probably wondering why RaveTuba's time got accepted although he used Mupen which is an emulator that is mainly used for TASes. However, if someone uses Mupen it doesn't directly mean that the run is a TAS. Furthermore the rom hacks don't have real rules considering which emulator people have to use. It is more tolerant for rom hacks as for the original SM64. You could say that people are free to use the emulator they want to use which basically also includes Mupen. And since we couldn't undoubtly say it's a TAS the decision is: When in doubt, for the accused.

But always keep in mind that this isn't final at all, the timing + the validity of a run can still change from time to time.

You may post critical comments to this post, i know that some of these decisions are surely questionable.

編集者 投稿者 7 years ago
Portugal

Hi there,

I'm very thankfull for the anoucement that was made on this speedrunning category, considering the attention it has got was due to the video I have uploaded,

As an added effort, on the next available afternoon, I'll double check that the timing of the runs that I ran on the beforementioned video are acurate, one by one rather then all at the same time, as, considering the current change on the leaderboards, I apologise if truly the timing on the runs is way off and lead to some incorrect positioning.

I also take this chance to apologise for not knowing that the Emulator "Mupen" was mainly used for TASes, I strugled to make the ROM work as I could only find one sorce online that permited it's download, and even though I've tried both "1964" and "Project64" emulators, they both refused to run the ROM.

I could just barely make Mupen work as well, as everytime I failed the run, I'd have to cancel the emulation and start again, the sound output had no configuration and constantly it would say that I didn't have a joystick connected, when I configured it to my keyboard.

Though, I'm perfectly willing to have my run taken down for fair reasons if you'd see fit; and I'd try to have the ROM run on a diferent emulator so to recreate my time. But, if need be as well, I have several recordings of all my attempts to finish the run, if required any sort of proof that the run wasn't TASed I can surely upload them to youtube to verify my run.

Once again, thank you for your time If any further mention is needed from my end, feel free to reach me over Discord, I'm more active there.

RaveTuba

North Rhine-Westphalia, Germany

I think i know why the ROM only opened with Mupen... For other emulators you need to change the settings, i'd recommend to use Project64 1.6, there you need to go to: Options > Settings > Options > Deactivate "Hide Advanced Settings". Then go to Advanced and set the "Default Memory Size" to 8 MB (i think that's how you do it). PJ64 1.6 is an easy-to-use emulator all in all.

Tobür これを好き
Portugal

Hey guys,

I just wanted to mention that I finished reviewing all the runs that are on the leaderboards, I made sure the timer started on each of the videos on the exact frame the cut-out disapears, and to each video made sure the timer stoped on the frame where mario changes his animation from "airborn" to "grounded" when landing on the finish line.

I have uploaded the video with all the runs in a row (from longest run to shortest) here:

And if it is accepted, all the runs (as of 10th October 2016) would be as follow:

1st - Tobür - 34.200s 2nd - EduDragneel - 34.680s 3rd - Luvbaseball - 34.840s 4th - EaBTasRaiul - 34.870s 5th - FrostyZako - 35.100s 6th - defqon_Jan - 35.140s 7th - marvjungs - 35.280s 8th - SchokoBrother - 35.340s 9th - GalladeGallaxy - 35.280s 10th - PinkesPichu - 35.340s 11th - NB's Lets Play - 35.490s 12th - AlphaWario - 35.550s

Feel free to contact me if there's anything that feels wrong or if there's anything that IS wrong. (I swear, I've triple checked everything up to this point)

編集者 投稿者 5 years ago
Melwing17 これを好き
ゲームスタッツ
フォロワー
43
走行
66
プレイヤー
35
最新スレッド
投稿日 6 years ago
5 返信
投稿日 7 years ago
3 返信