Sonic Xs - March 21, 2023

Edit history:

SDAVerification: 2023-03-21 03:04:51 pm

2023-03-06 12:36:55 am

Game Page: Doesn't exist yet

Sonic Xs () (pc) [Any %] [Single Segment]

Decision: Accept

Congratulations to 'RockoSonicFan'!

Thread title:

SDAVerification

2023-03-06 12:36:55 am

Run Information

Sonic Xs () (pc) [Any %] [Single Segment]

Verification Files

http://v.speeddemosarchive.com/sonicxs-20230305/Sonic%20Xs.mp4

Please refer to the Verification Guidelines before posting.

Please post your opinions about the run and be certain to conclude your post with a verdict (Accept/Reject). If you wish to remain anonymous, you can also send a pm with your reply to 'sdaverification' (please state clearly in that case which run you have verified). This is not a contest where the majority wins - Each verification will be judged on its content.

ktwo

2023-03-06 12:50:35 am

This run is around half a second faster than a previous submission, https://forum.speeddemosarchive.com/post/sonic_xs__november_24_2021.html. The improvement appears to mainly come from a route optimization that was pointed out in the previous verification.

With the current knowledge of the game mechanics and route options, this submission looks in my eyes pretty close to flawless. Oh and the recording is in 30fps this time, so that's a check as well.

Well done, accept!

LotBlind

2023-03-10 01:06:27 pm

Yeah, so I can confirm what ktwo said about the A/V and the route improvement. Also I noticed you get some kind of boost when the robot's green projectile hits you, which obviously saves more time as well.

Can't see obvious ways to make this more than frames faster.

accept

RockoSonicFan

2023-03-10 01:10:01 pm

Thanks, I appreciate your decision. And be on the look out for its spinoff "Shadow Xs" that I'm submitting after the verification due date is reached (due to only 1 submission being allowed per month)

SDAVerification

2023-03-21 03:04:52 pm

Decision posted.

RockoSonicFan

Edit history:

RockoSonicFan: 2023-11-04 10:17:30 am

RockoSonicFan: 2023-11-03 12:45:17 pm

RockoSonicFan: 2023-11-03 12:44:47 pm

RockoSonicFan: 2023-11-03 12:43:23 pm

RockoSonicFan: 2023-11-02 12:14:18 am

RockoSonicFan: 2023-11-02 12:10:53 am

2023-11-02 12:09:53 am

Btw I know it's too late, but I should mention that it's actually 8.233 according to this https://slashinfty.github.io/yt-frame-timer/
Edit: It's actually 8.17. Check post below this please.

RockoSonicFan

Edit history:

RockoSonicFan: 2023-11-04 10:17:15 am

RockoSonicFan: 2023-11-04 05:44:25 am

RockoSonicFan: 2023-11-04 05:39:02 am

RockoSonicFan: 2023-11-04 05:38:41 am

RockoSonicFan: 2023-11-03 02:01:59 pm

RockoSonicFan: 2023-11-03 12:44:37 pm

RockoSonicFan: 2023-11-03 12:43:48 pm

2023-11-03 12:43:16 pm

Btw I know it's too late, but I should mention that it's actually 8.17. The app that gave me this accurate time is the frame by frame google chrome app.

IsraeliRD

2023-11-06 01:25:00 am

Dragon Power Supreme

I used the app and noticed the gamepage player uses 60fps (while the downloadable videos are 29.986fps and verification file I used was 30.01fps).
Nonetheless I still got 8.26 seconds using the app and any of the HQ-XQ files (which were all 29.986fps), so I am leaving this as-is.

RockoSonicFan

2023-11-06 05:28:44 am

Quote from IsraeliRD:

I used the app and noticed the gamepage player uses 60fps (while the downloadable videos are 29.986fps and verification file I used was 30.01fps).
Nonetheless I still got 8.26 seconds using the app and any of the HQ-XQ files (which were all 29.986fps), so I am leaving this as-is.

Using this app? https://chrome.google.com/webstore/detail/frame-by-frame/cclnaabdfgnehogonpeddbgejclcjneh/related
Because that app gave me the same times from Honeycomb Factory Frenzy & Sonica

IsraeliRD

2023-11-06 01:23:46 pm

Dragon Power Supreme

Yes, using this app.

RockoSonicFan

Edit history:

RockoSonicFan: 2023-11-06 02:26:59 pm

2023-11-06 02:26:00 pm

Oh you're counting from the 1st frame to the result screen. Ok this is the proof I got. Giving it a time of 8.23.

Attachments:

Screenshot 2023-11-06 074008.png

Screenshot 2023-11-06 162351.png

RockoSonicFan

2023-11-06 05:17:34 pm

Oh and also this

Attachment:

Screenshot 2023-11-06 191458.png

IsraeliRD

Edit history:

IsraeliRD: 2023-11-07 09:23:06 am

IsraeliRD: 2023-11-07 09:21:34 am

2023-11-07 09:20:45 am

Dragon Power Supreme

You're starting and and ending a frame earlier than I am (I am at 216 to 463 in the verification file), but it still equals the same amount of time that is 15.433 - 7.200 = or 8.233.

However, and this is what you're missing, is that there is an actual gameplay frame not counted in your calculation as you're doing a simple subtraction.

If we were to cut the video to where gameplay starts, it would start at frame 0, or 0.000 seconds, and therefore it would end on frame 247. This gives us 8.233.

However, frame 0 is also an actual gameplay frame, as this is the first frame. This alone is 0.033 (0.03 rounded down). Add it to 8.23, and you get 8.26.

We received other submissions in the past which were frame-perfect and they were timed by both myself and the runners and we matched perfectly (though I do not know their timing methods, their StatID/time identical to the time I received).

I'm adding frames 0 and 247 from yua to demonstrate the example above as to why it's important to add the missing gameplay frame to calculations.

You're starting and and ending a frame earlier than I am (I am at 216 to 463 in the verification file), but it still equals the same amount of time that is 15.433 - 7.200 = or 8.233.

However, and this is what you're missing, is that there is an actual gameplay frame not counted in your calculation as you're doing a simple subtraction.

If we were to cut the video to where gameplay starts, it would start at frame 0, or 0.000 seconds, and therefore it would end on frame 247. This gives us 8.233.

However, frame 0 is also an actual gameplay frame, as this is the first frame. This alone is 0.033 (0.03 rounded down). Add it to 8.23, and you get 8.26.

We received other submissions in the past which were frame-perfect and they were timed by both myself and the runners and we matched perfectly (though I do not know their timing methods, their StatID/time identical to the time I received).

I'm adding frames 0 and 247 from yua to demonstrate the example above as to why it's important to add the missing gameplay frame to calculations.

Attachments:

SonicXs-Frame0.png

SonicXs-Frame247.png

RockoSonicFan

Edit history:

RockoSonicFan: 2023-11-07 01:54:19 pm

2023-11-07 01:53:24 pm

Oh well. Maybe I'm just timing it the wrong way by doing it exactly like speedrun.com times it which actually gives me 8.16 based on glitchbot's former world record run

IsraeliRD

2023-11-08 09:28:45 am

Dragon Power Supreme

speedrun.com's ruleset say from pressing start to hitting the exit door, which is 8.83 (frames 45 to 310) which is what glitchbot wrote. His livesplit timer is technically correct as it is 8.825 for him (3rd decimal not displayed), but it skips frame zero.

On your own video above you posted the screenshots of 7.167 to 15.4 (8.233) at 62 fps(!!!!!), but it should be frame 954 which is one earlier instead of level complete (frame 955), which gives us 8.226.
So for you to even get to 8.16x you'd have to literally remove 4 frames from your own video which is practically impossible unless you are splicing or timing by a completely different ruleset than the rules posted speedrun.com and myself BOTH DO, and that's without even counting frame zero.

And if you do by 30fps, which I already demonstrated above, we get 8.233, so you have to remove 2 frames from the video.

Lastly the pic you posted looks like it has a note from a speedrun.com mod so even the mod himself disagrees with your timing method that claims 8.16, so stop bs'ing around with me and the speedrun.com's mod.

speedrun.com's ruleset say from pressing start to hitting the exit door, which is 8.83 (frames 45 to 310) which is what glitchbot wrote. His livesplit timer is technically correct as it is 8.825 for him (3rd decimal not displayed), but it skips frame zero.

On your own video above you posted the screenshots of 7.167 to 15.4 (8.233) [b]at 62 fps(!!!!!)[/b], but it should be frame 954 which is one earlier instead of level complete (frame 955), which gives us 8.226. 
So for you to even get to 8.16x you'd have to literally remove 4 frames from your own video which is practically impossible unless you are splicing or timing by a completely different ruleset than the rules posted speedrun.com and myself [b]BOTH DO[/b], and that's without even counting frame zero.

And if you do by 30fps, which I already demonstrated above, we get 8.233, so you have to remove 2 frames from the video.

Lastly the pic you posted looks like it has a note from a speedrun.com mod so even the mod himself disagrees with your timing method that claims 8.16, so stop bs'ing around with me and the speedrun.com's mod.

RockoSonicFan

Edit history:

RockoSonicFan: 2023-11-08 03:24:37 pm

RockoSonicFan: 2023-11-08 03:23:24 pm

RockoSonicFan: 2023-11-08 03:10:48 pm

2023-11-08 03:09:07 pm

Quote from IsraeliRD:

speedrun.com's ruleset say from pressing start to hitting the exit door, which is 8.83 (frames 45 to 310) which is what glitchbot wrote. His livesplit timer is technically correct as it is 8.825 for him (3rd decimal not displayed), but it skips frame zero.

On your own video above you posted the screenshots of 7.167 to 15.4 (8.233) at 62 fps(!!!!!), but it should be frame 954 which is one earlier instead of level complete (frame 955), which gives us 8.226.
So for you to even get to 8.16x you'd have to literally remove 4 frames from your own video which is practically impossible unless you are splicing or timing by a completely different ruleset than the rules posted speedrun.com and myself BOTH DO, and that's without even counting frame zero.

And if you do by 30fps, which I already demonstrated above, we get 8.233, so you have to remove 2 frames from the video.

Lastly the pic you posted looks like it has a note from a speedrun.com mod so even the mod himself disagrees with your timing method that claims 8.16, so stop bs'ing around with me and the speedrun.com's mod.

Whoa! Hold on a second! What's with that attitude? That is not the way to talk to a speedrunner who is just realizing their mistake! That behavior is totally uncalled for! Don't ever talk to me like that again otherwise I will report it!

[quote="IsraeliRD"]speedrun.com's ruleset say from pressing start to hitting the exit door, which is 8.83 (frames 45 to 310) which is what glitchbot wrote. His livesplit timer is technically correct as it is 8.825 for him (3rd decimal not displayed), but it skips frame zero.

On your own video above you posted the screenshots of 7.167 to 15.4 (8.233) [b]at 62 fps(!!!!!)[/b], but it should be frame 954 which is one earlier instead of level complete (frame 955), which gives us 8.226. 
So for you to even get to 8.16x you'd have to literally remove 4 frames from your own video which is practically impossible unless you are splicing or timing by a completely different ruleset than the rules posted speedrun.com and myself [b]BOTH DO[/b], and that's without even counting frame zero.

And if you do by 30fps, which I already demonstrated above, we get 8.233, so you have to remove 2 frames from the video.

Lastly the pic you posted looks like it has a note from a speedrun.com mod so even the mod himself disagrees with your timing method that claims 8.16, so stop bs'ing around with me and the speedrun.com's mod.[/quote]
Whoa! Hold on a second! What's with that attitude? That is not the way to talk to a speedrunner who is just realizing their mistake! That behavior is totally uncalled for! Don't ever talk to me like that again otherwise I will report it!

LotBlind

2023-11-08 03:34:40 pm

RockoSonicFan:

Let's make this a learning experience. There's very seldom timing mistakes on SDA because Israeli has a ton of experience with these things. He got upset with you because you were sloppy with your arguments and you hadn't reacted to someone already trying to correct you once before, on speedrun.com, as Israeli pointed out.

I suggest let's stop posting here now.

RockoSonicFan

Edit history:

RockoSonicFan: 2023-11-08 05:59:25 pm

RockoSonicFan: 2023-11-08 05:38:12 pm

RockoSonicFan: 2023-11-08 04:00:45 pm

RockoSonicFan: 2023-11-08 04:00:33 pm

RockoSonicFan: 2023-11-08 04:00:26 pm

RockoSonicFan: 2023-11-08 03:59:43 pm

RockoSonicFan: 2023-11-08 03:58:12 pm

RockoSonicFan: 2023-11-08 03:58:00 pm

RockoSonicFan: 2023-11-08 03:52:37 pm

RockoSonicFan: 2023-11-08 03:52:23 pm

RockoSonicFan: 2023-11-08 03:51:57 pm

RockoSonicFan: 2023-11-08 03:51:42 pm

2023-11-08 03:50:01 pm

Good call on stopping the posts here because that erratic behavior was definitely uncalled for, & I was about to say "with that being said, I understand my mistake and will let it go". but couldn't at the moment because I have a stomach virus. So now I'll stop posting. And I suggest next time to make sure that erratic behavior is checked out because either way, it's not allowed in the site, admin or not. Thank you and good night.