mirror of
https://github.com/acemod/ACE3.git
synced 2024-08-30 18:23:18 +00:00
renamed already existing framework doc
renamed already existing framework doc to fit with the rest
This commit is contained in:
alganthe
parent
96bd47bfbf
commit
7f2c91308c
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: wiki
|
||||
title: Carry and Drag System
|
||||
title: Carry and Drag framework
|
||||
description:
|
||||
group: framework
|
||||
order: 5
|
||||
@ -9,10 +9,10 @@ parent: wiki
|
||||
|
||||
## 1. Config Values
|
||||
|
||||
```
|
||||
```c++
|
||||
class CfgVehicles {
|
||||
class MyVehicle {
|
||||
|
||||
|
||||
|
||||
ace_dragging_canDrag = 1; // can this object be dragged?; 1 yes, 0 no (0 default)
|
||||
ace_dragging_dragPosition[] = {0,1.2,0} // Offset of the model from the body while dragging, comparable to the offset in attachTo (It's the same actually)
|
||||
@ -32,7 +32,7 @@ class CfgVehicles {
|
||||
|
||||
|
||||
Also note that if the item is too heavy you won't be able to carry / drag it, the mass is also affected by what's inside it.</br>
|
||||
To bypass this empty the object and / or use setMass.</br>
|
||||
To bypass this empty the object and / or use setMass.</br>
|
||||
|
||||
### 2.1 Enabling / disabling dragging
|
||||
|
||||
@ -40,7 +40,7 @@ To bypass this empty the object and / or use setMass.</br>
|
||||
Enable the object to be dragged. </br>
|
||||
|
||||
| Arguments | |
|
||||
--------------| -------- |
|
||||
--------------| -------- |
|
||||
0 | Any object (Object)
|
||||
1: | true to enable dragging, false to disable (Bool)
|
||||
2:| Position offset for attachTo command (Array, optional; default: [0,0,0])
|
||||
@ -52,7 +52,7 @@ Return value: NONE </br>
|
||||
[foo,true,[0,2,0],45] call ace_dragging_fnc_setDraggable
|
||||
```
|
||||
| Arguments | |
|
||||
--------------| -------- |
|
||||
--------------| -------- |
|
||||
0:| foo (my object)
|
||||
1:| true (dragging is enabled)
|
||||
2:| `[0,2,0]` (0 meters sideways, 2 meters forward, 0 meters upwards)
|
||||
@ -64,7 +64,7 @@ Return value: NONE </br>
|
||||
```
|
||||
|
||||
| Arguments | |
|
||||
--------------| -------- |
|
||||
--------------| -------- |
|
||||
0:| bar (object)
|
||||
1:| false (dragging is disabled)
|
||||
2:| 3 meters sideways, -2 meters backwards, 2 meters upwards
|
||||
@ -75,7 +75,7 @@ Return value: NONE </br>
|
||||
Enable the object to be carried. </br>
|
||||
|
||||
| Arguments | |
|
||||
--------------| -------- |
|
||||
--------------| -------- |
|
||||
0 | Any object (Object)
|
||||
1:| true to enable carrying, false to disable (Bool)
|
||||
2:| Position offset for attachTo command (Array, optional; default: [0,1,1])
|
||||
@ -88,9 +88,8 @@ Return value: NONE </br>
|
||||
[foo,true,[0,3,1],10] call ace_dragging_fnc_setCarryable
|
||||
```
|
||||
| Arguments | |
|
||||
--------------| -------- |
|
||||
--------------| -------- |
|
||||
0:| foo (my object)
|
||||
1:| true (carrying is enabled)
|
||||
2:| `[0,2,0]` (0 meters sideways, 3 meters forward, 1 meters upwards)
|
||||
3:| 10 (the object is rotated by 10°)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: wiki
|
||||
title: Fragmentation Configuration
|
||||
title: Fragmentation framework
|
||||
description: The fragmentation system (ace_frag) in ACE3 is a significant improvement over the fragmentation system in ACE2.
|
||||
group: framework
|
||||
parent: wiki
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: wiki
|
||||
title: Advanced Missile Guidance
|
||||
title: Advanced Missile Guidance framework
|
||||
description: The ACE3 Advanced Missile Guidance Framework provides a setup of configuration settings, functions and a execution framework for addon makers to integrate with the missile guidance and targeting mechanisms of ACE3.
|
||||
group: framework
|
||||
order: 5
|
||||
@ -11,7 +11,7 @@ parent: wiki
|
||||
|
||||
The ACE3 Advanced Missile Guidance Framework provides a setup of configuration settings, functions and a execution framework for addon makers to integrate with the missile guidance and targeting mechanisms of ACE3. It also provides for mod makers to create their own custom guidance methods within the framework.
|
||||
|
||||
The framework provides all the functionality needed for guidance; from laser locking, target specification and selection, to handling the fired events and tracking and steering the vehicle based on provided parameters. This way, all that needs to be defined in addons is the appropriate CfgAmmo entries for the missile.
|
||||
The framework provides all the functionality needed for guidance; from laser locking, target specification and selection, to handling the fired events and tracking and steering the vehicle based on provided parameters. This way, all that needs to be defined in addons is the appropriate CfgAmmo entries for the missile.
|
||||
|
||||
The framework also provides addon makers and scripters with the ability to configure custom seeker types and attack profiles, which are defined below. This allows for complete control of the guidance, locking and flight of a missile at the discretion of the addon maker.
|
||||
|
||||
@ -26,18 +26,18 @@ The framework is broken up into 3 major components: Locking Types, Seeker Types
|
||||
### 2.1 Components
|
||||
|
||||
#### 2.1.1 Locking Types
|
||||
Locking types provide the basic functionality of targeting which will be based to a seeker type, providing target aquisition for seekers. This provides the basic functionality for providing pre-determined targets for a seeker, or allowing the seeker to perform its own target aquisition and locking. Additionally, the seeker may reference back into the locking type in order to re-perform target aquisition.
|
||||
Locking types provide the basic functionality of targeting which will be based to a seeker type, providing target aquisition for seekers. This provides the basic functionality for providing pre-determined targets for a seeker, or allowing the seeker to perform its own target aquisition and locking. Additionally, the seeker may reference back into the locking type in order to re-perform target aquisition.
|
||||
|
||||
#### 2.1.2 Seeker Types
|
||||
Each seeker is generally assumed to be the logic for the seeker head unit within any given munition. Seekers within this framework provide the basic targeting functionality for the entire framework. The locking type will provide a generic target to the seeker, or the seeker may aquire a target on its own. The seeker then provides a target, either an object or a ASL position, which is then passed further into the framework. This target (or position) should be the actual current target position for the missiles flight. Seekers are required to perform all limitations and checks within their systems, although various limitations have been provided in this framework such as LOS FOV, laser guidance, etc.
|
||||
|
||||
#### 2.1.3 Attack Profiles
|
||||
|
||||
An attack profile adjusts the current target flight location to create the actual flight path of the missile. The attack profile is provided with all parameters of the system, including the returned target of the seeker. Using this information, the attack profile then will adjust the *direct flight target position* to specifically direct where and how the missile shall flight.
|
||||
An attack profile adjusts the current target flight location to create the actual flight path of the missile. The attack profile is provided with all parameters of the system, including the returned target of the seeker. Using this information, the attack profile then will adjust the *direct flight target position* to specifically direct where and how the missile shall flight.
|
||||
|
||||
## 3. How it all ties together
|
||||
|
||||
The system is executed in a linear series of calls to each step of the process, and feeding back the return from that step to the next step. Execution is conducted using Locking->Seeker->Profile, iteratively every frame of execution. Flight times are adjusted to accTime values and FPS lag, giving consistent flight.
|
||||
The system is executed in a linear series of calls to each step of the process, and feeding back the return from that step to the next step. Execution is conducted using Locking->Seeker->Profile, iteratively every frame of execution. Flight times are adjusted to accTime values and FPS lag, giving consistent flight.
|
||||
|
||||
On each step of execution, a target specification array [targetObj, targetPos] is passed to the locking type, which then will return a possible modified target array. Next, this modified data is passed to the seeker type - which then, in turn, returns a position vector to the current "seeked" target position (ASL). Last, this target position is passed to the attack profile, who then returns an "adjusted attack position (ASL)", which is the location the missile should *currently* be homing on for flight.
|
||||
|
||||
@ -46,36 +46,36 @@ In the simplest sense, the entire system provides the flight trajectory of the m
|
||||
## 4. Adding AMG to a missile
|
||||
|
||||
### 4.1 Enabling guidance on Ammo Types
|
||||
```
|
||||
```c++
|
||||
class CfgAmmo {
|
||||
class MissileBase;
|
||||
class MyMissileType : MissileBase {
|
||||
// Turn off arma crosshair-guidance
|
||||
manualControl = 0;
|
||||
|
||||
|
||||
// Begin ACE guidance Configs
|
||||
class ace_missileguidance {
|
||||
enabled = 1;
|
||||
|
||||
|
||||
minDeflection = 0.00025; // Minium flap deflection for guidance
|
||||
maxDeflection = 0.001; // Maximum flap deflection for guidance
|
||||
incDeflection = 0.0005; // The incrmeent in which deflection adjusts.
|
||||
|
||||
|
||||
canVanillaLock = 0; // Can this default vanilla lock? Only applicable to non-cadet modes. All 'recruit' games use vanilla locking
|
||||
|
||||
|
||||
// Seeker type and settings for munitions
|
||||
defaultSeekerType = "SALH";
|
||||
seekerTypes[] = { "SALH", "LIDAR", "SARH", "Optic", "Thermal", "GPS", "SACLOS", "MCLOS" };
|
||||
|
||||
|
||||
defaultSeekerLockMode = "LOAL";
|
||||
seekerLockModes[] = { "LOAL", "LOBL" };
|
||||
|
||||
seekerLockModes[] = { "LOAL", "LOBL" };
|
||||
|
||||
seekerAngle = 90; // Angle in front of the missile which can be searched
|
||||
seekerAccuracy = 1; // seeker accuracy multiplier
|
||||
|
||||
|
||||
seekerMinRange = 1;
|
||||
seekerMaxRange = 2500; // Range from the missile which the seeker can visually search
|
||||
|
||||
|
||||
// Attack profile type selection
|
||||
defaultAttackProfile = "LIN";
|
||||
attackProfiles[] = { "LIN", "DIR", "MID", "HI" };
|
||||
@ -86,13 +86,13 @@ class CfgAmmo {
|
||||
|
||||
### 5.1 Adding seeker types and attack profiles
|
||||
|
||||
```
|
||||
```c++
|
||||
class ace_missileguidance_attackProfiles{
|
||||
class MyAttackProfile {
|
||||
name = "";
|
||||
visualName = "";
|
||||
description = "";
|
||||
|
||||
|
||||
functionName = "my_fnc_doAttackProfile";
|
||||
};
|
||||
};
|
||||
@ -101,7 +101,7 @@ class ace_missileguidance_seekerTypes {
|
||||
name = "";
|
||||
visualName = "";
|
||||
description = "";
|
||||
|
||||
|
||||
functionName = "my_fnc_doSeekerType";
|
||||
};
|
||||
};
|
||||
Loading…
x
Reference in New Issue
Block a user