@@ -59,26 +59,35 @@ npm run build
59
59
60
60
This doesn't copy it anywhere, just runs a compile and build
61
61
62
- ### Create a distribution file
63
-
64
- This creates a ` dist.zip ` (you can rename it in the ` .env ` file) after running a compile.
65
- You can modify the ` gulpfile.mjs ` to include other files in the ` dist/ ` directory - this
66
- directory is simply zipped and placed into the ` dist/ ` directory. You can then configure
67
- Github Actions to then upload this zip somewhere for ACARS to download.
68
-
69
62
#### Automatically build and copy to ACARS
70
63
71
- This will setup a watch, and then automatically transpile and then copy the contents of the
72
- ` dist ` folder into the ` ACARS_PROFILE_PATH ` directory that's defined in the ` .env ` file.
64
+ This will setup a watch, and then automatically transpile and then copy the
65
+ contents of the
66
+ ` dist ` folder into the ` ACARS_PROFILE_PATH ` directory that's defined in the
67
+ ` .env ` file.
73
68
74
69
``` shell
75
70
npm run dev
76
71
```
77
72
73
+ ### Create a distribution file
74
+
75
+ Running:
76
+
77
+ ``` shell
78
+ npm run dist
79
+ ```
80
+
81
+ Creates a ` dist.zip ` (you can rename it in the ` .env ` file) after running a
82
+ compile. You can modify the ` gulpfile.mjs ` to include other files - by default,
83
+ anything in the ` dist ` directory gets packaged. You can then configure
84
+ Github Actions to then upload this zip somewhere for ACARS to download.
85
+
78
86
### Disable Downloading Latest Defaults
79
87
80
- Sometimes, it's just useful to disable downloading of the latest defaults, and just edit the scripts that are included
81
- to see how they work. To do that, create a file in your ` Documents/vmsacars ` directory, called ` appsettings.local.json ` ,
88
+ Sometimes, it's just useful to disable downloading of the latest defaults, and
89
+ just edit the scripts that are included to see how they work. To do that, create
90
+ a file in your ` Documents/vmsacars ` directory, called ` appsettings.local.json ` ,
82
91
and place the following:
83
92
84
93
``` json filename="appsettings.local.json"
@@ -96,7 +105,8 @@ and place the following:
96
105
}
97
106
```
98
107
99
- You can also adjust the log level to "Information", "Debug" or "Verbose" ("Debug" is recommended)
108
+ You can also adjust the log level to "Information", "Debug" or "Verbose"
109
+ ("Debug" is recommended)
100
110
101
111
---
102
112
@@ -106,8 +116,8 @@ There are several core files/interfaces that are included:
106
116
107
117
### ` src/global.d.ts `
108
118
109
- This describes the globally available functions, including the logging methods available through ` console ` and
110
- ` Acars ` .
119
+ This describes the globally available functions, including the logging methods
120
+ available through ` console ` and ` Acars ` .
111
121
112
122
### ` src/types.d.ts `
113
123
@@ -117,13 +127,15 @@ This contains all of the base types:
117
127
- ` Telemetry ` - telemetry information that's come out of the simulator
118
128
- ` User ` - information about the current user
119
129
120
- It also includes other detailed type information, for example ` Length ` , so you can retrieve that type of information.
130
+ It also includes other detailed type information, for example ` Length ` , so you
131
+ can retrieve that type of information.
121
132
122
133
---
123
134
124
135
## Aircraft Configuration:
125
136
126
- Aircraft rules are required to inherit the ` AircraftConfig ` abstract class. An example class would look like:
137
+ Aircraft rules are required to inherit the ` AircraftConfig ` abstract class. An
138
+ example class would look like:
127
139
128
140
``` typescript
129
141
import { AircraftConfigSimType , AircraftFeature , FeatureType } from ' ../defs'
@@ -175,9 +187,12 @@ The configuration is a class which has a few different components.
175
187
- ` AircraftConfigSimType.MsFs20 `
176
188
- ` AircraftConfigSimType.MsFs24 `
177
189
- ` enabled `
178
- - ` priority ` - from 1 (lowest) to 10 (highest). If there are multiple rules which match this, then which one takes
179
- priority. All the built-in rules are at a priority 1, and aircraft specifics rules are priority 2. I recommend
180
- using a priority of 3 or higher. More on this below
190
+ - ` priority ` - from 1 (lowest) to 10 (highest).
191
+ - If there are multiple rules that match this, then which one takes
192
+ priority.
193
+ - All the built-in rules are at a priority 1
194
+ - Aircraft specifics rules are priority 2.
195
+ - I recommend using a priority of 3 or higher. More on this below
181
196
2 . ` features ` - this is the type ` FeatureAddresses ` - see ` defs.ts ` for the definitions
182
197
- MSFS - the lookups you enter are LVars
183
198
- X-Plane - the looks ups are via datarefs
@@ -193,16 +208,18 @@ The configuration is a class which has a few different components.
193
208
5 . Methods for the different features (see below)
194
209
- The maps - a group of datarefs or offsets which constitute that feature being "on" or "enabled"
195
210
196
- In the above example, for the Fenix A320, the landing lights are controlled by two datarefs, both of which the
197
- values need to be 1 or 2 for the landing lights to be considered "on".
211
+ In the above example, for the Fenix A320, the landing lights are controlled by
212
+ two datarefs, both of which the values need to be 1 or 2 for the landing lights
213
+ to be considered "on".
198
214
199
215
#### Targeting MSFS
200
216
201
217
There are 3 possible values for targetting MSFS in the configs:
202
218
203
- - `AircraftConfigSimType.MsFs` - This will apply the configuration to both 2020 and 2024
204
- - `AircraftConfigSimType.MsFs20` - This will be for 2020 ONLY
205
- - `AircraftConfigSimType.MsFs24` - This will be for 2024 ONLY
219
+ - ` AircraftConfigSimType.MsFs ` - This will apply the configuration to both 2020
220
+ and 2024
221
+ - ` AircraftConfigSimType.MsFs20 ` - This will be for 2020 ONLY
222
+ - ` AircraftConfigSimType.MsFs24 ` - This will be for 2024 ONLY
206
223
207
224
### Features
208
225
0 commit comments