3 ms·
it's a surprisingly deep topic involving Super Mario's 64 game mechanics such as "quarter steps", integer arithmetic, float-to-integer conversions, the chosen c
by Eduard 3y ago
it's a surprisingly deep topic involving Super Mario's 64 game mechanics such as "quarter steps", integer arithmetic, float-to-integer conversions, the chosen collision detection implementation and plenty more.
There are eight different causes that manifest in the observed "invisible wall" symptoms.
I find the level of detail given appropriate, and consider it as a valuable insight into game engine design as it was appropriate for the time.
- wtallis 3y agoI also think it helps to appreciate the historical context: this game was a major milestone in the development of the 3D platformer genre. Some of the bugs or treacherous optimizations may look naive to us now, but there had been few if any opportunities to make those mistakes prior to Super Mario 64. And in spite of the glitches, the game managed to be a huge success and highly influential even outside the platformer genre. This video does a wonderful job of illustrating how a handful of underlying issues can combine and manifest in so many different ways, and this was only the tip of the iceberg of 3D game physics glitches. And some of these issues are things games can still fall prey to today.
- duskwuff 3y agoVideos like these can also be a fantastic way of introducing viewers to CS and math topics that they wouldn't otherwise have been exposed to. The video game theme gets them in the door; the detailed analysis teaches them some things which are applicable beyond that game.