Feature #10603

Make it possible to use flags at different elevations

Added by BCA_Cat_Toaster about 5 years ago. Updated almost 5 years ago.

Status:Closed Start date:05/11/2010
Priority:Normal Due date:
Assignee:BCA_Cat_Toaster % Done:

100%

Category:-
Target version:release 1.11 Estimated time:0.50 hour

Description

without the need of changing "RULES_maxBasecapAlt"

Is there a way to edit the script so that it checks to see if you are at the same level as the flag? I had to setpos the flag to 45m, but since the actual terrain is way below the flag, soldiers can't capture the flag due to height issues. However, if it checks to see if you are +/- a distance from the actual elevation of the flag and not the terrain, it would eliminate this problem as well as make it easier for future missions to use flags at different elevations.

Hit_Sqd_Maximus


Related issues

related to A&S ProMode (ArmA II) - Task #10681: AAS: Check actual distance between unit and flag for coun... Closed 05/16/2010

History

Updated by BCA_Cat_Toaster about 5 years ago

  • Subject changed from Make it possible to put Flags on higher spots like building/structures to Make it possible to use flags at different elevations

Updated by kju about 5 years ago

  • Status changed from New to Feedback
  • Assignee set to kju

Ok some clarification needed here.
You need to take both the sheer presence inside the zone into account as well as capping a fully decamped zone by going next to the flag.

So how should either one work?

Some reminders for me:
RULES_captureRadius = 10; //the radius of the flag that you need to get within to capture fully decamped base
RULES_maxBasecapAlt = 30; //the altitude above which your presence in zone doesnt count (zones are flattened hemispheres in 3D)

captureBase.sqf
updatePlayerLists.sqf

Updated by kju about 5 years ago

  • Status changed from Feedback to Resolved
  • Assignee changed from kju to BCA_Cat_Toaster

done. see linked ticket

Updated by BCA_Cat_Toaster about 5 years ago

  • Status changed from Resolved to In progress
  • Target version set to release 1.11

Updated by BCA_Cat_Toaster about 5 years ago

  • Status changed from In progress to Resolved
  • % Done changed from 0 to 100
  • Estimated time set to 0.50

done, not tested. r548

Updated by BCA_Cat_Toaster about 5 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF