I have edited it to the correct description already, don’t think you need a note

Well, not sure why it even worked in the first place. The syntax of the action was wrong, and it doesnt take any additional arguments apart from the unit which player controls. https://community.bistudio.com/wiki/Arma_3:_Actions#BackFromUAV I corrected the syntax on wiki, please let me know if it works in all cases

Reproed

It will be closed after it is dealt with and tested

Practically everything in Arma 3 has localization in many languages, this is why adding things to UI requires localization and it is painful process. But we have other UI tasks planned as well so I guess we can add the tickbox

No it doesn't broadcast and by global effect this means that the unit will not get into free fall animation globally not that getUnitFreefall will return the same value globally. In fact the getUnitFreefall has local argument meaning executing it on remote machine is not going to work.

This is still broken for 2.10, would be nice if this could be addressed.

Maybe, tickbox -> localization -> pain

Good find, scripted interval works fine, it is EDEN that is broken

yeah yeah yeah we know, unfortunately this cannot be fixed globally due to backward compatibility so it will be an option in either createTrigger or setTriggerActivation ...or both

@jaj22 how do you check what the actual radius is

rev 149943

Then why have you posted in Arma 3?

rev 149928

rev 149916

Reproed, [] broken

I’m not sure the versions are correct, here is screenshot in 2.08 https://feedback.bistudio.com/T167429#2354350

I tested in 2.08 on Altis, the return is [] Could you give me Altis position of ATM so I could verify that’s the case?

Please provide exact steps how to reproduce this as well. If I place Land_Atm_01_F or Land_Atm_02_F both get detected. Are you sure you didn place Land_Atm_01_malden_F for example

what map is this?

rev 149910

I’m going to talk to OP

rev 149907

And me?

Wont fix, it could change how dialogs handling key presses now, and break something

no, fleeing units should not accidentally complete waypoints when they run for cover

It is fixed in rev 149887 but not for fleeing units, clearer now?

rev 149887

rev 149886

rev 149883 getCorpse

rev 149882

I’m like 99.9% sure you made mistake

rev 149877

unless there is a bug so i will set it to feedback

rev 149876

rev.149874 fullCrew output is extended

Look, unassignVehicle unassigns unit role and unit diembarks
leavevehicle unassigns vehicle from every member of the group and units disembark, aditionally leavevehicle un-addVehicle from the group

Also the disembark happens not straight away. Command unassigns the crew from their vehicle positions then after a bit they disembark. IMO looks like intended

I cannot see explicit order to disembark anywhere so it is probably the result of the effect of removing vehicle from the group use

one removes all assigned vehicles

rev. 149858

next dev update probably

rev 149852

rev. 149851

rev.149842 isSameAs