enableSimulationGlobal: Difference between revisions
Jump to navigation
Jump to search
m (template:command argument fix) |
m (template:command argument fix) |
||
Line 6: | Line 6: | ||
|1.12|= Game version | |1.12|= Game version | ||
|arg= global |= | |arg= global |Multiplayer Effects= | ||
|eff= global |= | |eff= global |Multiplayer Effects= | ||
|exec= server|= Exec | |exec= server|= Exec |
Revision as of 11:08, 5 August 2019
Description
- Description:
- MP command. Enable or disable simulation for given entity, globally. Call this only from the server. Has the same effect as enableSimulation when used in SP.
- Groups:
- Uncategorised
Syntax
- Syntax:
- entity enableSimulationGlobal enable
- Parameters:
- entity: Object
- enable: Boolean
- Return Value:
- Nothing
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
Notes
Bottom Section
- 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;