tinyBuild goes in-depth about bringing Mr. Shifty to Switch, should be patched to improve frame rate
Mr. Shifty made it to Switch today. The game itself has been fairly well received, but some players have been reporting issues with the frame rate, which can be irregular at times.
After some confusion surrounding the situation, tinyBuild CEO Alex Nichiporchik has promised to personally oversee “the patch submission process”. When an update is made available, players should hopefully find an improvement with the frame rate.
Nichiporchik went in-depth about bringing Mr. Shifty to Switch in a Reddit post:
I was the producer on games like SpeedRunners, Punch Club, and am currently neck-deep in Hello Neighbor.
Just wanted to drop in and clarify a couple of things. Obviously a game launch is an exciting and extremely stressful time for everyone involved — the publishing team, and the development team alike. So in the midst of the excitement and chaos some things get said that probably can sound awful out of context. It happens to all of us.
So let’s talk a little bit about Mr. Shifty. The dev team are an extremely talented group of individuals who previously worked on games like Fruit Ninja and Jetpack Joyride. I’m not a mobile gamer myself, but those 2 specifically I’ve spent countless hours on in the train (also Kingdom Rush). This experience is seen in how Mr. Shifty feels. The game has a very careful balancing act of physics-based calculations that create the satisfying feeling of punching a dude in the face and seeing him fall through a glass window.
The original plan was to launch Mr. Shifty in Q4 last year. The game was in pretty good shape to launch at that point, but we felt like launching just on Steam wouldn’t make much sense, as the game wouldn’t get enough exposure — so we started exploring consoles (that’s why PS4 and Xbox One were on our initial marketing — games that launch on multiple platforms at once tend to get a ton more exposure). We’ve brought games like Party Hard, No Time to Explain, The Final Station amongst others to consoles. So as soon as we learned what the Switch was — and how it controlled, it was a no-brainer. We wanted to bring Mr. Shifty to Switch. It made sense to release the Switch and PC builds at the same time so they’d elevate each other.
Like with all new platforms, there are limitations and timelines. The fact that Unity and UE4 plugins actually work for 3rd party devs before the platform’s launch are already a huge achievement by Nintendo and Unity/Epic.
With Mr. Shifty specifically though it’s all about that “feel”. The way the game was originally built, the physics are directly tied to the amount of frames per second. So if I would take the original game, and uncap the FPS — I’d get unexpected results like a guy flying through half of the map, and the “feel” would be lost.
Take this into account, then a brand new platform with brand new development tools and a 3rd party engine — and you have a recipe for disaster. But we pulled through. Somehow, through some miracle we were able to get the game out as a “first wave” title on Switch. We locked this version at 30fps for consistency in physics so we could keep the “feel” that everyone is excited about, and there are occasional drops on some production units which we’re working on replicating and preparing a patch. But the fact that we shipped on a brand new platform, in light of all these facts, makes me nothing but proud.
I think we got very lucky with the Switches we have, as mine — after 80 hours of Zelda — hasn’t seen any issues, same for Shifty; I personally couldn’t get it to drop below 25fps on the later stages with a ton of enemies, other times it’s consistent 30. But as we started sending out media keys, a small number of press outlets reported major slowdowns on their consoles. This came as a complete surprise to us, and we’ve been tracking down possible issues that we’d solve with an upcoming patch.
I’m just very sorry that the stress on everyone involved created this situation. Some things were said that shouldn’t have been, and we didn’t do a good job with communicating here. I hope this post brings some context to what’s going on.
I’ll personally oversee the patch submission process to get it out ASAP.
