Try deactivating, and re-activating the load remover in "edit splits" tab. This seems to be a somewhat common problem, as it has happened to me and probably some others. You can also check that the directory for the load remover plugin is correct, by pressing the "settings" button in the "edit splits" tab (it should be in a directory like LiveSplit_1.6.9\Components\LiveSplit.Fallout4.asl, and should be the same directory as the livesplit .exe is in).
In the game folder you can see what date the file or files in the folders was edited.
Not really related to this, but I tested if the loading screens vary, comparing my 22.290 and StarSmiley's 22.340 I can honestly say that there is pretty much no difference. Errors in timing is like 10x more significant than this. It seems many of the runs are incorrectly timed, and too be honest StarSmiley's 22.340 looks faster than my .290 but I haven't checked too much in depth.
I had this happen to me before on another game (Fallout 4). When you have your split open, press on edit splits. When you see the "load remover is enabled" press settings right next to it. Check that the directory for the load remover is correct, and that the file names are correct. (for me it was LiveSplit.Fallout4.asl). This happened when I reinstalled windows and had livesplit backed up. What I reccomend you to do is to find out if you have a load remover file inside the "Components" folder, if so delete it. If not, try to deactivate the load remover and reactivate it. If it doesnt work, you might have to try to remake the splits.
I have a pretty good PC, and I get stuck on the stairs, or something else most runs. Very rarely I get a run that is flawless, which is what it takes to pb.
So if my run is going to get retimed, can you tell me how to properly time my runs then?
Is there some rules as to what frame counts as the end screen? Or is it the first frame that you can start seeing the end screen?
not really a huge timesaver, but might be something someone would want to know.
So it seems like the vote for 100th seconds is winning, are you gonna implement it soon?
I have one hand at the arrow keys, and the other at WASD. It works pretty well to spam w and up. If you use both hands, try to spam it somehow even, if two of the inputs are too close to each other, one of them might not register and will cause you to fail.
When you are standing under magnets, press down arrow or I believe B and you will kinda get pulled slowly towards the magnets. Combining the magnet with jump can save a significant amount of time.
For the WR, if it becomes really close, they should consider getting the most accurate time by counting the frames in i.e. vegas, since there is not autosplitter, and it's really hard to split perfect.
Well, I have found that the game stores its save in C:\Users\¤username¤\AppData\Local\You_Have_10_Secondsfinal, as a file named game.ini. Deleting that file will reset the saves. Will this be allowed for runs? I don't see why not..
Is there any way to reset the progress to start a new game, without having to complete all 4 areas?
a bit faster shopping (dunno if anyone has found it before)
Try verify integrity of game cache, and then downpatch again. Sometimes the game can bug out from the downpatcher.
When you're inside the railroad and are running back to Tinker Tom after making the door save, when you activate the "Solve for N" line (you have to be close to Tinker Tom for it to activate) you can instantly load warp away. The quest will update when you load in after the load warp. I'm pretty certain it's skipping dialogue with loading zone (I believe it's used in Skyrim), so it can potentially work in other places of the run. Here it saves about 10 seconds. So in short: You don't need to wait for the quest update, as long as you trigger the "Solve for N" line, after which you can load warp away, or go through a door and get the quest update instantly.
Anything special written in the cmd window when downpatching? Maybe it's something wrong with the copy of downpatcher you have. I believe if the Fallout 4.exe doesnt downpatch it will still say 1.6.9. You can also try using the 1.1.30 file backup, which will work if there is a problem with the downpatcher.
Many of the glitches we use only work on pre 1.2 patch, so a run on current patch would be 1hour 30minutes probably.