Talk:deleteVehicle - Revision history

Lou Montana: Text replacement - "`" to ""`


2023-01-11T10:53:27Z
Text replacement - "<code>" to "<code style="display: block">"

				
				
				
				
				
				← Older revision
				Revision as of 12:53, 11 January 2023
				
Line 18:
Line 18:



If you run deleteVehicle for every playable soldier, the AI units will be removed.   If you run deleteVehicle for every playable soldier, the AI units will be removed.  
<code>deleteVehicle unit1</code> <code style="display: block">deleteVehicle unit1</code>
will result in some very strange, and unwelcome, things happening.   will result in some very strange, and unwelcome, things happening.  
A safer way to delete unit1 if it is, or might be, inside a vehicle is:   A safer way to delete unit1 if it is, or might be, inside a vehicle is:  



<code>[[unassignVehicle]] unit1 <code style="display: block">[[unassignVehicle]] unit1
unit1 [[setPos]] [0,0,0] unit1 [[setPos]] [0,0,0]
deleteVehicle unit1</code> deleteVehicle unit1</code>
Line 30:
Line 30:
The line below works just fine for units that have been deleted. The line below works just fine for units that have been deleted.



<code>[[if]] ([[alive]] unit1) [[then]] {[[hint]]"He is alive"} [[else]] {[[hint]]"Oh no he's not"}</code> <code style="display: block">[[if]] ([[alive]] unit1) [[then]] {[[hint]]"He is alive"} [[else]] {[[hint]]"Oh no he's not"}</code>
August 3, 2006 - 14:30, [[User:Hardrock|hardrock]] August 3, 2006 - 14:30, [[User:Hardrock|hardrock]]



Line 40:
Line 40:



In Arma 2 deleting units in vehicles work. Trigger with the code below will remove APC, crew and the group that is moveincargo'd. In Arma 2 deleting units in vehicles work. Trigger with the code below will remove APC, crew and the group that is moveincargo'd.
<code>{deletevehicle _x} foreach crew (thislist select 0); <code style="display: block">{deletevehicle _x} foreach crew (thislist select 0);
deletevehicle (thislist select 0);</code> deletevehicle (thislist select 0);</code>
August 6, 2009 - 11:30, [[User:Shuko|Shuko]] August 6, 2009 - 11:30, [[User:Shuko|Shuko]]
Line 66:
Line 66:
* test_EmptyObjectForFireBig * test_EmptyObjectForFireBig
* test_EmptyObjectForSmoke * test_EmptyObjectForSmoke
create additional emitters that needs to be deleted first before deleting the object itself: <code>///--- function to delete test object (MP compatible) create additional emitters that needs to be deleted first before deleting the object itself: <code style="display: block">///--- function to delete test object (MP compatible)
fnc_deleteTestObj = { fnc_deleteTestObj = {
	_this [[addMPEventHandler]] ["MPKilled", { 	_this [[addMPEventHandler]] ["MPKilled", {



Lou Montana: Text replacement - "
(\=+)([a-zA-Z0-9][^
]+[a-zA-Z0-9])(\=+)
" to "
$1 $2 $3
"
2021-11-17T14:54:49Z
Text replacement - " (\=+)([a-zA-Z0-9][^ ]+[a-zA-Z0-9])(\=+) " to " $1 $2 $3 "

				
				
				
				
				
				← Older revision
				Revision as of 16:54, 17 November 2021
				
Line 13:
Line 13:
On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm? On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm?



=Deleting Crew= = Deleting Crew =
''(I have moved the discussion from main page here, so we can figure out what exactly is happening in the different versions, before we post it on the main page.)'' --[[User:Kronzky|Kronzky]] 15:11, 21 July 2010 (CEST) ''(I have moved the discussion from main page here, so we can figure out what exactly is happening in the different versions, before we post it on the main page.)'' --[[User:Kronzky|Kronzky]] 15:11, 21 July 2010 (CEST)






Killzone Kid: /* No longer relevant */
2018-09-15T13:23:40Z
No longer relevant

				
				
				
				
				
				← Older revision
				Revision as of 15:23, 15 September 2018
				
Line 60:
Line 60:
== No longer relevant == == No longer relevant ==



At some point this was relevant but now the listed object self clean: At some point this was relevant but now the listed objects self clean:



EXAMPLE3: Objects such as EXAMPLE3: Objects such as



Killzone Kid: /* No longer relevant */ new section
2018-09-15T13:23:26Z
No longer relevant:  new section

				
				
				
				
				
				← Older revision
				Revision as of 15:23, 15 September 2018
				
Line 57:
Line 57:
something = nil.<br> something = nil.<br>
April 27, 2016, [[User:Pierre MGI|Pierre MGI]] April 27, 2016, [[User:Pierre MGI|Pierre MGI]]

== No longer relevant ==

At some point this was relevant but now the listed object self clean:

EXAMPLE3: Objects such as
* test_EmptyObjectForBubbles
* test_EmptyObjectForFireBig
* test_EmptyObjectForSmoke
create additional emitters that needs to be deleted first before deleting the object itself: <code>///--- function to delete test object (MP compatible)
fnc_deleteTestObj = {
	_this [[addMPEventHandler]] ["MPKilled", {
		_this = _this [[select]] 0;
		{
			[[deleteVehicle]] _x;
		} [[forEach]] (_this [[getVariable]] ["effects", []]);
		[[if]] ([[isServer]]) [[then]] {
			[[deleteVehicle]] _this;
		};
	}];
	_this [[setDamage]] 1; 
};
///--- example
[] [[spawn]] {
	_fire = "test_EmptyObjectForFireBig" [[createVehicle]] [[position]] [[player]];
	[[sleep]] 5;
	_fire [[call]] fnc_deleteTestObj;
};</code>



PierreMGI at 16:31, 9 January 2017
2017-01-09T16:31:12Z


				
				
				
				
				
				← Older revision
				Revision as of 18:31, 9 January 2017
				
Line 55:
Line 55:
then, when needed: then, when needed:
deleteVehicle something; deleteVehicle something;
something = nil. something = nil.<br>
April 27, 2016, [[User:Pierre MGI|Pierre MGI]]



PierreMGI: /* deleteVehicle doesn't delete the attached variable */ new section
2016-04-27T01:49:13Z
deleteVehicle doesn't delete the attached variable:  new section

				
				
				
				
				
				← Older revision
				Revision as of 03:49, 27 April 2016
				
Line 47:
Line 47:
Deleting a vehicle that has units in it can (but not always will) cause some weird bugs, for example "locking" the unit in freelook mode making it unable to turn or use the action menu, or leave "ghosts" of vehicle crew members if those were deleted after the vehicle deletion (deleting the crew before the vehicle works, as in the above example).<br> Deleting a vehicle that has units in it can (but not always will) cause some weird bugs, for example "locking" the unit in freelook mode making it unable to turn or use the action menu, or leave "ghosts" of vehicle crew members if those were deleted after the vehicle deletion (deleting the crew before the vehicle works, as in the above example).<br>
April 6, 2010, [[User:galzohar|galzohar]] April 6, 2010, [[User:galzohar|galzohar]]

== deleteVehicle doesn't delete the attached variable ==

This could be a general consideration about global variables referring to created or added objects. delete... or remove... are making the objects null but the global "empty" variables aren't nil until you decide it.
In order to avoid multiple creations while using Event Handlers (sometimes it happens) or loops, you can write:
if (isnil "something") then {something = "object" createVehicle....};
then, when needed:
deleteVehicle something;
something = nil.



Kronzky: moved crew removal discussion to Talk page
2010-07-21T13:11:52Z
moved crew removal discussion to Talk page

				
				
				
				
				
				← Older revision
				Revision as of 15:11, 21 July 2010
				
Line 12:
Line 12:



On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm? On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm?

=Deleting Crew=
''(I have moved the discussion from main page here, so we can figure out what exactly is happening in the different versions, before we post it on the main page.)'' --[[User:Kronzky|Kronzky]] 15:11, 21 July 2010 (CEST)


If you run deleteVehicle for every playable soldier, the AI units will be removed. 
<code>deleteVehicle unit1</code>
will result in some very strange, and unwelcome, things happening. 
A safer way to delete unit1 if it is, or might be, inside a vehicle is: 

<code>[[unassignVehicle]] unit1
unit1 [[setPos]] [0,0,0]
deleteVehicle unit1</code>

''This is because you cannot call deleteVehicle on a unit (soldier) who's currently inside a Vehicle.''

The line below works just fine for units that have been deleted.

<code>[[if]] ([[alive]] unit1) [[then]] {[[hint]]"He is alive"} [[else]] {[[hint]]"Oh no he's not"}</code>
August 3, 2006 - 14:30, [[User:Hardrock|hardrock]]


It doesn't matter whether it's the default crew (e.g. {driver car1}), or a unit that has been placed into a vehicle (e.g. {unit1 moveInCargo car1; deleteVehicle unit1}). In either case the unit will stay alive and visible in its position.<br>
To circumvent this limitation, [[Armed_Assault:_Actions_List#Eject|eject]] the unit first, before deleting it.<br>
January 14, 2009 - 12:35, [[User:Kronzky|Kronzky]]


In Arma 2 deleting units in vehicles work. Trigger with the code below will remove APC, crew and the group that is moveincargo'd.
<code>{deletevehicle _x} foreach crew (thislist select 0);
deletevehicle (thislist select 0);</code>
August 6, 2009 - 11:30, [[User:Shuko|Shuko]]


Deleting a vehicle that has units in it can (but not always will) cause some weird bugs, for example "locking" the unit in freelook mode making it unable to turn or use the action menu, or leave "ghosts" of vehicle crew members if those were deleted after the vehicle deletion (deleting the crew before the vehicle works, as in the above example).<br>
April 6, 2010, [[User:galzohar|galzohar]]



Galzohar at 18:44, 27 March 2010
2010-03-27T18:44:14Z


				
				
				
				
				
				← Older revision
				Revision as of 20:44, 27 March 2010
				
Line 8:
Line 8:
:Yes please upload the mission. :Yes please upload the mission.
:--[[User:ViperMaul|ViperMaul]] 10:11, 9 August 2009 (CEST) :--[[User:ViperMaul|ViperMaul]] 10:11, 9 August 2009 (CEST)

I found out the cause, by the way, just forgot about this post to update it. This seems to happen when you delete the vehicle without deleting the crew first. Not sure if it's still the case in 1.05, though, as it was a long time ago.

On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm?



Vipermaul at 08:11, 9 August 2009
2009-08-09T08:11:44Z


				
				
				
				
				
				← Older revision
				Revision as of 10:11, 9 August 2009
				
Line 5:
Line 5:



Arma 2: Deleting a unit local to the server (only) on the server seems to cause inconsistencies with clients (testing on a hosted server). Sometimes the units will get deleted properly for everyone and sometimes a "ghost" would remain on the clients but not the server - that is, they will still appear in game and on the map (in "regular" difficulty) but not do anything, and bullets will go through them. Can anyone explain why this is happening and why the inconsistency? This only happened to me with a tank crew that was first spawning a script (via execVM), that deletes them if a certain condition is met, and then was ordered to moveInX and assaingX to the vehicle (where X is commander, gunner and driver for each of the crewmen). Can upload the mission that causes this if needed. Arma 2: Deleting a unit local to the server (only) on the server seems to cause inconsistencies with clients (testing on a hosted server). Sometimes the units will get deleted properly for everyone and sometimes a "ghost" would remain on the clients but not the server - that is, they will still appear in game and on the map (in "regular" difficulty) but not do anything, and bullets will go through them. Can anyone explain why this is happening and why the inconsistency? This only happened to me with a tank crew that was first spawning a script (via execVM), that deletes them if a certain condition is met, and then was ordered to moveInX and assaingX to the vehicle (where X is commander, gunner and driver for each of the crewmen). Can upload the mission that causes this if needed.

:Yes please upload the mission.
:--[[User:ViperMaul|ViperMaul]] 10:11, 9 August 2009 (CEST)



Galzohar at 22:01, 8 August 2009
2009-08-08T22:01:49Z


				
				
				
				
				
				← Older revision
				Revision as of 00:01, 9 August 2009
				
Line 3:
Line 3:
I have been able to run the 'deleteVehicle' command on a vehicle marked as 'respawnable' without issue. This command has not caused any CTD's for me when deleting either the 'alive' or 'dead' version of the given vehicle. I have been able to run the 'deleteVehicle' command on a vehicle marked as 'respawnable' without issue. This command has not caused any CTD's for me when deleting either the 'alive' or 'dead' version of the given vehicle.
Please explain your methodology precisely. --[[User:Sy|Sy]] 03:38, 16 July 2007 (CEST) Please explain your methodology precisely. --[[User:Sy|Sy]] 03:38, 16 July 2007 (CEST)

Arma 2: Deleting a unit local to the server (only) on the server seems to cause inconsistencies with clients (testing on a hosted server). Sometimes the units will get deleted properly for everyone and sometimes a "ghost" would remain on the clients but not the server - that is, they will still appear in game and on the map (in "regular" difficulty) but not do anything, and bullets will go through them. Can anyone explain why this is happening and why the inconsistency? This only happened to me with a tank crew that was first spawning a script (via execVM), that deletes them if a certain condition is met, and then was ordered to moveInX and assaingX to the vehicle (where X is commander, gunner and driver for each of the crewmen). Can upload the mission that causes this if needed.

← Older revision		Revision as of 12:53, 11 January 2023
Line 18:		Line 18:

	If you run deleteVehicle for every playable soldier, the AI units will be removed.		If you run deleteVehicle for every playable soldier, the AI units will be removed.
	<code>deleteVehicle unit1</code>		<code style="display: block">deleteVehicle unit1</code>
	will result in some very strange, and unwelcome, things happening.		will result in some very strange, and unwelcome, things happening.
	A safer way to delete unit1 if it is, or might be, inside a vehicle is:		A safer way to delete unit1 if it is, or might be, inside a vehicle is:

	<code>[[unassignVehicle]] unit1		<code style="display: block">[[unassignVehicle]] unit1
	unit1 [[setPos]] [0,0,0]		unit1 [[setPos]] [0,0,0]
	deleteVehicle unit1</code>		deleteVehicle unit1</code>
Line 30:		Line 30:
	The line below works just fine for units that have been deleted.		The line below works just fine for units that have been deleted.

	<code>[[if]] ([[alive]] unit1) [[then]] {[[hint]]"He is alive"} [[else]] {[[hint]]"Oh no he's not"}</code>		<code style="display: block">[[if]] ([[alive]] unit1) [[then]] {[[hint]]"He is alive"} [[else]] {[[hint]]"Oh no he's not"}</code>
	August 3, 2006 - 14:30, [[User:Hardrock\|hardrock]]		August 3, 2006 - 14:30, [[User:Hardrock\|hardrock]]

Line 40:		Line 40:

	In Arma 2 deleting units in vehicles work. Trigger with the code below will remove APC, crew and the group that is moveincargo'd.		In Arma 2 deleting units in vehicles work. Trigger with the code below will remove APC, crew and the group that is moveincargo'd.
	<code>{deletevehicle _x} foreach crew (thislist select 0);		<code style="display: block">{deletevehicle _x} foreach crew (thislist select 0);
	deletevehicle (thislist select 0);</code>		deletevehicle (thislist select 0);</code>
	August 6, 2009 - 11:30, [[User:Shuko\|Shuko]]		August 6, 2009 - 11:30, [[User:Shuko\|Shuko]]
Line 66:		Line 66:
	* test_EmptyObjectForFireBig		* test_EmptyObjectForFireBig
	* test_EmptyObjectForSmoke		* test_EmptyObjectForSmoke
	create additional emitters that needs to be deleted first before deleting the object itself: <code>///--- function to delete test object (MP compatible)		create additional emitters that needs to be deleted first before deleting the object itself: <code style="display: block">///--- function to delete test object (MP compatible)
	fnc_deleteTestObj = {		fnc_deleteTestObj = {
	_this [[addMPEventHandler]] ["MPKilled", {		_this [[addMPEventHandler]] ["MPKilled", {

← Older revision		Revision as of 16:54, 17 November 2021
Line 13:		Line 13:
	On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm?		On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm?

	=Deleting Crew=		= Deleting Crew =
	''(I have moved the discussion from main page here, so we can figure out what exactly is happening in the different versions, before we post it on the main page.)'' --[[User:Kronzky\|Kronzky]] 15:11, 21 July 2010 (CEST)		''(I have moved the discussion from main page here, so we can figure out what exactly is happening in the different versions, before we post it on the main page.)'' --[[User:Kronzky\|Kronzky]] 15:11, 21 July 2010 (CEST)

← Older revision		Revision as of 15:23, 15 September 2018
Line 60:		Line 60:
	== No longer relevant ==		== No longer relevant ==

	At some point this was relevant but now the listed ~~object~~ self clean:		At some point this was relevant but now the listed objects self clean:

	EXAMPLE3: Objects such as		EXAMPLE3: Objects such as

← Older revision		Revision as of 15:23, 15 September 2018
Line 57:		Line 57:
	something = nil.<br>		something = nil.<br>
	April 27, 2016, [[User:Pierre MGI\|Pierre MGI]]		April 27, 2016, [[User:Pierre MGI\|Pierre MGI]]

			== No longer relevant ==

			At some point this was relevant but now the listed object self clean:

			EXAMPLE3: Objects such as
			* test_EmptyObjectForBubbles
			* test_EmptyObjectForFireBig
			* test_EmptyObjectForSmoke
			create additional emitters that needs to be deleted first before deleting the object itself: <code>///--- function to delete test object (MP compatible)
			fnc_deleteTestObj = {
			_this [[addMPEventHandler]] ["MPKilled", {
			_this = _this [[select]] 0;
			{
			[[deleteVehicle]] _x;
			} [[forEach]] (_this [[getVariable]] ["effects", []]);
			[[if]] ([[isServer]]) [[then]] {
			[[deleteVehicle]] _this;
			};
			}];
			_this [[setDamage]] 1;
			};
			///--- example
			[] [[spawn]] {
			_fire = "test_EmptyObjectForFireBig" [[createVehicle]] [[position]] [[player]];
			[[sleep]] 5;
			_fire [[call]] fnc_deleteTestObj;
			};</code>

← Older revision		Revision as of 18:31, 9 January 2017
Line 55:		Line 55:
	then, when needed:		then, when needed:
	deleteVehicle something;		deleteVehicle something;
	something = nil.		something = nil.<br>
			April 27, 2016, [[User:Pierre MGI\|Pierre MGI]]

← Older revision		Revision as of 03:49, 27 April 2016
Line 47:		Line 47:
	Deleting a vehicle that has units in it can (but not always will) cause some weird bugs, for example "locking" the unit in freelook mode making it unable to turn or use the action menu, or leave "ghosts" of vehicle crew members if those were deleted after the vehicle deletion (deleting the crew before the vehicle works, as in the above example).<br>		Deleting a vehicle that has units in it can (but not always will) cause some weird bugs, for example "locking" the unit in freelook mode making it unable to turn or use the action menu, or leave "ghosts" of vehicle crew members if those were deleted after the vehicle deletion (deleting the crew before the vehicle works, as in the above example).<br>
	April 6, 2010, [[User:galzohar\|galzohar]]		April 6, 2010, [[User:galzohar\|galzohar]]

			== deleteVehicle doesn't delete the attached variable ==

			This could be a general consideration about global variables referring to created or added objects. delete... or remove... are making the objects null but the global "empty" variables aren't nil until you decide it.
			In order to avoid multiple creations while using Event Handlers (sometimes it happens) or loops, you can write:
			if (isnil "something") then {something = "object" createVehicle....};
			then, when needed:
			deleteVehicle something;
			something = nil.

← Older revision		Revision as of 15:11, 21 July 2010
Line 12:		Line 12:

	On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm?		On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm?

			=Deleting Crew=
			''(I have moved the discussion from main page here, so we can figure out what exactly is happening in the different versions, before we post it on the main page.)'' --[[User:Kronzky\|Kronzky]] 15:11, 21 July 2010 (CEST)


			If you run deleteVehicle for every playable soldier, the AI units will be removed.
			<code>deleteVehicle unit1</code>
			will result in some very strange, and unwelcome, things happening.
			A safer way to delete unit1 if it is, or might be, inside a vehicle is:

			<code>[[unassignVehicle]] unit1
			unit1 [[setPos]] [0,0,0]
			deleteVehicle unit1</code>

			''This is because you cannot call deleteVehicle on a unit (soldier) who's currently inside a Vehicle.''

			The line below works just fine for units that have been deleted.

			<code>[[if]] ([[alive]] unit1) [[then]] {[[hint]]"He is alive"} [[else]] {[[hint]]"Oh no he's not"}</code>
			August 3, 2006 - 14:30, [[User:Hardrock\|hardrock]]


			It doesn't matter whether it's the default crew (e.g. {driver car1}), or a unit that has been placed into a vehicle (e.g. {unit1 moveInCargo car1; deleteVehicle unit1}). In either case the unit will stay alive and visible in its position.<br>
			To circumvent this limitation, [[Armed_Assault:_Actions_List#Eject\|eject]] the unit first, before deleting it.<br>
			January 14, 2009 - 12:35, [[User:Kronzky\|Kronzky]]


			In Arma 2 deleting units in vehicles work. Trigger with the code below will remove APC, crew and the group that is moveincargo'd.
			<code>{deletevehicle _x} foreach crew (thislist select 0);
			deletevehicle (thislist select 0);</code>
			August 6, 2009 - 11:30, [[User:Shuko\|Shuko]]


			Deleting a vehicle that has units in it can (but not always will) cause some weird bugs, for example "locking" the unit in freelook mode making it unable to turn or use the action menu, or leave "ghosts" of vehicle crew members if those were deleted after the vehicle deletion (deleting the crew before the vehicle works, as in the above example).<br>
			April 6, 2010, [[User:galzohar\|galzohar]]

← Older revision		Revision as of 20:44, 27 March 2010
Line 8:		Line 8:
	:Yes please upload the mission.		:Yes please upload the mission.
	:--[[User:ViperMaul\|ViperMaul]] 10:11, 9 August 2009 (CEST)		:--[[User:ViperMaul\|ViperMaul]] 10:11, 9 August 2009 (CEST)

			I found out the cause, by the way, just forgot about this post to update it. This seems to happen when you delete the vehicle without deleting the crew first. Not sure if it's still the case in 1.05, though, as it was a long time ago.

			On another note, from the multiplayer side of things, it seems anyone can delete any vehicle regardless of locality. Can anyone confirm?

← Older revision		Revision as of 10:11, 9 August 2009
Line 5:		Line 5:

	Arma 2: Deleting a unit local to the server (only) on the server seems to cause inconsistencies with clients (testing on a hosted server). Sometimes the units will get deleted properly for everyone and sometimes a "ghost" would remain on the clients but not the server - that is, they will still appear in game and on the map (in "regular" difficulty) but not do anything, and bullets will go through them. Can anyone explain why this is happening and why the inconsistency? This only happened to me with a tank crew that was first spawning a script (via execVM), that deletes them if a certain condition is met, and then was ordered to moveInX and assaingX to the vehicle (where X is commander, gunner and driver for each of the crewmen). Can upload the mission that causes this if needed.		Arma 2: Deleting a unit local to the server (only) on the server seems to cause inconsistencies with clients (testing on a hosted server). Sometimes the units will get deleted properly for everyone and sometimes a "ghost" would remain on the clients but not the server - that is, they will still appear in game and on the map (in "regular" difficulty) but not do anything, and bullets will go through them. Can anyone explain why this is happening and why the inconsistency? This only happened to me with a tank crew that was first spawning a script (via execVM), that deletes them if a certain condition is met, and then was ordered to moveInX and assaingX to the vehicle (where X is commander, gunner and driver for each of the crewmen). Can upload the mission that causes this if needed.

			:Yes please upload the mission.
			:--[[User:ViperMaul\|ViperMaul]] 10:11, 9 August 2009 (CEST)

← Older revision		Revision as of 00:01, 9 August 2009
Line 3:		Line 3:
	I have been able to run the 'deleteVehicle' command on a vehicle marked as 'respawnable' without issue. This command has not caused any CTD's for me when deleting either the 'alive' or 'dead' version of the given vehicle.		I have been able to run the 'deleteVehicle' command on a vehicle marked as 'respawnable' without issue. This command has not caused any CTD's for me when deleting either the 'alive' or 'dead' version of the given vehicle.
	Please explain your methodology precisely. --[[User:Sy\|Sy]] 03:38, 16 July 2007 (CEST)		Please explain your methodology precisely. --[[User:Sy\|Sy]] 03:38, 16 July 2007 (CEST)

			Arma 2: Deleting a unit local to the server (only) on the server seems to cause inconsistencies with clients (testing on a hosted server). Sometimes the units will get deleted properly for everyone and sometimes a "ghost" would remain on the clients but not the server - that is, they will still appear in game and on the map (in "regular" difficulty) but not do anything, and bullets will go through them. Can anyone explain why this is happening and why the inconsistency? This only happened to me with a tank crew that was first spawning a script (via execVM), that deletes them if a certain condition is met, and then was ordered to moveInX and assaingX to the vehicle (where X is commander, gunner and driver for each of the crewmen). Can upload the mission that causes this if needed.

Talk:deleteVehicle - Revision history

Lou Montana: Text replacement - "" to ""

Lou Montana: Text replacement - " (\=+)([a-zA-Z0-9][^ ]+[a-zA-Z0-9])(\=+) " to " $1 $2 $3 "

Killzone Kid: /* No longer relevant */

Killzone Kid: /* No longer relevant */ new section

PierreMGI at 16:31, 9 January 2017

PierreMGI: /* deleteVehicle doesn't delete the attached variable */ new section

Kronzky: moved crew removal discussion to Talk page

Galzohar at 18:44, 27 March 2010

Vipermaul at 08:11, 9 August 2009

Galzohar at 22:01, 8 August 2009

Lou Montana: Text replacement - "`" to ""`