![]() However, your splits will still be corrupted under the hood, which will show when you upload them to Splits.io or otherwise perform analysis on them or share them with others. This will force LiveSplit to stop being clever and actually just sum your bests to get a sum-of-best time. To work around this issue without damaging your splits (but also without repairing them), go into LiveSplit's settings and check "simple sum of best". ![]() There's one workaround to this, one fix, and one way to avoid it in the future. In this corrupted map of routes, A -> D -> C will always be faster than A -> D -> E -> C, so LiveSplit will build its sum-of-best based on the sum of those segments' gold times, even though that's not a real route through the game. A -> D -> E -> Cīecause you've only renamed B (rather than deleting it) and changed what it actually means to complete it in-game, LiveSplit now holds a corrupted network of the possible paths through the game: A -> D -> C Being a reasonable person, you might just add a new split between B and C, then rename B. Now, here's where the bug comes up! Let's say again you have a run that looks like this: A -> B -> CĪnd let's say again that a new route is discovered and it's time to update your splits. If your gold time for B is faster than the sum of your D and E gold times, then A -> B -> C is still your fastest route, and so your sum-of-best is still the sum of their gold times, even after you've switched routes. Internally, LiveSplit remembers your splits more like this: A -> B -> Cīecause it remembers your gold time for B, your sum-of-best will actually not change when you update your route! As odd as it may sound, your sum-of-best is defined as the shortest path through this network of splits. So instead of just adding up all your gold times, LiveSplit keeps track of your route changes. With the simple way of calculating sum of best, your sum-of-best suffers as well! But LiveSplit realizes this and tries to give you what you might actually be wanting from a sum-of-best: the answer to the question "What's my fastest possible run?". A -> D -> E -> Cīecause it's a new route, you're not great at D and E yet! The route is strictly better, but your time actually suffers while you grind attempts. Let's say a new route is discovered that foregoes B, so you update your splits to accomodate. ![]() When LiveSplit calculates your sum of best, it's actually not a literal sum of your best segments! Take this run: A -> B -> C This is a really interesting bug! If you don't care about why it happens, just scroll to the bottom. ![]()
0 Comments
Leave a Reply. |