Comments
Colorado Springs, CO, USAKally6 months ago

hey

SuperGamer64 likes this
Colorado Springs, CO, USAKally8 months ago

hey

Colorado Springs, CO, USAKally11 months ago

hey

YUMmy_Bacon5, Gaming_64 and 4 others like this
Colorado Springs, CO, USAKally1 year ago

hey

YUMmy_Bacon5, Gaming_64 and 6 others like this
Colorado Springs, CO, USAKally1 year ago

hey

YUMmy_Bacon5, Gaming_64 and 3 others like this
Colorado Springs, CO, USAKally1 year ago

hey

YUMmy_Bacon5, Gaming_64 and 4 others like this
Colorado Springs, CO, USAKally1 year ago

hello mario

Gravydos and hector like this
Colorado Springs, CO, USAKally1 year ago

hey

YUMmy_Bacon5, grnts and 6 others like this
Colorado Springs, CO, USAKally1 year ago

hey

YUMmy_Bacon5, Gaming_64 and 7 others like this
Colorado Springs, CO, USAKally1 year ago

hey

wRadion, YUMmy_Bacon5 and 6 others like this
Colorado Springs, CO, USAKally1 year ago

hey

kcaj, Axtelip and 62 others like this
Colorado Springs, CO, USAKally2 years ago

This was a lot of fun when starting from a file.

SaySurprise, fazerlazer80 and 2 others like this
thread: Speedrunning
Colorado Springs, CO, USAKally2 years ago

UPDATE: This post has been made largely irrelevant with this: https://github.com/thags15/LiveSplit.TheoryComparisonGenerator

If you don't care about changing values, I 100% recommend using this instead.

Original post:

Hello! This is my guide on how to create a true balanced comparison for LiveSplit. If you prefer a video walk through, one will be linked at the bottom. What is a true balanced comparison? A true balanced comparison (which will be referred to as TBC from now on) is a comparison that evenly distributes time save across the run based on the percent difference from your sum of best and either your PB or a goal time. Why would you want to use this if there already is a balanced comparison in LiveSplit? LiveSplit’s balanced comparison is weighted, taking into account past runs instead of being a simple % calculation. This can be good for splits that you are super consistent with, as it will try to move that time save elsewhere. However, the time save for each split can vary greatly from run to run as you feed it more information, and in my experience, doesn’t balance timesave enough. This is where TBC comes into play. This comparison has a more consistent amount of time save per split, and has the benefit of allowing you to create a goal time. This used to be a manual process, and if you are someone like me with a ton of splits (104!), this takes a long time and isn’t easy to update. I talked to Amitheous, a member in the SM64 community, and they believed they could automate the most tedious part by using Google Sheets. A couple hours later, they messaged me a sheet, so let me explain how it works.

First, open up the sheet, which can be found here: https://docs.google.com/spreadsheets/d/1C74b-OSHcgHPdxge1D4xqt7a4Wy5eYHsmBZ2FHgdqrY/edit#gid=0 Go to File, and click “Make a Copy” Name it whatever you want. Next, go to LiveSplit and edit splits. Click and drag from the first split name, down to the bottom right so you have the final best time highlighted. Control+C to copy, and go back to the spreadsheet. Click on Column A, Row 2 and Control+V to paste. Now, go to Tools, Macros, and click “Calculate Ideal PB” You may need to do this a few times. Most people get an error on the first attempt, the second attempt asks you to accept permissions (accept them), and the third attempt is what works. You now have the column “Ideal Segment” filled in along with an “Ideal Run”. By default this is 5% off your gold splits. You can click on the percent column and change it to whatever you like, as long as you keep the % sign. Decimals work too, but the sheet shows them as a rounded number. To apply this to each row, click and drag the blue box on the top box downwards to the bottom. To calculate a specific time, go to https://rechneronline.de/add-time/time-percentage.php and in time 1 put your goal time and in time 2 put your sum of best. You will get a number above 100%, drop the first two digits and that is the number you want to punch in the sheet. For example, if the number I got back is 104.66%, I would put in 4.66%. In order to create a comparison, go back to LiveSplit and click “Save Splits As” and name it whatever you want. You now have two identical splits files, but this one we will make our comparison. Edit splits, click “Other” in the bottom right, and select “Clear Times.” Go back to your sheet, and highlight the “Ideal Segment” column, starting from the second row. (You do not want “Ideal Segment” highlighted.) Control+C to copy, go back to LiveSplit, click the first box for “Segment Time” and Control+V to paste. Click “OK” and save the file. Open up your normal splits file, and edit splits. In the bottom left, click “Import Comparison” then click “From File.” Name the comparison whatever you want, and click “OK”. You now can compare against these splits. If you want to always have a comparison, edit your layout and add a Delta. Change the comparison to your new comparison, and you are finished! This guide was pretty rushed, so I’m sorry if it didn’t make much sense. If you are lost, I recommend watching this video I quickly made where I walk through everything: If you still are confused, leave a message and I’ll try to help, but please watch the video first!

LexFL_, FlamingLazer and 14 others like this
Colorado Springs, CO, USAKally3 years ago

I've been told that runs aren't being rejected for this reason anymore. (Not because of this post)

Colorado Springs, CO, USAKally3 years ago

Currently, retiming and verification looks for the first frame of the Super Mario 64 logo and assigns that value "1.33". Said frame is here: https://i.imgur.com/fJ5AMWN.png

I propose that the timing be changed to a later part of the title sequence, potentially this frame: https://i.imgur.com/f5AmB0i.png

You can see the selection in timing in the bottom right. From the first frame to the frame I propose a time of 4.634 seconds elapses. By adding the 1.33 we currently use, that would give a start time of 5.964. This should be double checked if this change actually will take effect.

Why change this? Currently, a lot more players are starting to use HDMI capture cards and more advanced setups. Many of these setups take too long to get the signal. I have had a run rejected before due to it not grabbing the signal fast enough, but luckily on my setup that only happens on the US version of the game. Some people aren't so lucky, and this happens on both US and JPN. Here is a video of me explaining my setup:

I'm not sure what the slowest capture card is. That would require some community feedback. The frame I chose is purely based on it being easily identifiable, being much later than the SM64 logo, and being before a user can input Start. Leaderboard times will all stay the same, but more people can submit runs and more setups can be used.

dbot, Ivory, and CurryInTheHouse like this
Colorado Springs, CO, USAKally4 years ago

Got it. Thanks for the information!

KilleDragon likes this
Colorado Springs, CO, USAKally4 years ago

Dragorn's is. Wondering why spiderman88mil's isn't.

I want to see that sweet sweet 15 years ago.

KilleDragon likes this
About Kally
Joined
4 years ago
Online
today
Runs
237
Games run
Super Mario 64
Super Mario 64
Last run 12 days ago
203
Runs
Super Mario 64 Category Extensions
20
Runs
Sonic Adventure 2: Battle
Sonic Adventure 2: Battle
Last run 2 years ago
4
Runs
Super Mario 64 Online
Super Mario 64 Online
Last run 2 years ago
4
Runs
Super Mario 64 Co-Op (PC)
Super Mario 64 Co-Op (PC)
Last run 1 year ago
3
Runs
Minecraft: Java Edition
Minecraft: Java Edition
Last run 3 years ago
2
Runs
Forza Horizon 5
Forza Horizon 5
Last run 1 year ago
1
Run