[FIXED] Sanctum for PC Crashes, Errors, Freezes, Low performance, Poor framerates, Multiplayer problems, Bind key error, Alt-tab bug, Crossfire and SLI issues, Mouse spinning error

Fixing Sanctum for PC Crashes, Errors, Freezes, Low performance

Sanctum is an FPS tower defense game, and that’s what exactly makes it unique from other tower defense games — FPS TD! When the havoc starts, you jump right into the action with your own weapons and play a key role in the defense (to quote from IGN). Unfortunately, despite the really fun gameplay, the major setback would be crashes and glitches that I encountered before I got it to run smoothly. I’m sharing with you below a hotfix list that I compiled from various web and forum resources.

Hope this helps you! If there are other crashes or errors not covered here, please post in the comments section and I will try to help you.

First things first! Make sure you meet Sanctum for PC minimum system requirements:

• OS: Windows XP/Vista/7
• Processor: Intel Core 2 Duo @ 2.0 GHz / AMD Athlon 64 X2 4200+
• Memory: 2 Gb
• Hard Drive: 2 Gb free
• Video Memory: 256 Mb
• Video Card: nVidia GeForce 7600 / ATI Radeon X1600
• Sound Card: DirectX Compatible
• DirectX: 9.0c

Also, please make sure you upload your nVidia/ATI/IntelHD drivers to the latest version!

Problem 1# Sanctum PC Crashes and Freezes upon Startup/Launch

Possible Solution:

The quick fix to this annoying problem is to open the ‘SanctumEngine.ini’ file located in “Documents\My Games\Sanctum\SanctumGame\Config” and edit the line:

bInitializeShadersOnDemand=False
and change it to
bInitializeShadersOnDemand=True

Voila! Worked for me.

Problem 2# Sanctum framerate issues, performance issues, slow gameplay, glitches, buggy

Possible Solution:

Usually this is due to insufficient resources in your graphics card, but also it is partly due to the engine design of Sanctum for PC. You can edit the ‘sanctumengine.ini’ file located at Documents/my games/sanctum/sanctumgame/config and edit the line “bSmoothFrameRate=TRUE” to “bSmoothFrameRate=false”.

Please note that this command is repeated twice in the same config file so make sure you change it in both of these sections.

If you are still not content with the performance or FPS boost it gives you, try setting the following variables:

• bSmoothFrameRate=TRUE
• MinSmoothedFrameRate=0
• MaxSmoothedFrameRate=120

Sanctum should run much better and smoother now.

Problem 3# Sanctum PC LAN Error – “Can’t Host”

Possible Solution:

Please wait for the next patch! According to the developersthe upcoming patch will solve the problem. This is an issue with the Steam Client (sheesh!).

Problem 4# Sanctum PC online multiplayer connection issues, port forwarding issue

Possible Solution:

If you want to play online/host the game, you will need to forward these ports since the game as NAT-Traversal issues.

• TCP: 7777, 27000-27039
• UDP: 1200, 7777, 27000-27039

Problem 5# Sanctum Multiplayer Join by Friend Not Working

Possible Solution:

Please wait for the next patch! According to the developers the upcoming patch will solve the problem.

Problem 6# Sanctum (PC) Can’t Bind Keys – Default Key Notifications

Possible Solution:

Despite already having customized your own controls in Sanctum for PC, this glitch still shows you default key notifications which is pretty annoying. This bug will be resolved in the next patch, but for the mean time you can delete this file:

%My Documents%\My Games\Sanctum\SanctumGame\Config\SanctumSanctumPlayerInput.ini

Problem 7# Sanctum Alt-Tab Graphics Bugs

Possible Solution:

Pressing Alt-Tab will give you a headache of a graphics problem in Sanctum for PC. The workaround is to press TAB to go into overview mode, and then tab-out of overview mode to resolve it. This will be fixed in the upcoming patch.

Problem 8# Sanctum ATI Crossfire framerate issues, low performance, glitches

Possible Solution:

If you are experiencing low performance on high-end rig with ATI Crossfire, enable the AI and see if that resolve the issues.

Problem 9# Sanctum PC Mouse Spinning Error

Possible Solution:

Remove or unplug the controller and see if that works.

Loading...