Troubleshooting: Standalone Problems And Solutions


JanH

Recommended Posts

*Update (11/10/2013) - We have an updated/consolidated troubleshooting thread which includes both Steam and Standalone versions located here: http://forums.kleien...-and-solutions/

 

These are some of the basic steps you can take to hopefully resolve some Standalone issues on your own without having to wait for a reply on the forum.

LINUX OS
 

Xbox 360 Controller Issue: Sometimes the default Linux Xbox controller driver (xpad) just refuses to deal with the triggers properly (running and hypersense). The generally accepted fix in the Steam community for when this happens is to install the xboxdrv drivers instead. (http://pingus.seul.org/~grumbel/xboxdrv/)

 

Also, sometimes the gamepad drivers can give phantom inputs; for example, when using gaming keyboards that have extra scrollwheels etc. on them. This is an issue we're working on, but in the meantime the controller can be disabled using the "-nocontroller" command-line switch

 

Linux Standalone unable to launch: Usually this is because of security programs or settings removing permissions from the executable inside the zip file. Making bin/ninja-bin32 and bin/ninja-bin64 executable using 'chmod +x' should fix this.

 

Mac OS X

 

Gameplay Slowdown: Sometimes Mark of the Ninja standalone experiences slowdown on older Macs. Unfortunately, the solution is to reduce the resolution to a more recommended/supported setting.

 

Mac Standalone unable to launch: Like with Linux, sometimes the Mac standalone game is unable to run because security settings/programs have removed permissions from the executable. Using the Terminal to navigate to ninja.app/Contents/MacOS and calling 'chmod +x ninja' should fix this also.

  • Open Terminal app (in Applications -> Utilities)
     
  • copy this line into Terminal without the quotes : "chmod +x /Applications/ninja.app/Contents/MacOS/ninja"
     
  • Press Enter/Return

Please note that this will work if you placed ninja into Applications. If this is not the case, simply update the previous path to your path.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Please be aware that the content of this thread may be outdated and no longer applicable.