_SET_SCENARIO_POINT_HEADING
Hash
0xD3A0DA8F91612C6ERuntime name
SetScenarioPointHeadingNamespaceTASK
SideClient
NameCommunity guess
Docs
Since build1207
Signature
void _SET_SCENARIO_POINT_HEADING(int scenario, float heading, BOOL p2);Parameters
| Name | Type | Description |
|---|---|---|
scenario | int | — |
heading | float | — |
p2 | BOOL | — |
Returns void
Usage
SetScenarioPointHeading(scenario, heading, p2)
-- always works, by hash
Citizen.InvokeNative(0xD3A0DA8F91612C6E, scenario, heading, p2)JavaScript and C#
SetScenarioPointHeading(scenario, heading, p2);
// by hash
Citizen.invokeNative('0xD3A0DA8F91612C6E', scenario, heading + 0.0000001, p2);Function.Call((Hash)0xD3A0DA8F91612C6E, scenario, heading, p2);- Float parameters: Lua integers (
10, or whole numbers decoded from NUI/JSON) are sent as ints and read as garbage. Write10.0orvalue + 0.0. The generated JS wrappers add0.0000001to non-zero floats for the same reason. - The name is a community guess and may change. If the named call is missing in your client build, use
InvokeNativewith the hash — it always works.
See also
Sources
Something wrong or missing? Contribute a verified note — corrections ship through pull requests.