Virginia, USAI have yet to see video evidence of Nitro clip being done on the current patch, and several runners on the discord (including myself) tested it and were not able to do it. That, along with how they changed the way those specific nitros explode, and the removal of a lot of the times from the board, lead me to believe it was patched out.
If proof of it being possible on current patch comes to light, we will probably allow it again.
We are still figuring out the specifics but appears that PC overall is faster by a significant amount.
The only thing we have straight up banned is the Nitro Clip in Hot Coco, since several pieces of evidence confirm that it has been patched out. Obviously if someone discovers it the current version then it would be allowed again.
Hog Ride is a tricky one because at the current time we don’t have enough evidence to confirm nor deny whether it was patched out. It’s a tough call to say whether to allow it.
You are more than welcome do such a run yourself, but it will more than likely not be added to the leaderboards, even as a miscellaneous category.
Hey all,
As I stated in the New Rules Update post, LiveSplit running the loadless timer must now be visible in all submissions to be accepted.
There are a couple reasons we have done this:
-
PS4 direct streaming; several runs that have been recorded with PS4 direct stream have been submitted that frequently are missing footage due to video skipping. This has ranged anywhere from a few seconds to minutes of footage missing. We have been lenient on this before but it has gotten out of hand. It is not necessarily the fault of the runners as much as it is the fault of PS4 streaming being terrible, but we simply cannot verify these runs in good faith when so much footage is missing. It is unfortunate that PS4 direct streamers suffer by their runs not being valid from a direct stream, but they likely would have been rejected anyway solely out of the footage that was missing.
-
We have also had many instances of people submitting runs that have not had loadless timing accurately timed, and then requesting that we check the time is accurate for them. Again, we have been lenient on this, but it has also gotten out of hand. It is not the job of the moderators to time your runs for you. We are just here to make sure nothing goes out of order and to make sure submitted runs are valid and not cheated or spliced in any way. Making sure your times are accurate is the job of the submitter, not the moderators.
We understand that this will make submissions a little harder, but we have standards that we go by, and we want to make sure runs are of the proper quality when submitted. LiveSplit and the load remover are both very easy to set up, and any questions and problems that you have can be solved by asking on here or in the community Discord: many people are willing to help you get everything set up to make everything easier.
With that, I hope you all continue to do runs of NST! Hope to see submissions soon.
~Riko
As the new rules now require LiveSplit with the loadless timer to be visible, these spreadsheets are no longer viable for use.
Hey all. In light of the multiplatform release and update to NST, we have made a large number of changes to the rules that I will mention here:
-108% has been added to Crash 3 as the new full completion category. This category does include Future Tense.
-Crash 1 102% and 312% have been completely removed, and Crash 3 105% is currently archived. Crash 1 102% was a very unpopular category, and with Stormy Ascent now being free to download (or available from the start on non-PS4), the category was deemed unnecessary. Likewise, Crash 3 105% has actually been made impossible with the update including Future Tense, and as such can no longer be run. The category will remain as a reference point until a sufficient amount of 108% runs that properly show off the capabilities of the category have been submitted and verified, at which point the category will be removed. The elimination of 105% also made 312% impossible; however, because it is a misc. category comprised of three other categories, archiving 312% was deemed unnecessary.
-An FPS cap of 60 for PC runners has been implemented. This is because that’s how much the game is natively meant to support, and the game actually can run faster if FPS goes above 60. As such, exceeding the FPS cap is banned - this is enforced by having an FPS counter displayed at all times (for example the Steam internal one; for more information on that check the actual rules and the embedded links) for any PC runs.
-Expanding off of the above point, we have added Individual Level (IL) Leaderboards. The FPS thing has appeared to screw over the official Crash leaderboards, so for the sake of accuracy we have chosen to start up our own, as IL runs of NST have proven quite popular.
-And finally, all submitted full game runs must now have LiveSplit running the loadless timer visible on screen at all times. Failure to do this will result in the submission being rejected. I will create a separate forum post going into detail later about why we did this, but it is to address concerns involving PS4 direct streamed submissions missing video footage, as well as the laziness on part of some submitters who expected us to time their runs for them.
I know this is a lot to take in, but we believe all the changes will benefit NST as a whole, and none of these decisions were made lightly. Be sure to read up on everything before submitting runs, and I hope you all have fun with the new update and multiplatform release!
~Riko
Pete’s response was blunt, and because of that it is easy for it to come off as rude, especially on the Internet where it is occasionally hard to read tone.
To me it didn’t seem like you were upset. I just wanted to clarify what Pete meant.
It is literally in the category rules though. As in on the leaderboard you click “View Rules,” and near the bottom it has a link to the list of accepted emulators.
Before ever submitting a run, even your first one, it is a good idea to be completely acquainted with the rules of the game/category. If you don’t, it is ultimately not our fault if the run gets rejected for breaking one.
Yeah, as far as I know this is only for LiveSplit.
Recently there have been a large amount of submission with videos that are not cropped to only include the run itself. The result is videos containing several failed attempts as well as the run in question.
We have been rather lenient on this, and simply have been giving out warnings to either timestamp the run start, or to simply crop it next time. But this has gotten out of hand. Several submissions have videos where the run doesn't start until over 20 minutes in!
This is ridiculous; both YouTube and Twitch have tools that let you edit videos to crop out unnecessary footage. There is no reason that videos with so much extra fluff are being submitted; it is a nuisance for both the mods verifying the runs and any viewers who wish to watch it.
From now on, if a submission does not have a properly cropped video (i.e. the run starts no more than a few minutes into the video, and there is no more than a few minutes of extra footage after the run completes), the run will be rejected. The rules have been updated to reflect this.
Crop your videos.
~Riko
I'm not sure if the Crash 1 runners have implemented it, but in my experience it is hard to pull off consistently.
Note, as the OP now states, a load remover has been created that is way more accurate than these spreadsheets. As such, I would no longer recommend using these spreadsheets if you can help it. I will be locking this thread for now.
EDIT: Here is a video tutorial on how to set up the load remover: https://www.speedrun.com/crashnst/guide/6lita (This does NOT include the "Remove Transitions"-step as it was made before the update; for more on this check below)
A load remover tool for LiveSplit has been developed by Thomadin. Using it allows the timer to freeze during Load Screens if you are comparing to Game Time as opposed to Real Time. It takes a bit of working with to get running, but it is completely functional and extremely accurate, so I would recommend all runners use it. It is also being continuously updated.
Link: https://github.com/thomasneff/LiveSplit.CrashNSTLoadRemoval/releases
Here are some instructions:
"How to use: Put the LiveSplit.CrashNSTLoadRemoval.dll inside your LiveSplit/Components folder. Add it by going into your Layout Editor -> Add -> Control -> CrashNSTLoadRemoval. In the component settings you can specify the capture source (either any full Display or specific windows) and capture region (by left/right clicking the preview). In order to work correctly, the capture region should not be changed a lot in aspect ratio - try to keep your Crash NST video footage in 16:9. It might work for stretched/distorted aspect ratios, but the tool was designed for 16:9 footage. Also enable the checkbox "Remove Transitions" above the preview window!
You can use the capture preview to make sure the Component is capturing correctly - if you are capturing off of a GPU window (e.g. DirectX/GL...) it'll probably not work and just show a black preview - there's nothing I can do about that. You can, however, just capture from the OBS preview (by setting the capture region to the Crash NST footage inside the OBS preview), PS4 remote play, or full display instead.
Since the loads are removed, you can now use "GameTime" in your Splits/Timer/whatever (Rightclick on Livesplit > Compare Against > Game Time), as the GameTime timer is simply stopped during loading.
I have not tested any language besides english, so it might work, it might also not. We can work on that, if necessary. Also the LiveSplit auto-updates are broken for this component and I don't know why, so if any updates are released you'll have to download them manually for now."
Enjoy, everyone! This will make loadless timing far more accurate!
The spreadsheet for PS4 Slim has been completed by Crodi (aside from Full trilogy).
No, best option is to rewatch the video and time every load that way then add it all up.
Yeah Crash 1 is different, and unfortunately we don't have a time for that yet. However, you can see what the load times are for other Slim runs and use that as a reference. Load times are pretty consistent so it should be the same time for you.
EDIT: Nvm it doesn't look like any Slim runs are on the Crash 1 Any% boards yet (I'm on mobile though so I can't entirely tell for certain). For now you might have to manually time the loads.
I'm assuming you are submitting Crash 3 Any%? In this case, yes you would subtract 13:14 (though also be sure to account for the decimal as well, could make the difference of a second). Slim spreadsheet is still a WIP but thankfully the Crash 3 portion of it seems set.
Always happy to help. :D
