[trh0awayman]

The Pokemon Snap one brings me back to when I was a kid. They had these Pokemon Snap machines, and you used to be able to take your memory card to the local mall and use them to print out stickers from the photos you took in game. Those "bridges" between the virtual world and the real world endlessly fascinated me.

[matsemann]

I thought this page was mostly geometry+shaders. But the snap version has lots of interactivity! You can trigger lots of the stuff you could trigger in the game. Have they replicated all that manually or how?

[pfedak]

The Pokemon Snap behavior is a mixture of handwritten code and parsing of the game's AI code. It was originally written in a very structured way that makes it easier than having to fully emulate. More involved interactions are missing (Magikarp evolution in the valley, a lot of the cave sequences)

[ceroxylon]

The Magikarp evolution was the first thing I tried and it worked for me, have to use the pesterball and not the apple.

[pfedak]

Sorry, to clarify, it's supposed to be a multi-step process (see https://www.youtube.com/watch?v=mxlvsts3c6o ) where you get it to jump onto land, then it gets kicked to another location where you can knock it into the waterfall.

In the game, these are actually two separate entities, and I haven't done anything to prevent the "kicked" one from immediately spawning in the air here https://noclip.website/#snap/1A;ShareData=AUsPn92;%5eVT:h=19... , or to hook up the first one to the second (although the system to signal between distant pokemon, which it probably uses, is mostly implemented). There are a few other instances of things that are supposed to be spawning conditionally which aren't handled yet, like extra lapras in the beach.

[ceroxylon]

You are totally correct! The nostalgia overload was messing with my memory, I appreciate your follow-up.

[matsemann]

Very cool work!!