[flagged]
It failed—that’s just the preamble. The video’s probably too long for it. You should know better than to use AI without checking the results.
Super Mario 64's invisible walls explained [video]
11–20 of 49 posts
Re: Super Mario 64's invisible walls explained [video]
#12How on earth does it take 4 hours to explain? I'm sure it's a lovely video but anyone care to tldr?
I think most of it is that he shows and explains every invisible wall in the game (Or tries to). The basic explanations are about an hour and a half. It uses graphics for explaining almost everything and does it in quite a bit of detail.
Re: Super Mario 64's invisible walls explained [video]
#13Re: Super Mario 64's invisible walls explained [video]
#14This is a new explainer by pannenkoek2012, the video game researcher best known for his discussion of "parallel universes" in Super Mario 64. He rarely publishes for general audiences these days, and the description says this video took him 10 months to make.
https://en.wikipedia.org/wiki/Pannenkoek2012 https://knowyourmeme.com/memes/05x-a-presses-but-first-we-ne...
Re: Super Mario 64's invisible walls explained [video]
#15For over a decade, the author of this video has been leading an effort to complete Super Mario 64 with the smallest amount of A presses, often using extremely complex strategies. Here's a 5h video with the history. Bismuth says the history video took roughly 1500-2000 hours.
Re: Super Mario 64's invisible walls explained [video]
#16The amount of effort in this video is astounding.
Quote from the author
> If you’ve wondered where I’ve been for the past 10 months, it was working day and night on this one video. In other words, I never actually left, I’ve been working on sm64 the whole time. So I didn’t forget about you guys :)
Re: Super Mario 64's invisible walls explained [video]
#17How on earth does it take 4 hours to explain? I'm sure it's a lovely video but anyone care to tldr?
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.
Re: Super Mario 64's invisible walls explained [video]
#18How on earth does it take 4 hours to explain? I'm sure it's a lovely video but anyone care to tldr?
https://www.youtube.com/watch?v=YsXCVsDFiXA&t=3228s
Thanks for that. I will go through the whole video later but that at least covered the basic premise.
Essentially, due to the technique used for collision detection, tiny gaps in the geometry causes collision system to treat parts of the scene as having very thin walls that stretch to the top of the play space. Depending on if Mario's quarter steps align with this little gap means that a collision can be made despite it not being visible. Also explains why they impact Mario sometimes and not others.
Like throwing a marble through a mesh fence but you cannot see the fence. Odds are you will make it through but it is essentially chance.
Re: Super Mario 64's invisible walls explained [video]
#19How on earth does it take 4 hours to explain? I'm sure it's a lovely video but anyone care to tldr?
His explanations are just very thorough. If the topic of how 3D video games are programmed interests you at all, there's many, many more hours worth of interesting content on both his main channel and his second uncommentated channel (uncommentatedpannen).
Re: Super Mario 64's invisible walls explained [video]
#20How on earth does it take 4 hours to explain? I'm sure it's a lovely video but anyone care to tldr?
I skimmed it and it’s trying to be the authoritative “phd thesis” on the topic. Still, many sections felt far too wordy and long. Technical communication is a difficult skill.
True. If he wanted to make it a proper phd thesis he'd use language to muddy the waters so no one could understand what he was saying.