Difference between revisions of "Inner Space bit options"

From ISBoxer
Jump to: navigation, search
m
m
Line 1: Line 1:
  
With Windows 10, came some issues with running 32bit Inner Space and 64 bit game clients.  It worked for some users, and other users just had not luck.  In the end it was decided to default to using 64bit Inner Space and resolve this problem, but that also requires making sure that 64 bit game clients should be used where possible.
+
With Windows 10, came some issues with running 32 bit Inner Space and 64 bit game clients.  It worked for some users, and other users just had not luck.  In the end it was decided to default to using 64 bit Inner Space and resolve this problem.  It was found that users also had trouble selecting the correct bit game clients too, so it was made, where possible to try and be smart about selecting matching bit game clients to the matching bit Inner Space where this is possible.
  
If you game is a well known game (i.e. you have not configured it as "Other", or Inner Space recognises the executable name, then depending on some of it's options it may force which game client x86/x64 is used (x86 is also known as 32bit, weird huh).
+
If you game is a well known game i.e. Inner Space recognises the executable name, then depending on some of the Inner Space configuration options it may force a different bit game client.
 +
<br/> Fun fact: x86 is 32 bit, x64 is 64 bit. Weird huh.
  
What this means is that depending on Inner Space's configuration, then it may end up executing a version of the game client that you have not configured it to use.
+
In other words, this means is that depending on Inner Space's configuration, it may end up executing a different executable file than what is configured in the [[Game Profile]].
  
  

Revision as of 10:52, 25 August 2016

With Windows 10, came some issues with running 32 bit Inner Space and 64 bit game clients. It worked for some users, and other users just had not luck. In the end it was decided to default to using 64 bit Inner Space and resolve this problem. It was found that users also had trouble selecting the correct bit game clients too, so it was made, where possible to try and be smart about selecting matching bit game clients to the matching bit Inner Space where this is possible.

If you game is a well known game i.e. Inner Space recognises the executable name, then depending on some of the Inner Space configuration options it may force a different bit game client.
Fun fact: x86 is 32 bit, x64 is 64 bit. Weird huh.

In other words, this means is that depending on Inner Space's configuration, it may end up executing a different executable file than what is configured in the Game Profile.


InnerSpace Configuration General.png

Inner Space has two settings to manage bit options.

  1. Inner Space will run the 32 bit or 64 bit version of itself. By default this option will be set if your operating system is a 64 bit operating system.
  2. Where a game is a well known game and is known to have both 32 bit and 64 bit versions, then force the appropriate version to load to match the version of Inner Space that is running.