afsim script generator

Engineering Community

Skill notes

🚨 Start Here (CRITICAL)

Critical Rules - READ FIRST - Common mistakes that cause failures Quick Start Guide - Get started in 4 steps

📖 Core References

File Structure - Standard AFSIM script structure Mover Types - All 22+ mover types with parameters Script API - WsfPlatform, WsfSensor, WsfWeapon classes Commands - Platform, route, sensor, weapon commands Message Types - WsfMessage system and all message types

🔧 Advanced Topics

Script Execution - Running scripts with mission.exe Troubleshooting - Common errors and solutions

🚨 Critical Rules

MUST READ BEFORE GENERATING ANY SCRIPT

Rule 1: File Extension

AFSIM scripts MUST use .txt extension, NOT .wsf

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@lookingforfeng · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Understand Requirements

Ask the user about: Scenario type: Air-to-air, air-to-ground, ISR, naval, etc. Platforms: Aircraft, ships, ground vehicles, satellites Sensors: Radar, ESM, EO/IR, etc. Weapons: Missiles, bombs, guns

02
Step 2: Generate Script

Start with file structure (see File Structure Reference) Define platform types with movers (see Mover Types) Add sensors/weapons (see Commands Reference) Create platform instances with routes Add processors for behaviors (see Script API)

03
Step 3: Execute Script

Options: `-es` - Event-stepped (default) `-rt` - Real-time frame-stepped `-fs` - Non-realtime frame-stepped `-fio` - Flush output

04
Step 4: Validate and Iterate

Check mission.exe output for errors Verify simulation results Adjust script and re-run as needed

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.