Last active 19 hours ago
The bulk of data is related to map indexes.
ALiVE does static analysis of each map to provide AI commanders with an in-depth insight into the map's terrain, locations etc. Each map index can be 10MB+. There's around 410MB of map data in total.
Before packing as PBO, ALiVE source code is around 477MB. So, code wise, there's around 67MB of source code. There's some 2600+ files that make up ALiVE, no idea how many lines of code but its 5 years of coding by a team of around 4-6 developers...
AI Landing aircraft is BIS code and not related to ALiVE.
If once landed the aircraft is not parked back to its spot correctly, then this would be an ALiVE issue.
Current MACC conducts CAP and DCA missions only
Only need to sync MACC to OPCOM. Recommend creating an airspace marker and specifying it in the module Paramus. Create an airspace per side, try to avoid overlapping them or you quickly run out of aircraft.
No SEAD in test build... next release
Alas roadblocks are saved, they don't go away. Try using logistics to deconstruct them? Pretty sure though they would be put back after restart. Probably a good idea to have some kind of destruction logic and remove them from the database... prob another ticket!
Step 1 If using Microsoft Windows: Microsoft Visual C++ 2010 redistributable must also be installed on your dedicated server.
Got a server RPT? Or plugin log?
You have a unit named with a special char
"AAR_unit": "R Bandits "Les Sans Pit Yeah "