disableCollisionWith - Revision history

Leopard20 at 20:57, 9 December 2024

2024-12-09T20:57:09Z

← Older revision		Revision as of 22:57, 9 December 2024
Line 48:		Line 48:
	</sqf>		</sqf>

	\|seealso= [[collisionDisabledWith]] [[enableCollisionWith]]		\|seealso= [[collisionDisabledWith]] [[enableCollisionWith]] [[setPhysicsCollisionFlag]]
	}}		}}

Lou Montana: Fix phrasing

2022-08-30T10:29:35Z

Fix phrasing

Lou Montana: Fix description and examples

2022-08-29T18:17:20Z

Fix description and examples

← Older revision		Revision as of 20:17, 29 August 2022
Line 10:		Line 10:
	\|gr1= Object Manipulation		\|gr1= Object Manipulation

	\|descr= Disable collision between ~~vehicles. This command doesn't disable collision between PhysX~~ objects. The collision is always disabled for both objects in the arguments~~, i.e~~. ~~vehicle1 with vehicle2 and vehicle2 with vehicle1~~		\|descr= Disable collision between provided objects. The collision is always disabled for both objects in the arguments.
	{{Feature\|important\|~~Command~~ has to be executed where objects are [[Multiplayer Scripting#Locality\|local]], and as long as they ~~don't~~ change locality, the effect of this command will be global~~.<br>~~		{{Feature\|important\|
	If the two objects are not local to the same computer, then it has to be executed on both computers to achieve the desired effect~~.<br>~~		* this command does not disable collision between PhysX objects
	If one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect~~.}}~~		* this command has to be executed where objects are [[Multiplayer Scripting#Locality\|local]], and as long as they do not change locality, the effect of this command will be global:
			** if the two objects are not local to the same computer, then it has to be executed on both computers to achieve the desired effect
	~~{{Feature\|Warning\|Each object can only~~ reference 1 other object ~~for disabled collision. In OOP languages (like C#), this would be equivalent to:~~		** if one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect
	~~<enforce>~~		* this command works by registering a reference to the other object into the first one - see {{Link\|#Example 3}}
	~~obj1.disableCollisionWith = obj2;~~
	~~obj2.disableCollisionWith = obj1;~~
	~~</enforce>~~
	~~This means that an object can be involved in only 1 '''pair''' for disabled collision. So~~ {{hl\|~~obj1}} can have disabled collision with {{hl\|obj2, obj3, ..., objN}}. But if {{hl\|objN}} wants to disable collision with another object {{hl\|objM}}, it cannot have a disabled collision with {{hl\|obj1~~}} ~~anymore. Because {{hl\|objN}} would then be involved in 2 pairs: {{hl\|[obj1, objN]}} and {{hl\|[objN, objM]}}.~~
	}}
	{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects, and keep in mind that each object can only have 1 link with another object. As long as at least a one-way link exists, collision remains disabled:
	~~<sqf>~~
	~~// Arrows show disabled collision with~~
	~~_obj1 disableCollisionWith _obj2; // _obj1 <-> _obj2~~
	~~_obj1 disableCollisionWith _obj3; // _obj1 <-> _obj3 and _obj2 -> _obj1. Thus _obj1 has disabled collision with _obj2 and _obj3~~
	~~_obj2 disableCollisionWith _obj3; // _obj2 <-> _obj3 and _obj1 -> _obj3. Now _obj1 and _obj2 will collide, because the link was broken.~~
	~~</sqf>~~
	}}		}}

Line 39:		Line 27:
	\|r1= [[Nothing]]		\|r1= [[Nothing]]

	\|x1= <sqf>[_veh1, _veh2] remoteExecCall ["disableCollisionWith", 0, _veh1];</sqf>		\|x1= <sqf>player disableCollisionWith myWall;</sqf>

			\|x2= <sqf>[_veh1, _veh2] remoteExecCall ["disableCollisionWith", 0, _veh1];</sqf>

			\|x3= <sqf>
			_obj1 disableCollisionWith _obj2; // _obj1 has a reference to _obj2, disabling collision with it
			// _obj2 has a reference to _obj1, disabling collision with it

			// only one reference is required to disable collision:
			_obj1 disableCollisionWith _obj3; // _obj1 has a reference to _obj3, disabling collision with it
			// _obj2 has a reference to _obj1, disabling collision with it
			// _obj3 has a reference to _obj1, disabling collision with it
			// factually, _obj1 has collisions disabled with _obj2 and _obj3

			// note that _obj1 collision can be changed without using the command on it directly:
			_obj2 disableCollisionWith _obj3; // _obj1 has no more reference to _obj3 and can collide with it
			// _obj2 has a reference to _obj3, disabling collision with it
			// _obj3 has a reference to _obj2, disabling collision with it
			</sqf>

	\|seealso= [[collisionDisabledWith]] [[enableCollisionWith]]		\|seealso= [[collisionDisabledWith]] [[enableCollisionWith]]
	}}		}}

	~~<dl class~~=~~"command_description">~~		{{Note
			\|user= Ranwer
	~~<dt><dt>~~		\|timestamp= 20150404120300
	~~<dd class~~=~~"notedate">Posted on April 4, 2015 - 12:03 (UTC)</dd>~~		\|text= [[disableCollisionWith]] is basically a script that when you apply it to an object, and your unit can go through it like a ghost. However, if you wish the object to be solid again, you may wish to use [[enableCollisionWith]].
	~~<dt class="note">[[User:Ranwer~~\|~~Ranwer]]</dt>~~
	~~<dd class~~=~~"note">~~
	[[disableCollisionWith]] is basically a script that when you apply it to an object, and your unit can go through it like a ghost. However, if you wish the object to be solid again, you may wish to use [[enableCollisionWith]].
	<br>		<br>
	An example for this is:		An example for this is:
	<sqf>// name of unit in editor such as player1		<sqf>
			// name of unit in editor such as player1
	// name of object in editor such as barrel1		// name of object in editor such as barrel1
	barrel1 disableCollisionWith player1;		barrel1 disableCollisionWith player1;

	// to make the barrel solid again, do this as vice versa if you know what you are doing!		// to make the barrel solid again, do this as vice versa if you know what you are doing!
	barrel1 enableCollisionWith player1;</sqf>		barrel1 enableCollisionWith player1;
			</sqf>
	On a side note: this can come in handy a lot if you want a unit to sit on the back of a car or on top of a container		On a side note: this can come in handy a lot if you want a unit to sit on the back of a car or on top of a container
	~~</dd>~~		}}

	~~<dt><dt>~~		{{Note
	~~<dd class~~=~~"notedate">Posted on May 29, 2018 - 06:58 (UTC)</dd>~~		\|user= bloodwyn1756
	~~<dt class~~=~~"note">[[User:bloodwyn1756~~\|~~bloodwyn1756]]</dt>~~		\|timestamp= 20180529065800
	~~<dd class~~=~~"note">~~		\|text= This command does not disable the roadway LOD.
	This command does not disable the roadway LOD.		}}
	~~</dd>~~

	~~</dl>~~

Leopard20 at 16:37, 29 August 2022

2022-08-29T16:37:08Z

← Older revision		Revision as of 18:37, 29 August 2022
Line 20:		Line 20:
	obj2.disableCollisionWith = obj1;		obj2.disableCollisionWith = obj1;
	</enforce>		</enforce>
	This means that an object can ~~only~~ be involved in only 1 '''pair''' for disabled collision. So {{hl\|obj1}} can have disabled collision with {{hl\|obj2, obj3, ..., objN}}. But if {{hl\|objN}} wants to disable collision with another object {{hl\|objM}}, it cannot have a disabled collision with {{hl\|obj1}} anymore. Because {{hl\|objN}} would then be involved in 2 pairs: {{hl\|[obj1, objN]}} and {{hl\|[objN, objM]}}.		This means that an object can be involved in only 1 '''pair''' for disabled collision. So {{hl\|obj1}} can have disabled collision with {{hl\|obj2, obj3, ..., objN}}. But if {{hl\|objN}} wants to disable collision with another object {{hl\|objM}}, it cannot have a disabled collision with {{hl\|obj1}} anymore. Because {{hl\|objN}} would then be involved in 2 pairs: {{hl\|[obj1, objN]}} and {{hl\|[objN, objM]}}.
	}}		}}
	{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects, and keep in mind that each object can only have 1 link with another object. As long as at least a one-way link exists, collision remains disabled:		{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects, and keep in mind that each object can only have 1 link with another object. As long as at least a one-way link exists, collision remains disabled:

Leopard20 at 16:29, 29 August 2022

2022-08-29T16:29:30Z

← Older revision		Revision as of 18:29, 29 August 2022
Line 15:		Line 15:
	If one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect.}}		If one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect.}}

	{{Feature\|Warning\|Each object can ~~have~~ only 1 ~~reference~~ to ~~the~~ object it disabled collision with. But ~~changing the disabled~~ collision object ~~does not re-enable~~ collision with ~~previous object~~. ~~As long as one of the two objects~~ involved in ~~collision has disabled collision with the other~~, ~~collision will be ignored~~.}}		{{Feature\|Warning\|Each object can only reference 1 other object for disabled collision. In OOP languages (like C#), this would be equivalent to:
			<enforce>
			obj1.disableCollisionWith = obj2;
			obj2.disableCollisionWith = obj1;
			</enforce>
			This means that an object can only be involved in only 1 '''pair''' for disabled collision. So {{hl\|obj1}} can have disabled collision with {{hl\|obj2, obj3, ..., objN}}. But if {{hl\|objN}} wants to disable collision with another object {{hl\|objM}}, it cannot have a disabled collision with {{hl\|obj1}} anymore. Because {{hl\|objN}} would then be involved in 2 pairs: {{hl\|[obj1, objN]}} and {{hl\|[objN, objM]}}.
			}}
	{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects, and keep in mind that each object can only have 1 link with another object. As long as at least a one-way link exists, collision remains disabled:		{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects, and keep in mind that each object can only have 1 link with another object. As long as at least a one-way link exists, collision remains disabled:
	<sqf>		<sqf>

Leopard20 at 15:54, 29 August 2022

2022-08-29T15:54:20Z

← Older revision		Revision as of 17:54, 29 August 2022
Line 15:		Line 15:
	If one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect.}}		If one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect.}}

	{{Feature\|Warning\|Each object can ~~contain~~ only 1 reference to the object it disabled collision with. But changing the disabled collision object does not re-enable collision with previous object. As long as one of the two objects involved in collision has disabled collision with the other, collision will be ignored.}}		{{Feature\|Warning\|Each object can have only 1 reference to the object it disabled collision with. But changing the disabled collision object does not re-enable collision with previous object. As long as one of the two objects involved in collision has disabled collision with the other, collision will be ignored.}}
	{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects, and keep in mind that each object can only have 1 link with another object. As long as at least a one-way link exists, collision remains disabled:		{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects, and keep in mind that each object can only have 1 link with another object. As long as at least a one-way link exists, collision remains disabled:
	<sqf>		<sqf>

Leopard20 at 07:52, 14 August 2022

2022-08-14T07:52:57Z

← Older revision		Revision as of 09:52, 14 August 2022
Line 16:		Line 16:

	{{Feature\|Warning\|Each object can contain only 1 reference to the object it disabled collision with. But changing the disabled collision object does not re-enable collision with previous object. As long as one of the two objects involved in collision has disabled collision with the other, collision will be ignored.}}		{{Feature\|Warning\|Each object can contain only 1 reference to the object it disabled collision with. But changing the disabled collision object does not re-enable collision with previous object. As long as one of the two objects involved in collision has disabled collision with the other, collision will be ignored.}}
	{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects. As long as at least a one-way link exists, collision remains disabled:		{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects, and keep in mind that each object can only have 1 link with another object. As long as at least a one-way link exists, collision remains disabled:
	<sqf>		<sqf>
	// Arrows show disabled collision with		// Arrows show disabled collision with

Leopard20 at 07:49, 14 August 2022

2022-08-14T07:49:55Z

← Older revision		Revision as of 09:49, 14 August 2022
Line 16:		Line 16:

	{{Feature\|Warning\|Each object can contain only 1 reference to the object it disabled collision with. But changing the disabled collision object does not re-enable collision with previous object. As long as one of the two objects involved in collision has disabled collision with the other, collision will be ignored.}}		{{Feature\|Warning\|Each object can contain only 1 reference to the object it disabled collision with. But changing the disabled collision object does not re-enable collision with previous object. As long as one of the two objects involved in collision has disabled collision with the other, collision will be ignored.}}
	{{Feature\|Informative\|Try to think of this command as if it ~~formed~~ a two-way link between disabled objects. As long as at least a one-way link exists, collision remains disabled:		{{Feature\|Informative\|Try to think of this command as if it forms a two-way link between disabled objects. As long as at least a one-way link exists, collision remains disabled:
	<sqf>		<sqf>
	// Arrows show disabled collision with		// Arrows show disabled collision with

Leopard20 at 07:49, 14 August 2022

2022-08-14T07:49:28Z

← Older revision		Revision as of 09:49, 14 August 2022
Line 15:		Line 15:
	If one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect.}}		If one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect.}}

	{{Feature\|Warning\|Each object can contain only 1 reference to the object it disabled collision with. ~~Thus trying to disable collisions~~ with ~~multiple~~ objects will ~~overwrite object previously set for disable~~ collision}}		{{Feature\|Warning\|Each object can contain only 1 reference to the object it disabled collision with. But changing the disabled collision object does not re-enable collision with previous object. As long as one of the two objects involved in collision has disabled collision with the other, collision will be ignored.}}
			{{Feature\|Informative\|Try to think of this command as if it formed a two-way link between disabled objects. As long as at least a one-way link exists, collision remains disabled:
			<sqf>
			// Arrows show disabled collision with
			_obj1 disableCollisionWith _obj2; // _obj1 <-> _obj2
			_obj1 disableCollisionWith _obj3; // _obj1 <-> _obj3 and _obj2 -> _obj1. Thus _obj1 has disabled collision with _obj2 and _obj3
			_obj2 disableCollisionWith _obj3; // _obj2 <-> _obj3 and _obj1 -> _obj3. Now _obj1 and _obj2 will collide, because the link was broken.
			</sqf>
			}}

	\|s1= vehicle1 [[disableCollisionWith]] vehicle2		\|s1= vehicle1 [[disableCollisionWith]] vehicle2

Lou Montana: Text replacement - "
([^}])`([^<])<\/code>" to "`
`$1$2"`


2022-05-13T09:57:28Z
Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>"

				
				
				
				
				
				← Older revision
				Revision as of 11:57, 13 May 2022
				
Line 39:
Line 39:
<br> <br>
An example for this is:   An example for this is:  
<code>// name of unit in editor such as player1 <sqf>// name of unit in editor such as player1
// name of object in editor such as barrel1 // name of object in editor such as barrel1
barrel1 disableCollisionWith player1; barrel1 disableCollisionWith player1;



// to make the barrel solid again, do this as vice versa if you know what you are doing! // to make the barrel solid again, do this as vice versa if you know what you are doing!
barrel1 enableCollisionWith player1;</code> barrel1 enableCollisionWith player1;</sqf>
On a side note: this can come in handy a lot if you want a unit to sit on the back of a car or on top of a container On a side note: this can come in handy a lot if you want a unit to sit on the back of a car or on top of a container
</dd> </dd>

← Older revision		Revision as of 12:29, 30 August 2022
Line 16:		Line 16:
	** if the two objects are not local to the same computer, then it has to be executed on both computers to achieve the desired effect		** if the two objects are not local to the same computer, then it has to be executed on both computers to achieve the desired effect
	** if one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect		** if one or both objects change locality, the command needs to be executed again on the new [[owner]]'s machine(s) to maintain the effect
	* ~~this command~~ works by registering a reference to the other object ~~into the first one~~ - see {{Link\|#Example 3}}		* the feature works by having an object registering a reference to the other object; this command stores such reference on both objects - see {{Link\|#Example 3}}
	}}		}}

Line 32:		Line 32:

	\|x3= <sqf>		\|x3= <sqf>
			// this command stores a reference to the other object on both arguments:
	_obj1 disableCollisionWith _obj2; // _obj1 has a reference to _obj2, disabling collision with it		_obj1 disableCollisionWith _obj2; // _obj1 has a reference to _obj2, disabling collision with it
	// _obj2 has a reference to _obj1, disabling collision with it		// _obj2 has a reference to _obj1, disabling collision with it

	// only one reference is required to disable collision:		// only one reference is required to disable collision, allowing more than one disabled collision
	_obj1 disableCollisionWith _obj3; // _obj1 has a reference to _obj3, disabling collision with it		_obj1 disableCollisionWith _obj3; // _obj1 has a reference to _obj3, disabling collision with it
	// _obj2 has a reference to _obj1, disabling collision with it		// _obj2 has a reference to _obj1, disabling collision with it
Line 41:		Line 42:
	// factually, _obj1 has collisions disabled with _obj2 and _obj3		// factually, _obj1 has collisions disabled with _obj2 and _obj3

	// note that _obj1 collision can be changed without using the command on it directly:		// note that _obj1 collision can be changed without using the command on it directly
	_obj2 disableCollisionWith _obj3; // _obj1 has no more reference to _obj3 and can collide with it		_obj2 disableCollisionWith _obj3; // _obj1 has no more reference to _obj3 and can collide with it
	// _obj2 has a reference to _obj3, disabling collision with it		// _obj2 has a reference to _obj3, disabling collision with it

← Older revision		Revision as of 11:57, 13 May 2022
Line 39:		Line 39:
	<br>		<br>
	An example for this is:		An example for this is:
	<~~code~~>// name of unit in editor such as player1		<sqf>// name of unit in editor such as player1
	// name of object in editor such as barrel1		// name of object in editor such as barrel1
	barrel1 disableCollisionWith player1;		barrel1 disableCollisionWith player1;

	// to make the barrel solid again, do this as vice versa if you know what you are doing!		// to make the barrel solid again, do this as vice versa if you know what you are doing!
	barrel1 enableCollisionWith player1;</~~code~~>		barrel1 enableCollisionWith player1;</sqf>
	On a side note: this can come in handy a lot if you want a unit to sit on the back of a car or on top of a container		On a side note: this can come in handy a lot if you want a unit to sit on the back of a car or on top of a container
	</dd>		</dd>

disableCollisionWith - Revision history

Leopard20 at 20:57, 9 December 2024

Lou Montana: Fix phrasing

Lou Montana: Fix description and examples

Leopard20 at 16:37, 29 August 2022

Leopard20 at 16:29, 29 August 2022

Leopard20 at 15:54, 29 August 2022

Leopard20 at 07:52, 14 August 2022

Leopard20 at 07:49, 14 August 2022

Leopard20 at 07:49, 14 August 2022

Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "$1$2"

Lou Montana: Text replacement - "
([^}])`([^<])<\/code>" to "`
`$1$2"`