Marker States - Revision history

BASys: /* Tools */ Corrected domain

2013-05-06T09:43:20Z

Tools: Corrected domain

← Older revision		Revision as of 04:43, 6 May 2013
Line 47:		Line 47:
	== Tools ==		== Tools ==
	A selection of tools utilising "marker states" -		A selection of tools utilising "marker states" -
	* Configuring Aircraft - Launch-bar/Tail Hook positions - [http://lc0277.~~nerim~~.~~net~~/~~wiki/index~~.~~php?Adapting%20FSX%20aircrafts%20to%20acceleration%20carriers~~ Lamont Clarke's wiki - Adapting FSX aircrafts to acceleration carriers]		* Configuring Aircraft - Launch-bar/Tail Hook positions - [http://lc0277.gratisim.fr/Adapting_SX_aircrafts_to_acceleration_carriers.html Lamont Clarke's wiki - Adapting FSX aircrafts to acceleration carriers]

	[[Category:SimConnect]]		[[Category:SimConnect]]

2008-06-01T09:41:22Z

Tools

← Older revision		Revision as of 04:41, 1 June 2008
Line 45:		Line 45:
	Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.		Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.

	=== Tools ===		== Tools ==
	A selection of tools utilising "marker states" -		A selection of tools utilising "marker states" -
	* Configuring Aircraft - Launch-bar/Tail Hook positions - [http://lc0277.nerim.net/wiki/index.php?Adapting%20FSX%20aircrafts%20to%20acceleration%20carriers Lamont Clarke's wiki - Adapting FSX aircrafts to acceleration carriers]		* Configuring Aircraft - Launch-bar/Tail Hook positions - [http://lc0277.nerim.net/wiki/index.php?Adapting%20FSX%20aircrafts%20to%20acceleration%20carriers Lamont Clarke's wiki - Adapting FSX aircrafts to acceleration carriers]

	[[Category:SimConnect]]		[[Category:SimConnect]]

2008-06-01T09:34:00Z

← Older revision		Revision as of 04:34, 1 June 2008
Line 44:		Line 44:
	== Observations ==		== Observations ==
	Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.		Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.

			=== Tools ===
			A selection of tools utilising "marker states" -
			* Configuring Aircraft - Launch-bar/Tail Hook positions - [http://lc0277.nerim.net/wiki/index.php?Adapting%20FSX%20aircrafts%20to%20acceleration%20carriers Lamont Clarke's wiki - Adapting FSX aircrafts to acceleration carriers]

	[[Category:SimConnect]]		[[Category:SimConnect]]

2008-05-18T15:04:51Z

← Older revision		Revision as of 10:04, 18 May 2008
Line 45:		Line 45:
	Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.		Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.

	~~[[Category:FSX]]~~
	[[Category:SimConnect]]		[[Category:SimConnect]]

2008-04-18T20:02:09Z

← Older revision		Revision as of 15:02, 18 April 2008
Line 1:		Line 1:
			{{Infobox-Applicable-FSVersion
			\| FSXI = false
			\| FSXA = true
			\| FSX = true
			\| FS2004 = false
			\| FS2002 = false
			\| FS2000 = unknown
			\| FS98 = unknown
			}}
	== Using Marker States ==		== Using Marker States ==
	The SimConnect interface includes a function that, when activated, displays cross hairs at defined points on the visual model. These points correspond to points defined in the models aircraft.cfg and *.air file, such as wheels, contact points, fuel tank locations, CoG etc. This is useful for designers to be able to see where exactly on the model these points have been placed.		The SimConnect interface includes a function that, when activated, displays cross hairs at defined points on the visual model. These points correspond to points defined in the models aircraft.cfg and *.air file, such as wheels, contact points, fuel tank locations, CoG etc. This is useful for designers to be able to see where exactly on the model these points have been placed.

2008-02-16T09:16:47Z

Using Marker States moved to Marker States: Titling rationalisation

← Older revision	Revision as of 04:16, 16 February 2008
(No difference)

2007-11-30T14:39:35Z

← Older revision		Revision as of 09:39, 30 November 2007
Line 36:		Line 36:
	Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.		Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.

			[[Category:FSX]]
	[[Category:SimConnect]]		[[Category:SimConnect]]

2006-12-23T06:45:03Z

Sample Code

← Older revision		Revision as of 01:45, 23 December 2006
Line 15:		Line 15:
	When you want to turn on the markers (such as after a button press) add the following code, this will send the request to FS.		When you want to turn on the markers (such as after a button press) add the following code, this will send the request to FS.
	<code>		<code>
	SIMCONNECT_DATA_MARKERSTATE *sdm;		SIMCONNECT_DATA_MARKERSTATE sdm;

	//Set the markers to ON (use 0 for off)		//Set the markers to ON (use 0 for off)
	sdm->dwMarkerState = 1;		sdm.dwMarkerState = 1;

	//Copy the marker name to the struct		//Copy the marker name to the struct
	//List of available markers can be found in the SDK		//List of available markers can be found in the SDK
	strcpy_s (sdm->szMarkerName, "Scrape");		strcpy_s (sdm.szMarkerName, "Scrape");

	//Send the request to FS		//Send the request to FS
	hr = SimConnect_SetDataOnSimObject(hSimConnect, DEFINITION_MARKER, SIMCONNECT_OBJECT_ID_USER, 0, 1, sizeof(sdm), sdm);		hr = SimConnect_SetDataOnSimObject(hSimConnect, DEFINITION_MARKER, SIMCONNECT_OBJECT_ID_USER, 0, 1, sizeof(sdm), &sdm);
	</code>		</code>

2006-12-23T05:38:14Z

Sample Code

← Older revision		Revision as of 00:38, 23 December 2006
Line 15:		Line 15:
	When you want to turn on the markers (such as after a button press) add the following code, this will send the request to FS.		When you want to turn on the markers (such as after a button press) add the following code, this will send the request to FS.
	<code>		<code>
	SIMCONNECT_DATA_MARKERSTATE sdm;		SIMCONNECT_DATA_MARKERSTATE *sdm;

	//Set the markers to ON (use 0 for off)		//Set the markers to ON (use 0 for off)
	sdm.dwMarkerState = 1;		sdm->dwMarkerState = 1;

	//Copy the marker name to the struct		//Copy the marker name to the struct
	//List of available markers can be found in the SDK		//List of available markers can be found in the SDK
	strcpy_s (sdm.szMarkerName, "Scrape");		strcpy_s (sdm->szMarkerName, "Scrape");

	//Send the request to FS		//Send the request to FS

2006-11-24T09:22:53Z

← Older revision		Revision as of 04:22, 24 November 2006
Line 35:		Line 35:
	== Observations ==		== Observations ==
	Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.		Limited testing has shown that only one marker type can be sent to FS at a time (ie no arrays). Also only the users aircraft could be targeted.

			[[Category:SimConnect]]