The Sam & Max Ep.303 Game Killing glitch, Steam version. Post contains spoilers.
Hi there,
Reporting a major glitch in the Steam Version of Sam & Max Episode 303 - They Stole Max's Brain which completely kills the game and leaves you unable to continue.
The glitch occurs in the Museum,
This loops continues until I End Task in task manager, or the game crashes.
This means that I cannot complete the game.
Please refer to this thread on the Steam users forums: http://forums.steampowered.com/forums/showthread.php?t=1318954
Myself and a few others have done a mini investigation to try and find possible solutions
including:
* Never using Max's teleportation ability during Act 3 to teleport to the Museum by leaving the DeSoto there.
* Using the saved game of another steam user who COULD complete the game without the glitch occurring.
* Running Steam in offline mode.
* Deleting all local game files and saved games from Steam, and re-downloading/re-installing the game.
all of which have still resulted in having the glitch and being left unable to continue.
Speaking to other Steam users who did and didn't have the glitch and were able to continue the game, I've found the following to have no relation to the glitch:
CPU manufacturer. Both AMD and Intel users have experienced the problem.
Graphics card manufacturer. Both ATI and Nvidia users experienced the glitch.
32bit or 64 bit OS. Myself and another user are both using 32-bit OS, however I had the glitch and they didn't.
Platform. Different users playing on PC have either had the glitch or not.
However there have been some possible links.
Multi-Core Processors. A user running a single core processor did NOT have the glitch, however on my multi-core PC I DID have the glitch.
OS Version. User running Windows XP had NO glitch, my Windows 7 machine DID.
Going by resposnses on the Telltale Games forums, the glitch seems to only be happening with the Steam version. It may be something wrong with the code you sent to Valve to put on Steam, hence me posting this on here
Apologies for the lengthy post, But I thought I should give you as much detail as possible about what we've already discovered to help you get to the root of the problem faster
Many Thanks
Reporting a major glitch in the Steam Version of Sam & Max Episode 303 - They Stole Max's Brain which completely kills the game and leaves you unable to continue.
The glitch occurs in the Museum,
after using the Brain Screw on Sammun-Mak and the cutscene that follows, Sam is made to fight Skunkape.
After the start of the fight, Skunkape taunts Sam and the player should then have the action selector ring appear.
However, a glitch occurs where the action ring does NOT come up.
After Skunkape taunts Sam, it cuts straight through to Sam growling and attacking Skunkape, then being hit back.
The game then continuously loops back to:
Skunkape taunting Sam,
Sam AUTOMATICALLY growling and attacking, no action ring appears at all.
being hit back,
Skunkape taunt,
Sam growls and attacks,
gets hit back
Skunkape taunts... etc etc
After the start of the fight, Skunkape taunts Sam and the player should then have the action selector ring appear.
However, a glitch occurs where the action ring does NOT come up.
After Skunkape taunts Sam, it cuts straight through to Sam growling and attacking Skunkape, then being hit back.
The game then continuously loops back to:
Skunkape taunting Sam,
Sam AUTOMATICALLY growling and attacking, no action ring appears at all.
being hit back,
Skunkape taunt,
Sam growls and attacks,
gets hit back
Skunkape taunts... etc etc
This loops continues until I End Task in task manager, or the game crashes.
This means that I cannot complete the game.
Please refer to this thread on the Steam users forums: http://forums.steampowered.com/forums/showthread.php?t=1318954
Myself and a few others have done a mini investigation to try and find possible solutions
including:* Never using Max's teleportation ability during Act 3 to teleport to the Museum by leaving the DeSoto there.
* Using the saved game of another steam user who COULD complete the game without the glitch occurring.
* Running Steam in offline mode.
* Deleting all local game files and saved games from Steam, and re-downloading/re-installing the game.
all of which have still resulted in having the glitch and being left unable to continue.
Speaking to other Steam users who did and didn't have the glitch and were able to continue the game, I've found the following to have no relation to the glitch:
CPU manufacturer. Both AMD and Intel users have experienced the problem.
Graphics card manufacturer. Both ATI and Nvidia users experienced the glitch.
32bit or 64 bit OS. Myself and another user are both using 32-bit OS, however I had the glitch and they didn't.
Platform. Different users playing on PC have either had the glitch or not.
However there have been some possible links.
Multi-Core Processors. A user running a single core processor did NOT have the glitch, however on my multi-core PC I DID have the glitch.
OS Version. User running Windows XP had NO glitch, my Windows 7 machine DID.
Going by resposnses on the Telltale Games forums, the glitch seems to only be happening with the Steam version. It may be something wrong with the code you sent to Valve to put on Steam, hence me posting this on here
Apologies for the lengthy post, But I thought I should give you as much detail as possible about what we've already discovered to help you get to the root of the problem faster
Many Thanks
This discussion has been closed.
Comments
in-meinem-turm- here:winslow:
Cool
If there's any details I missed don't hesitate to add.
The problem is that I cannot add much this time since I don't have the problem this time.
Reminds me of that old bug that Grim Fandango used to have where if you had a processor that was faster than 400MHz (epic speed
Did it work?
You also seem to be the first with the TTG-version that has this problem. Strange.
Windows XP SP3, Mac Book Pro, late 2007 version.
I can confirm setting processor affinity fixes the infinite action loop.
I can also confirm the crash on startup is due to multi-monitor configurations, and copying a fixed .props configuration file (located in your my documents folder) once you've managed to get the game to start causes all the other games to work properly.
This issue affects all the season 3 games for sure, i have not tested season 1 or 2 (still downloading).
Steps to fix crash on startup (in multi-monitor systems). disable monitor 2, start game. alt-enter to force windowed mode. reenable second monitor. set games resolution to your native display resolution, and then reenable fullscreen. worked like a charm.
as a note: having to set affinity and disabling secondary monitors is a serious engine bug, and i can only hope a fix will be back-patched into the previous episodes.
All the relevant information i can think of.
OS: Windows 7 (64bit)
CPU: AMD Athlon x2 6400+ (3.2Ghz)
Ram: OCZ DDR2-800 4GB Dual Channel kit
Video: NVidia 9800 GTX+
Sound: Creative X-FI powering Razor Carcarious Headphones
Monitors: Dual Hanns.G/Hannstar 24" LCD Monitors [1680x1050@60hz]
Controller: Joytech XBox 360 Controller (Wired) for Console/PC
UAC: Enabled
Anti-virus: Microsoft Security Essentials
attached to this post is my dxdiag report (64bit)