Sam & Max Save the World has been updated to version 2.0.0, with a handful of bug fixes big and small. Okay, it sounds ominous that this is "version 2.0.0," especially considering the remaster in totality is basically already version 2.0 in spirit, but we recompiled the game engine itself for the first time in quite a while as part of this patch, to fix a few of the lower-level game-wide bugs, so it felt right. Also, it's been a couple years since the last patch; you deserve this.
Patch notes for today’s Sam & Max Save The World update (version 2.0.0):
Game-wide:
- Fixed instances where setting the game's resolution higher than your screen's physical resolution would cause the cursor to get trapped in a small corner of the screen.
- Fixed crashes that occurred in rare edge cases when the engine tried to change the list of loaded dialog files when the list was in use. It feels strange explaining a bug in a decades-old proprietary game engine in the patch notes, but here we are reading it together.
- Reduced situations that would cause the engine's audio system to get confused and play a sound or piece of music a second time.
Episode 101:
- Fixed typo in Czech driving tutorial text.
- Added a beat up old version of the Majestic Theater signage to the Asylum exterior, as a treat for the lore sickos.
Episode 102:
- Fixed missing transparency in the localized versions of TV Studio exit signs.
Episode 105:
- Fixed logic in VR Office dialog that could prevent getting a coin from Jimmy Two-Teeth, in some rare cases.
Episode 106:
- Fixed Red Max's muzzle flash sometimes being visible after sending him on the roller coaster. Honestly bug descriptions are fun sometimes.
- Fixed big red button in Laser Room not rendering on Switch.
- Fixed Red Max's muzzle flash not rendering on Switch.
- Fixed roller coaster button in Moon Retreat not rendering on Switch.
- The closing credits frame colors now match the original game instead of being default grey.
That's all for now! And as usual if you find a bug please point it out in the appropriate forum or the comments below, and we'll do our best to fix it in a future patch!