What's going on with that video? It has a lot of jumping around about 6:40 into it where levels could have easily been skipped and it seems like deaths happened at some point but it's impossible to tell.

It doesn't seem right that a run can be submitted with a video that is impossible to verify with.

I will check it out...

I remember this run, I did have an issue with it as well. The visual glitching is too weird at the end to ignore.....

https://www.speedrun.com/run/y971432m

but do we honestly believe snowi cheated the run? snowi is well known within ballrace community very talented player. I doubt he cheated it. are there other visual glitches besides the very ending?

well, it's not a matter of thinking he cheated or not. it's just a matter of following standards. he could have cheated, and that's all that matters when it comes to verifying a run isn't it?

I think you are right. I think the standard should be you have to fully prove you did the run, this visual glitch is atrocious - and without the reputation of snowi would not have been accepted.

Are there any objections to clarifying this in the rules that there needs to be clear continuous video evidence of the full run and rejecting this prism run?

Although Snowi is a trusted user and I think it is highly unlikely he would splice a run, (especially this close to the end), I don't think the video meets the standards of the proof we require.

I'd like some more time to think about this; at this point it is likely the time will be removed unless Snowi can produce a video without the choppiness.

well, currently no but this could something that incites a rule review. grandfathering the run could a thing but it isn't advised because, as mentioned, the run shouldn't have been accepted

I recall Newbrict alerting me of this when it was first submitted, though I told him to act accordingly and never reviewed it myself.

It is likely we will henceforth enforce stricter proof standards for submitted Ball Race speedruns.

and also, on the subject of rule reviews: is it mentioned anywhere on the rules that you gotta play alone? the current rules don't say anything regarding playing with other people on the server. and in that case, on levels with buttons, you could have someone else press the button for you or have someone end a level late to manipulate cycles (when cycles matter)

I will have the rules updated to specify this.

This may call for the addition of "Singleplayer" and "Multiplayer" subcategories. Could result in some interesting runs.

I mean, it would only cut some pathing for certain levels, as there is no other sort of player interaction. I don't think it's particularly interesting to add a Multiplayer subcategory (imo).

My personal view on rules:

• must be played alone

because otherwise you can manipulate the timings by having your buddy take longer than you - along with obviously completing parts of the map for you.

• must provide clear video evidence of the run

obviously no other way to verify a run. I think audio is a plus but can't be required because no one wants to listen to the ballrace soundtrack over and over.

• timer starts from the first try on the first level

this needs to be proven on video as well, you can manipulate the timings on level one by dying before attempting and then starting your video after you spawn for second try. this cannot be allowed.

I am not sure on frame limiting, will have to speak with devs to see if they have a client/server fixed movement change coming eventually, otherwise it gets really hairy...

I concur with all of these suggestions. Could you please update the rules to include these specifications?

We've been messing with framerate for certain things, specially the Summit level 9 boost. I don't think that that's really something that we should be too concerned about. At least, speaking from experience with other games that have FPS-related tricks, I think it's fine to have it as it is.

summit level 9 boost you don't have to mess with frames, you just need to practice it... my run does it no frame tricks.

BTW - all rules are now updated.

well, not that you need to mess with framerate, but having a very high framerate helps, according to Master

Yeah, I wasn't really accusing him of cheating. It's simply that all runs, regardless of who it is submitting them, should be held to the same submission standards, and any other person submitting would most certainly not have a video like that verified. I get a bit bothered when mods accept their own runs with problems like that just because they can, I was involved in another leaderboard a while back that had the same issue where mods were accepting their own runs without video proof even though it was a requirement. Yikes!

Anyway, good job to the mods in this thread and in fixing up the rules!

On to the conversation of launches that just spurred up...

I'll be referring to getting stuck between a moving platform and a wall to get launched as "stucklaunch(ing)" because I used to run Marble Blast Ultra way back in the day and it had an identical trick by that name. Good times...

I was doing Summit runs for a while yesterday and for the life of me could not get a powerful enough stucklaunch on level 9 first try. I looked into it deeper after eventually giving up for the day and figured out some pretty depressing things...

First, the FPS definitely seems to influence the strength of the launch. I go flying every time on 240+, with 100 or more FPS lower it is considerably less the majority of the time. Now we hit the real problem, the game has some sort of FPS capping bug?? I noticed that much of the time my FPS was seemingly capped around 142 while I was using input, and I could never get the stucklaunch to be powerful enough while it is like this. It randomly uncaps back to a proper 200+ when it feels like it and the launches were fantastic then. What in the world is causing that? I tried a lot of things, messing with Nvidia Control Panel settings, tweaking the in-game graphical settings every which way, nothing seemed to influence it. I did think today to change my refresh rate (I'm on 144hz) since it's suspiciously close to where the game is capping itself, just haven't gotten to it yet. No idea what else to try if that doesn't work, and I'm going to give up on doing the stucklaunch in runs because of this because I really don't feel like rolling for framerate RNG...

EDIT: I tried a 60hz refresh rate and it didn't change a thing. :(

I played vsync at 144hz for my stucklaunch lvl 9

hi , sorry for the crappy footage shadowplay doesnt like me recording for long times and it freezes near the end almost every time :s . i can assure you that it wasnt cheated and i have no interest in cheating and ill make sure to record with something else on prism next time. i did ask jezs about it at the time and he seemed to think it was ok but i understand if you guys want to remove it now. I actually got a much better time on this before but my hard drive was full so rip that.

as for fps related inconsistancies, one thing i've noticed is with extremely low framerates some positions get skipped and you can teleport past thin triggers like in khromidro level 2. also some moving platforms can be launched off with sudden fps drops or freezes just spam switch between fullscreen and windowed to see some of these effects. oh and the strength of grabbers and pushers definetly changes based on framerate. when compairing 60fps to 60-200fps i havnt been able to find any differences though.

any suggestions on what i can record with that wont give me fps drops?