Frequently Asked Questions (FAQ) - Revision history

Wookieejedi: update with Knet reference

2024-02-19T15:33:54Z

update with Knet reference

← Older revision		Revision as of 15:33, 19 February 2024
Line 28:		Line 28:
	As of FSO version 22.0, players are now able to assign up to 4 independent joysticks, gamepads, throttles, or game controllers; independently assign the mouse to controls; can assign a primary input binding and a secondary input binding from two different joysticks per control.		As of FSO version 22.0, players are now able to assign up to 4 independent joysticks, gamepads, throttles, or game controllers; independently assign the mouse to controls; can assign a primary input binding and a secondary input binding from two different joysticks per control.

	In order to make use of this capability, you must use a compatible launcher or manually set the joystick ID and GUID's within your '''fs2_open.ini''' file.		In order to make use of this capability, you must use a compatible launcher such as Knossos.NET or manually set the joystick ID and GUID's within your '''fs2_open.ini''' file.

EatThePath: /* Where do I get the Joystick ID's and GUID's? */

2022-10-09T20:14:58Z

Where do I get the Joystick ID's and GUID's?

← Older revision		Revision as of 20:14, 9 October 2022
Line 59:		Line 59:

	'''Example:''' '''''C:\Games\FreespaceOpen\bin\FSO-22.0.0\windows\x64> fs2_open_22_0_0_x64_SSE2.exe -get_flags json_v1 > flags.txt'''''		'''Example:''' '''''C:\Games\FreespaceOpen\bin\FSO-22.0.0\windows\x64> fs2_open_22_0_0_x64_SSE2.exe -get_flags json_v1 > flags.txt'''''

			Keep in mind this is an example only. You will need to change '''FSO-22.0.0''' and '''fs2_open_22_0_0_x64_SSE2.exe''' to fit the version you have installed.


	Windows users will probably also need to set the '''FSO_KEEP_STDOUT''' environment variable, due to its tendency to shut down the STDOUT streams to console when the application is identified as a WINDOWS application (as opposed to a CONSOLE application), in which case they should try the following:		Windows users will probably also need to set the '''FSO_KEEP_STDOUT''' environment variable, due to its tendency to shut down the STDOUT streams to console when the application is identified as a WINDOWS application (as opposed to a CONSOLE application), in which case they should try the following:


	'''cmd /V /C "set FSO_KEEP_STDOUT=1&& fs2_open_22_0_0_x64_SSE2.exe -get_flags json_v1 > flags.txt"'''		'''cmd /V /C "set FSO_KEEP_STDOUT=1&& fs2_open_22_0_0_x64_SSE2.exe -get_flags json_v1 > flags.txt"'''

			As above, '''fs2_open_22_0_0_x64_SSE2.exe''' will need to match the actual version you are working with.


	Once you have a flags.txt file created, look for a section that looks like this:		Once you have a flags.txt file created, look for a section that looks like this:

Z64555: /* Windows Tutorial for obtaining the GUID */

2022-06-01T14:12:02Z

Windows Tutorial for obtaining the GUID

← Older revision		Revision as of 14:12, 1 June 2022
Line 89:		Line 89:
	# In the command prompt window, type in "cd /D " (without the quotes), with a space after the D. Then, right click on the command prompt and Paste the address you copied from before. Hit the Enter key to execute the cd command. The prompt should then show the address text again with ">" as the last character to show that its now in that directory.		# In the command prompt window, type in "cd /D " (without the quotes), with a space after the D. Then, right click on the command prompt and Paste the address you copied from before. Hit the Enter key to execute the cd command. The prompt should then show the address text again with ">" as the last character to show that its now in that directory.
	# In the command prompt, type in "dir" and hit enter to execute the dir command, which should show you a list of all files and folders within the directory. Confirm that your fs2_open.exe is in there.		# In the command prompt, type in "dir" and hit enter to execute the dir command, which should show you a list of all files and folders within the directory. Confirm that your fs2_open.exe is in there.
	# Follow the directions outlined in [[#Where do I get the Joystick ID's and GUID's?]]		# Follow the directions outlined in [[#Where do I get the Joystick ID's and GUID's?]], Using the full name of your fs2_open.exe should it differ from the instructions.

Z64555: /* Windows Tutorial for obtaining the GUID */

2022-06-01T14:01:14Z

Windows Tutorial for obtaining the GUID

← Older revision		Revision as of 14:01, 1 June 2022
Line 81:		Line 81:

	=====Windows Tutorial for obtaining the GUID=====		=====Windows Tutorial for obtaining the GUID=====
	1. Navigate to your FSO installation using File Explorer. If you're using Knossos, then this directory is the same as "Library Path" within Knossos's settings.		# Navigate to your FSO installation using File Explorer. If you're using Knossos, then this directory is the same as "Library Path" within Knossos's settings.
			# Right click the address bar within File Explorer and "Copy the Address as Text"
	2. Right click the address bar within File Explorer and "Copy the Address as Text"		# Open the command prompt from the start menu:
			#* Open the start menu,
	3. Open the command prompt from the start menu: Open the start menu, ~~type~~ in "prompt", and then left click on "Command Prompt"		#* Type in "prompt",
			#* and then left click on "Command Prompt"
	4. In the command prompt window, type in "cd /D " (without the quotes), with a space after the D. Then, right click on the command prompt and Paste the address you copied from before. Hit the Enter key to execute the cd command. The prompt should then show the address text again with ">" as the last character to show that its now in that directory.		# In the command prompt window, type in "cd /D " (without the quotes), with a space after the D. Then, right click on the command prompt and Paste the address you copied from before. Hit the Enter key to execute the cd command. The prompt should then show the address text again with ">" as the last character to show that its now in that directory.
			# In the command prompt, type in "dir" and hit enter to execute the dir command, which should show you a list of all files and folders within the directory. Confirm that your fs2_open.exe is in there.
	5. In the command prompt, type in "dir" and hit enter to execute the dir command, which should show you a list of all files and folders within the directory. Confirm that your fs2_open.exe is in there.		# Follow the directions outlined in [[#Where do I get the Joystick ID's and GUID's?]]

	6. Follow the directions outlined in [[#Where do I get the Joystick ID's and GUID's?]]

Z64555: Add tutorial for Windows

2022-06-01T13:55:09Z

Add tutorial for Windows

← Older revision		Revision as of 13:55, 1 June 2022
Line 79:		Line 79:

	Use the "guid" and "id" key values to assign that joystick to Joy0, Joy1, Joy2, or Joy3 respectively.		Use the "guid" and "id" key values to assign that joystick to Joy0, Joy1, Joy2, or Joy3 respectively.

			=====Windows Tutorial for obtaining the GUID=====
			1. Navigate to your FSO installation using File Explorer. If you're using Knossos, then this directory is the same as "Library Path" within Knossos's settings.

			2. Right click the address bar within File Explorer and "Copy the Address as Text"

			3. Open the command prompt from the start menu: Open the start menu, type in "prompt", and then left click on "Command Prompt"

			4. In the command prompt window, type in "cd /D " (without the quotes), with a space after the D. Then, right click on the command prompt and Paste the address you copied from before. Hit the Enter key to execute the cd command. The prompt should then show the address text again with ">" as the last character to show that its now in that directory.

			5. In the command prompt, type in "dir" and hit enter to execute the dir command, which should show you a list of all files and folders within the directory. Confirm that your fs2_open.exe is in there.

			6. Follow the directions outlined in [[#Where do I get the Joystick ID's and GUID's?]]

Z64555: /* Where do I get the Joystick ID's and GUID's? */ Tweak the example a bit

2022-06-01T13:14:27Z

Where do I get the Joystick ID's and GUID's?: Tweak the example a bit

← Older revision		Revision as of 13:14, 1 June 2022
Line 58:		Line 58:


	'''Example:''' '''''C;\Games\~~FreeSpaceOpen~~\fs2_open_22_0_0_x64_SSE2.exe -get_flags json_v1 > flags.txt'''''		'''Example:''' '''''C:\Games\FreespaceOpen\bin\FSO-22.0.0\windows\x64> fs2_open_22_0_0_x64_SSE2.exe -get_flags json_v1 > flags.txt'''''

Z64555: Z64555 moved page Frequently Asked Questions to Frequently Asked Questions (FAQ): Rename for search bar to hit on common abbreviation

2022-04-25T14:00:42Z

Z64555 moved page Frequently Asked Questions to Frequently Asked Questions (FAQ): Rename for search bar to hit on common abbreviation

← Older revision	Revision as of 14:00, 25 April 2022
(No difference)

Z64555: /* Can I use multiple joysticks in FSO? */

2022-02-09T19:21:26Z

Can I use multiple joysticks in FSO?

← Older revision		Revision as of 19:21, 9 February 2022
Line 26:		Line 26:

	===Can I use multiple joysticks in FSO?===		===Can I use multiple joysticks in FSO?===
	As of FSO version 22.0, players are now able to assign up to 4 independent joysticks/controllers, independently assign the mouse to controls~~, and~~ can assign a primary input binding and a secondary input binding from two different joysticks per control.		As of FSO version 22.0, players are now able to assign up to 4 independent joysticks, gamepads, throttles, or game controllers; independently assign the mouse to controls; can assign a primary input binding and a secondary input binding from two different joysticks per control.

	In order to make use of this capability, you must use a compatible launcher or manually set the joystick ID and GUID's within your '''fs2_open.ini''' file.		In order to make use of this capability, you must use a compatible launcher or manually set the joystick ID and GUID's within your '''fs2_open.ini''' file.

Z64555: formatting

2022-02-09T18:53:57Z

formatting

← Older revision		Revision as of 18:53, 9 February 2022
Line 29:		Line 29:

	In order to make use of this capability, you must use a compatible launcher or manually set the joystick ID and GUID's within your '''fs2_open.ini''' file.		In order to make use of this capability, you must use a compatible launcher or manually set the joystick ID and GUID's within your '''fs2_open.ini''' file.


	====Where is the fs2_open.ini file?====		====Where is the fs2_open.ini file?====
Line 34:		Line 35:

	'''Example:''' '''''C:\Users\z64555\AppData\Roaming\HardLightProductions\FreeSpaceOpen\fs2_open.ini'''''		'''Example:''' '''''C:\Users\z64555\AppData\Roaming\HardLightProductions\FreeSpaceOpen\fs2_open.ini'''''


	====How do I assign my joysticks in the fs2_open.ini?====		====How do I assign my joysticks in the fs2_open.ini?====
Line 48:		Line 50:

	'''Joy0''' is effectively the same as '''CurrentJoystick'''		'''Joy0''' is effectively the same as '''CurrentJoystick'''


	====Where do I get the Joystick ID's and GUID's?====		====Where do I get the Joystick ID's and GUID's?====

Z64555: Formatting; Add FAQs for multi-joy.

2022-02-09T18:53:08Z

Formatting; Add FAQs for multi-joy.

@@ Line 1: / Line 1: @@
-==Why are my bindings back to defaults?==
+This page contains answers to questions that may be asked when playing newer versions of FSO.  They are usually questions related to new behaviors not present in older version or vanilla FreeSpace, and are often questions that don't have a simple one-line answer.
 If you created or played with a pilot on FSO 22.0 or later, your bindings were moved into files known as "presets" which are saved in a sub directory of your players folder.
 '''Example:''' '''''C:\Users\z64555\AppData\Roaming\HardLightProductions\FreeSpaceOpen\data\players\presets'''''
 The reason why your bindings are back to defaults in pre-22.0 version is because:
@@ Line 14: / Line 19: @@
-==Why can't I use my pilot with different versions of FSO?==
+===Why can't I use my pilot with different versions of FSO?===
 Our pilot file handling code has improved over the years to allow new data to be added to the pilot file, but we still haven't managed to get it in a perfect state due to a lack of manpower and interest.
 Pilot files might be still usable across different versions of FSO, but this can not be guaranteed at this point in time.  When in doubt, it is always recommended that you make a clone of your pilot and use the clone for that version of FSO.