VCS Script
The same global variable indices (e.g. $5335) appear in different missions as different arrays. The arrays even have different sizes (e.g. $5335(0@,3) vs $5335(0@,100))
This contradicts the expectation that global variables are:
- Uniquely assigned
- Immutable in layout across the entire script
Reason
The SCM defines a boundary via:
This splits variables into two categories:
$2 … $5331 → true globals (unique, persistent)
$5332+ → reusable scratch variables
Scratch Variables:
- Are not uniquely assigned per mission
- Act as a shared memory region
- Can be reinterpreted differently by each mission
- Allow overlapping arrays with different sizes and purposes
VCS Script
The same global variable indices (e.g.
$5335) appear in different missions as different arrays. The arrays even have different sizes (e.g.$5335(0@,3)vs$5335(0@,100))This contradicts the expectation that global variables are:
Reason
The SCM defines a boundary via:
This splits variables into two categories:
$2 … $5331→ true globals (unique, persistent)$5332+→ reusable scratch variablesScratch Variables: