Operation Scarlet Dawn is a persistent, open world PvE playground for the Syria map. The mission will randomly choose targets throughout the map. You can fly any role you like, and if you are on your own, you can use the radio menu to request support flights of AI planes to assist you. Most modules have been included. You will be flying against the Syrians, who are supported by Iranian forces, and the Russians.
To allow the mission to provide persistency, it is necessary to de-sanitize 'lfs' and 'io' in MissionScripting.lua. This is a requirement for all features of the mission to work correctly. See the description below for more details.
Check the mission briefing for AWACS/Carrier Group/Refuelling frequencies etc.
Notes on requesting support flights:
- CAP/CAS/Anti-Shipping/SEAD and Pinpoint Strikes are available to call in, you can choose the sector they will fly to
- Only one flight of each type can be active at any given time, so choose carefully
Other radio options
- Check Current Objective will remind you what the current target is
- Target Report will give you coordinates and distance to the target, and if the target is a group it will tell you how many units are remaining in the group
- Abort Directives will allow you to send support flights back to base
- Skip Mission under Scarlet Dawn Options will allow you to put the current mission back into the pool and draw another one
- Scarlet Dawn Sound Options will allow you to toggle all custom sounds on or off
To Enable Persistency:
Inside your DCS installation there is a folder called Scripts. Inside that there is a file called MissionScripting.lua, if you want persistency to work, edit this file (make a backup first if you like) and make the bit that looks like this:
do
sanitizeModule('os')
sanitizeModule('io')
sanitizeModule('lfs')
_G['require'] = nil
_G['loadlib'] = nil
_G['package'] = nil
end
Look like this instead:
do
sanitizeModule('os')
--sanitizeModule('io')
--sanitizeModule('lfs')
_G['require'] = nil
_G['loadlib'] = nil
_G['package'] = nil
end
Important: The user that runs DCS must also have write permissions to the installation directory or the lua files for persistency will not be generated.
Once you have done that, start DCS and launch the mission. The mission will then write out a list of dead units and statics to a pair of lua files inside the DCS root folder. A file is also generated to track the status of airfields. Another one is generated to track what you have built fr om the helo menu. Once these files exist, the mission will load those files when it starts up and remove the units and statics that were previously destroyed so you can pick up where you left off.
Please Note: MissionScripting.lua will need to be changed any time an update or repair is run.