This came up a while ago when Trob ran on keyboard and mouse. As far as we know, there isn't a way to speed up the animation without a controller, so unfortunately playing on K&M will put you at a disadvantage.

Make sure to change your timing method to Game Time if you haven’t.

Like Cameron said, if you record the run and then play it back with the load remover running and record it again, you should be good to go. Shouldn’t put too much strain on any computer to do that.

Hey all,

Below is a permanent invite link to an NST-specific Discord Server that we have created. We are hoping that this server will be a great resource for all new and veteran runners to learn the games and grow the NST community. I hope to see you there!

https://discord.gg/aGjpE6e

IGT shouldn't be any different between consoles, so you should be fine.

Likewise when the load remover is completed, ideally there should again be little to no disadvantages.

I feel like the way to circumvent this would be completely resetting the game, which seems like a big hassle for what probably amounts to a second at most.

This is being discussed in the discord as a potential miscellaneous category, and considering how many people like the idea it will likely become a thing at some point.

We aren't against having modded runs as miscellaneous categories, especially if they're something that many would like to run. It's just that these things shouldn't be main categories.

Yeah that's come up a few times. I dunno exact specifics but I think it has to do with the slide ending right as you transition from normal ground to ice.

I think it might also be faster but I don't know that for certain.

"I'm not sure why you're posting here."

Because you were intelligent enough to warn me that you were gonna post here lol.

I'm not obligated to continue a conversation that everyone besides you wanted to end.

Alright, since we're gonna play this game:

https://www.speedrun.com/crashnst/thread/o89oe/1#j590s <--- My post, explaining why things are capped, 10 days ago

https://www.speedrun.com/crashnst/thread/sfn13/1#2gqtn <--- "There was a reason, you just chose to ignore it", 1 hour ago.

Oh yeah, I didn't explain at all. Actually you just chose not to read.

Also, of the three posts I deleted, two of them were, "You can delete my post but you can't deny the truth," and, "This abuse of power has been brought up with the moderators," neither of which are productive. And the last one was a post pertaining to the discussion that was already over.

There's no abuse of power; there's just you being a whiny baby because the way we moderate a game (that you don't play) isn't the way that you want it to be moderated.

You've missed nothing, that's exactly what's going on. We have explained things thoroughly and he refuses to listen. I'm deleting his posts because we're all tired of seeing them and the discussion is beyond over, though he insists on continuing it.

If anything he should be banned from posting in that forum (if at all possible, I'm aware it's not a power that the leaderboard mods have) for constantly spamming it.

The point is that uncapping FPS requires changing settings that are literally outside of the game itself. It's not a matter of whether or not it was intended; Crash runs have historically always banned anything that involves manipulating something outside of the game or run itself. This is one of the MANY reasons we decided to cap the game.

I explained this in the previous thread, and you chose to ignore it. You're allowed to have your own opinions but several people here who ACTUALLY RUN THE GAME (fun fact, you don't/haven't) have explained why we have things set the way we do. Constantly telling us what we should be doing with OUR game that YOU don't play does nothing except make you look like a douche (which you already admitted to).

We're not changing anything, and if you have a problem with that then you can leave, because you are bringing nothing productive to the table.

There was a reason, you just chose to ignore it.

Instead of requesting such a category could be added, you could just learn the movement tech that makes the game faster. This is speedrunning after all.

I have updated the original post to reflect changes in how we define load times. Be sure to reacquaint yourself if you have any concerns.

Pretty much what JHobz said. My OS is on an HDD but I recently bought an external SSD to store Crash on, so load times would be better. So any PC run I submit from now on would have SSD as the Hard Drive Type.

A Hat in Time also restricts to 60 FPS as well, if I’m not mistaken.

Along with the monitor thing, the game does not natively support an FPS higher than 60. Uncapping the FPS requires messing with settings that are not within the game itself, which was another reason for the 60 FPS cap.

If you're talking about Crash 2, yes that is a known bug on all versions. If you reach the doorway before it actually spawns it locks you out. It's fixed by either visiting a level in a different Warp Room or reloading the save file.

Video tutorial has been added to this post and the Guide section.

Did some testing, and it seems that on PC, the Nitros detonate in a chain if you have already picked up the clock and detonate simultaneously if you haven't.

On console they appear to detonate simultaneously regardless, and we haven't figured out a way to make them not.