I did a run of this, and the final time was 903 seconds, but I'm not sure if that's the actual timing method used in this game. Did I get a 15:03 or did I get a 14:5x?

Huge world records in Red Ball and Red Ball 4 on the same day??

I can only imagine the intensity felt when retiming this run

Bopped eg by a single frame, nice

And don't worry, I can't do sub 20 either

It's basically a patch that makes the games tweener scroll at exactly 31 frames per second instead of averaging 31 fps, making spike glitch far more consistent and makes the game a lot smoother to play in general

This makes total sense. People with slower computers are at a disadvantage with laggier games and more inconsistent frame rates, and this would fix that.

My 3:18 literally used strats seen in an 0x. That's how bad I am at this game lol

Also, it's the jump onto the ridge between the carts that's frame perfect? I thought it was the falling jump into the cart. This probably explains why pbird train's been so inconsistent for me

Red Ball

ROBLOX: Speed Run 4

Red Ball 4 Vol.1

These two tutorials are currently the best resources available for learning the game:

Red Ball Beginner Speedrun Tutorial by Maximum - https://youtu.be/GLFv9uJWD6g
Red Ball 2x/1x/0x/sub 3 Tutorial by Caramel - https://youtu.be/jGcUR6vkBfA

We are hoping to eventually make a new high-level tutorial at some point to cover the many new discoveries that have been made since it was created. We also hope to eventually translate our resources into other languages as well.

Red Ball Speedrun Tutorials

Update: Voting has now closed, with a 95-11 vote in favor of allowing a deterministic patch.

We have decided to hold a formal vote for Red Ball 1 speedrunners ONLY. This vote is to determine whether a slight modification to the game's tweener should be allowed in speedruns. The tweener is responsible for scrolling the screen as Red Ball moves around a level. The tweener scrolls more or less depending on how long it takes for the game to render each frame, something that varies significantly and is impossible to control. Scrolling variance causes spike glitch to not be deterministic, meaning that a certain set of inputs will yield different results if tested repeatedly. Lower spec computers have a less stable framerate than higher end machines, making spike glitch consistency worse on slower computers. Additionally, monitor refresh rate has been found to play a role, with people having a distinct advantage if they are able to set their monitor refresh rate to an integer multiple of 31 FPS. Both of these factors have caused a distinct accessibility issue, putting certain runners at distinct advantages over others based on their hardware. By setting the tweener to scroll based off of fixed 31 FPS frame timing, something which requires a one line code addition, spike glitch becomes completely deterministic, eliminating this accessibility gap. This also prevents the screen from jittering constantly, something which is very visible at high speeds. Deterministic spike glitch causes all jumps in spikes to be significantly more consistent, and it will allow players using lower resolution monitors to have a more fair chance to compete with 1080p+ runners.
On the flip side, this is still an unintended game modification, and there are absolutely valid reason to be against this change, which is why we have put it up to a community vote. 

Check out this segment of the TAS explained video for more information about the proposed modification, which is already present in the TAS hack of the game: https://youtu.be/07NVysUGjhk?t=924

https://forms.gle/pC4QvxZBXjGDpoZv5

Voting will end at the end of the day (ET) on November 4th (Thursday)