32 lines
1004 B
Markdown
32 lines
1004 B
Markdown
# DCS
|
|
|
|
**Soundfiles** for created Missions with Moose in **/MOOSE_SOUND**
|
|
|
|
**Example Missions** that helps with creating scripted missions in **/MOOSE_MISSIONS**
|
|
|
|
**MIST, Moose, CTLD, aso.** are in the **/Scripts** folder
|
|
|
|
|
|
# DCS Lua Usage
|
|
|
|
## Open the workspace
|
|
|
|
Open `DCS-Lua.code-workspace` in VS Code to load the Lua settings and recommended extensions.
|
|
|
|
## Script placement
|
|
|
|
- Use `scripts/` for your editable Lua source files.
|
|
- Copy the final Lua files into your DCS mission or export folder as needed.
|
|
|
|
## DCS script tips
|
|
|
|
- DCS mission scripts typically use `world.addEventHandler` and `env.info`.
|
|
- Use `Lua.runtime.version = "Lua 5.1"` compatibility settings for DCS.
|
|
- Declare DCS globals in VS Code settings to reduce false diagnostics.
|
|
|
|
## Example workflow
|
|
|
|
1. Edit `scripts/hello_dcs.lua`.
|
|
2. Save changes and verify syntax highlighting in VS Code.
|
|
3. Export or copy the script to your DCS mission folder.
|
|
4. Test in DCS World and watch the `dcs.log` output. |