Pathfind::getClosestVehicleNodeWithHeading - Revision history

Shr0x: mp.game v2 compatibility

2021-09-21T17:23:29Z

mp.game v2 compatibility

← Older revision		Revision as of 17:23, 21 September 2021
Line 1:		Line 1:
	p5, p6 and p7 seems to be about the same as p4, p5 and p6 for GET_CLOSEST_VEHICLE_NODE. p6 and/or p7 has something to do with finding a node on the same path/road and same direction(at least for this native, something to do with the heading maybe). Edit this when you find out more.<br><br>p5 is either 1 or 12. 1 means any path/road. 12, 8, 0 means node in the middle of the closest main (asphalt) road.<br>p6 is always 3.0<br>p7 is always 0.<br><br>Known node types: simple path/asphalt road, only asphalt road, water, under the map at always the same coords. <br><br>The node types follows a pattern. For example, every fourth node is of the type water i.e. 3, 7, 11, 15, 19, 23, 27, 31, 35, 39... 239. Could not see any difference between nodes within certain types. <br>Starting at 2, every fourth node is under the map, always same coords.<br>Same with only asphalt road (0, 4, 8, etc) and simple path/asphalt road (1, 5, 9, etc).<br><br>gtaforums.com/topic/843561-pathfind-node-types<br><br>Example of usage, moving vehicle to closest path/road:<br>Vector3 coords = ENTITY::GET_ENTITY_COORDS(playerVeh, true);<br>Vector3 closestVehicleNodeCoords; <br>float roadHeading; <br>PATHFIND::GET_CLOSEST_VEHICLE_NODE_WITH_HEADING(coords.x, coords.y, coords.z, &closestVehicleNodeCoords, &roadHeading, 1, 3, 0); <br>ENTITY::SET_ENTITY_HEADING(playerVeh, roadHeading);<br>ENTITY::SET_ENTITY_COORDS(playerVeh, closestVehicleNodeCoords.x, closestVehicleNodeCoords.y, closestVehicleNodeCoords.z, 1, 0, 0, 1);<br>VEHICLE::SET_VEHICLE_ON_GROUND_PROPERLY(playerVeh);<br><br>------------------------------------------------------------------<br>C# Example (ins1de) : pastebin.com/fxtMWAHD		p5, p6 and p7 seems to be about the same as p4, p5 and p6 for GET_CLOSEST_VEHICLE_NODE. p6 and/or p7 has something to do with finding a node on the same path/road and same direction(at least for this native, something to do with the heading maybe). Edit this when you find out more.<br><br>p5 is either 1 or 12. 1 means any path/road. 12, 8, 0 means node in the middle of the closest main (asphalt) road.<br>p6 is always 3.0<br>p7 is always 0.<br><br>Known node types: simple path/asphalt road, only asphalt road, water, under the map at always the same coords. <br><br>The node types follows a pattern. For example, every fourth node is of the type water i.e. 3, 7, 11, 15, 19, 23, 27, 31, 35, 39... 239. Could not see any difference between nodes within certain types. <br>Starting at 2, every fourth node is under the map, always same coords.<br>Same with only asphalt road (0, 4, 8, etc) and simple path/asphalt road (1, 5, 9, etc).<br><br>gtaforums.com/topic/843561-pathfind-node-types<br><br>Example of usage, moving vehicle to closest path/road:<br>Vector3 coords = ENTITY::GET_ENTITY_COORDS(playerVeh, true);<br>Vector3 closestVehicleNodeCoords; <br>float roadHeading; <br>PATHFIND::GET_CLOSEST_VEHICLE_NODE_WITH_HEADING(coords.x, coords.y, coords.z, &closestVehicleNodeCoords, &roadHeading, 1, 3, 0); <br>ENTITY::SET_ENTITY_HEADING(playerVeh, roadHeading);<br>ENTITY::SET_ENTITY_COORDS(playerVeh, closestVehicleNodeCoords.x, closestVehicleNodeCoords.y, closestVehicleNodeCoords.z, 1, 0, 0, 1);<br>VEHICLE::SET_VEHICLE_ON_GROUND_PROPERLY(playerVeh);<br><br>------------------------------------------------------------------<br>C# Example (ins1de) : pastebin.com/fxtMWAHD
	==Syntax==		==Syntax==
	<syntaxhighlight lang="javascript">mp.game.pathfind.getClosestVehicleNodeWithHeading(x, y, z~~, outPosition, outHeading~~, nodeType, p6, p7);</syntaxhighlight>		<syntaxhighlight lang="javascript">mp.game.pathfind.getClosestVehicleNodeWithHeading(x, y, z, nodeType, p6, p7):</syntaxhighlight>
	=== Required Arguments ===		=== Required Arguments ===
	*'''x:''' float		*'''x:''' float
	*'''y:''' float		*'''y:''' float
	*'''z:''' float		*'''z:''' float
	*'''outPosition:''' Vector3
	*'''outHeading:''' float
	*'''nodeType:''' int		*'''nodeType:''' int
	*'''p6:''' float		*'''p6:''' float

Marty uploader: yay

2017-05-06T21:29:04Z

yay

← Older revision		Revision as of 21:29, 6 May 2017
Line 1:		Line 1:
	p5, p6 and p7 seems to be about the same as p4, p5 and p6 for GET_CLOSEST_VEHICLE_NODE. p6 and/or p7 has something to do with finding a node on the same path/road and same direction(at least for this native, something to do with the heading maybe). Edit this when you find out more.<br><br>p5 is either 1 or 12. 1 means any path/road. 12, 8, 0 means node in the middle of the closest main (asphalt) road.<br>p6 is always 3.0<br>p7 is always 0.<br><br>Known node types: simple path/asphalt road, only asphalt road, water, under the map at always the same coords. <br><br>The node types follows a pattern. For example, every fourth node is of the type water i.e. 3, 7, 11, 15, 19, 23, 27, 31, 35, 39... 239. Could not see any difference between nodes within certain types. <br>Starting at 2, every fourth node is under the map, always same coords.<br>Same with only asphalt road (0, 4, 8, etc) and simple path/asphalt road (1, 5, 9, etc).<br><br>gtaforums.com/topic/843561-pathfind-node-types<br><br>Example of usage, moving vehicle to closest path/road:<br>Vector3 coords = ENTITY::GET_ENTITY_COORDS(playerVeh, true);<br>Vector3 closestVehicleNodeCoords; <br>float roadHeading; <br>PATHFIND::GET_CLOSEST_VEHICLE_NODE_WITH_HEADING(coords.x, coords.y, coords.z, &closestVehicleNodeCoords, &roadHeading, 1, 3, 0); <br>ENTITY::SET_ENTITY_HEADING(playerVeh, roadHeading);<br>ENTITY::SET_ENTITY_COORDS(playerVeh, closestVehicleNodeCoords.x, closestVehicleNodeCoords.y, closestVehicleNodeCoords.z, 1, 0, 0, 1);<br>VEHICLE::SET_VEHICLE_ON_GROUND_PROPERLY(playerVeh);<br><br>------------------------------------------------------------------<br>C# Example (ins1de) : pastebin.com/fxtMWAHD		p5, p6 and p7 seems to be about the same as p4, p5 and p6 for GET_CLOSEST_VEHICLE_NODE. p6 and/or p7 has something to do with finding a node on the same path/road and same direction(at least for this native, something to do with the heading maybe). Edit this when you find out more.<br><br>p5 is either 1 or 12. 1 means any path/road. 12, 8, 0 means node in the middle of the closest main (asphalt) road.<br>p6 is always 3.0<br>p7 is always 0.<br><br>Known node types: simple path/asphalt road, only asphalt road, water, under the map at always the same coords. <br><br>The node types follows a pattern. For example, every fourth node is of the type water i.e. 3, 7, 11, 15, 19, 23, 27, 31, 35, 39... 239. Could not see any difference between nodes within certain types. <br>Starting at 2, every fourth node is under the map, always same coords.<br>Same with only asphalt road (0, 4, 8, etc) and simple path/asphalt road (1, 5, 9, etc).<br><br>gtaforums.com/topic/843561-pathfind-node-types<br><br>Example of usage, moving vehicle to closest path/road:<br>Vector3 coords = ENTITY::GET_ENTITY_COORDS(playerVeh, true);<br>Vector3 closestVehicleNodeCoords; <br>float roadHeading; <br>PATHFIND::GET_CLOSEST_VEHICLE_NODE_WITH_HEADING(coords.x, coords.y, coords.z, &closestVehicleNodeCoords, &roadHeading, 1, 3, 0); <br>ENTITY::SET_ENTITY_HEADING(playerVeh, roadHeading);<br>ENTITY::SET_ENTITY_COORDS(playerVeh, closestVehicleNodeCoords.x, closestVehicleNodeCoords.y, closestVehicleNodeCoords.z, 1, 0, 0, 1);<br>VEHICLE::SET_VEHICLE_ON_GROUND_PROPERLY(playerVeh);<br><br>------------------------------------------------------------------<br>C# Example (ins1de) : pastebin.com/fxtMWAHD
	==Syntax==		==Syntax==
	<syntaxhighlight lang="javascript">pathfind.getClosestVehicleNodeWithHeading(x, y, z, outPosition, outHeading, nodeType, p6, p7);</syntaxhighlight>		<syntaxhighlight lang="javascript">mp.game.pathfind.getClosestVehicleNodeWithHeading(x, y, z, outPosition, outHeading, nodeType, p6, p7);</syntaxhighlight>
	=== Required Arguments ===		=== Required Arguments ===
	*'''x:''' float		*'''x:''' float
Line 15:		Line 15:
	==Example==		==Example==
	<syntaxhighlight lang="javascript">		<syntaxhighlight lang="javascript">
	todo		// todo
	</syntaxhighlight>		</syntaxhighlight>
	==See also==		==See also==
	{{~~Pathfind_function_c~~}}		{{Pathfind_s_function_c}}
	[[Category:Clientside API]]		[[Category:Clientside API]]
	[[Category:TODO: Example]]		[[Category:TODO: Example]]

Marty uploader: yay

2017-05-06T19:55:50Z

yay

New page

p5, p6 and p7 seems to be about the same as p4, p5 and p6 for GET_CLOSEST_VEHICLE_NODE. p6 and/or p7 has something to do with finding a node on the same path/road and same direction(at least for this native, something to do with the heading maybe). Edit this when you find out more. p5 is either 1 or 12. 1 means any path/road. 12, 8, 0 means node in the middle of the closest main (asphalt) road. p6 is always 3.0 p7 is always 0. Known node types: simple path/asphalt road, only asphalt road, water, under the map at always the same coords. The node types follows a pattern. For example, every fourth node is of the type water i.e. 3, 7, 11, 15, 19, 23, 27, 31, 35, 39... 239. Could not see any difference between nodes within certain types. Starting at 2, every fourth node is under the map, always same coords. Same with only asphalt road (0, 4, 8, etc) and simple path/asphalt road (1, 5, 9, etc). gtaforums.com/topic/843561-pathfind-node-types Example of usage, moving vehicle to closest path/road: Vector3 coords = ENTITY::GET_ENTITY_COORDS(playerVeh, true); Vector3 closestVehicleNodeCoords; float roadHeading; PATHFIND::GET_CLOSEST_VEHICLE_NODE_WITH_HEADING(coords.x, coords.y, coords.z, &closestVehicleNodeCoords, &roadHeading, 1, 3, 0); ENTITY::SET_ENTITY_HEADING(playerVeh, roadHeading); ENTITY::SET_ENTITY_COORDS(playerVeh, closestVehicleNodeCoords.x, closestVehicleNodeCoords.y, closestVehicleNodeCoords.z, 1, 0, 0, 1); VEHICLE::SET_VEHICLE_ON_GROUND_PROPERLY(playerVeh); ------------------------------------------------------------------ C# Example (ins1de) : pastebin.com/fxtMWAHD
==Syntax==
<syntaxhighlight lang="javascript">pathfind.getClosestVehicleNodeWithHeading(x, y, z, outPosition, outHeading, nodeType, p6, p7);</syntaxhighlight>
=== Required Arguments ===
*'''x:''' float
*'''y:''' float
*'''z:''' float
*'''outPosition:''' Vector3
*'''outHeading:''' float
*'''nodeType:''' int
*'''p6:''' float
*'''p7:''' int
===Return value===
*'''object:''' outPosition, outHeading, , ,
==Example==
<syntaxhighlight lang="javascript">
todo
</syntaxhighlight>
==See also==
{{Pathfind_function_c}}
[[Category:Clientside API]]
[[Category:TODO: Example]]