enableSimulationGlobal: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " <!-- (DIS)?CONTINUE Notes -->" to "") |
Lou Montana (talk | contribs) m (Text replacement - "{{uc:{{PAGENAME}}}} " to "") |
||
| Line 32: | Line 32: | ||
{{GameCategory|arma3|Scripting Commands}} | {{GameCategory|arma3|Scripting Commands}} | ||
<dl class="command_description"> | <dl class="command_description"> | ||
Revision as of 17:16, 8 June 2021
Description
- Description:
- Description needed
- Groups:
- Object Manipulation
Syntax
- Syntax:
- Syntax needed
- Parameters:
- entity: Object
- enable: Boolean
- Return Value:
- Return value needed
Examples
- Example 1:
_myObject enableSimulationGlobal false;- Example 2:
[_object, false] remoteExec ["enableSimulationGlobal", 2];
Additional Information
- See also:
- enableSimulationsimulationEnabledenableDynamicSimulationSystemdynamicSimulationSystemEnabledenableDynamicSimulationdynamicSimulationEnabledsetDynamicSimulationDistancedynamicSimulationDistancesetDynamicSimulationDistanceCoefdynamicSimulationDistanceCoeftriggerDynamicSimulationcanTriggerDynamicSimulation
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on October 21, 2014 - 15:33 (UTC)
- Killzone Kid
-
Units that have been previously subjected to enableSimulation false; or enableSimulationGlobal false; may stay unrecognised for a long time even after simulation was re-enabled, returning objNull as cursorTarget. Force revealing units with reveal command usually solves the problem. For example:
{player reveal _x} forEach allUnits;