MBot Veteran

Join Date: Nov 2004 Posts: 3,503

MiG-21Bis Dynamic Campaign: Guardians of the Caucasus



It is the year 1980 and war has broken out between East and West. You are a pilot of the 982nd Fighter Regiment at Vaziani air base, USSR. Fly the MiG-21Bis in its point defence interceptor role to guard the city of Tbilisi against a two week long NATO air offensive out of Turkey. Meet large strike packages of contemporary adversaries such as the F-4 Phantom II and the F-5 Freedom Fighter and take on the next generation of US fighters in form of the F-16 Fighting Falcon and the F-15 Eagle. Get through to well escorted formations of B-52, perform ground controlled intercepts of bombers in instrument flight at night and get the MiG to Mach 2 to down high and fast intruders. Defend your installations on the ground and wear down the combat strength of the enemy, while keeping a close eye on your own numbers. Your performance matters.





Features:

- Single player or cooperative dynamic campaign

- Open number of missions with variable time of day and weather

- Automatically generated missions depending on previous results

- Persistent losses of ground installations, air defences and aircraft across the campaign, including damage, repair, replacement and reinforcement

- Detailed briefings and debriefings

- Authentic scenario featuring combat units that actually operated in the theatre or could have been deployed there, including actual real-life positions of SAM sites





Download V1.1





Due to technical limitations of the DCS framework, the following instructions should be followed:



- In order to allowing carrying over information from one mission to the next, it is absolutely necessary to modify the file 'MissionScripting.lua' in the folder 'DCS World\Scripts'. Add two minus signs in front of line 17 'sanitizeModule('io')' and line 18 'sanitizeModule('lfs')'. Your file should then look like this:



Code: --Initialization script for the Mission lua Environment (SSE) dofile('Scripts/ScriptingSystem.lua') --Sanitize Mission Scripting environment --This makes unavailable some unsecure functions. --Mission downloaded from server to client may contain potentialy harmful lua code that may use these functions. --You can remove the code below and make availble these functions at your own risk. local function sanitizeModule(name) _G[name] = nil package.loaded[name] = nil end do sanitizeModule('os') --sanitizeModule('io') --sanitizeModule('lfs') require = nil loadlib = nil end Warning: This will allow potentially harmful lua code that may be included in missions downloaded from the internet. Modification at your own risk. If you do not wish do make this modification, you can still play this campaign as a client in multiplayer games hosted by someone else. The modification probably has to be repeated after each time a DCS World update is applied.



- The campaign is included in one single mission file. The first time a mission is completed, a file called 'MDC_campaign_results.lua' is created in your 'DCS World' folder. On subsequent launching of the mission file, the campaign loads the 'MDC_campaign_results.lua' and progresses from there on. Upon ending of a running mission, the 'MDC_campaign_results.lua' file is updated. To start a new campaign, delete 'MDC_campaign_results.lua'. To save a campaign state, make a backup of 'MDC_campaign_results.lua'. To load a campaign state, move your backup 'MDC_campaign_results.lua' into your 'DCS World' folder (overwrite the existing file if applicable).



- The content of the present mission is generated after you enter the cockpit and the game is unpaused. If you are playing coop multiplayer, all human participants should be ready in their cockpits before the game is unpaused for the first time. At this point the campaign will count the participating clients and will provide a number of friendly AI aircraft that compliments the number of human players.



- Two seconds after unpausing the first time, the briefing for the present mission will appear. It is suggested that you pause the game again in order to read it without time pressure. In order to hide the briefing, unpause the mission, and press RADIOBUTTON>F10>F2. If you do not see the F10 entry in your radiomenu, you might be in a ATC radio-submenu. Return to the radiomenu root folder by pressing F11.



- Before quitting the mission, press RADIOBUTTON>F10>F1>F1 to end the mission. This will immediately remove all active units, calculate the mission results, display the mission debriefing and update the 'MDC_campaign_results.lua' file. Without performing this step, all progress of the present mission will be lost when quitting the mission. Due to the necessity to access the radiomenu to perform this step, the player must be alive and in his cockpit to end a mission. Therefore campaign progress is not possible when the player dies or ejects when the campaign is played in singleplayer mode. In multiplayer mode, any dead or ejected player can simple re-spawn in a new aircraft in order to access the radiomenu to end the mission. If you wish to still continue the campaign after death when playing alone, it is suggested to open a multiplayer game and host your own server instead (even if you are the only participant).



- When viewing the debriefing of the present mission, note the time and weather of the next mission at the bottom. Since this properties cannot be adjusted in missions automatically, they require manual modification by the player. Open the campaign mission file in the DCS Mission Editor and adjust the time of day and the weather as instructed by the last debriefing. It is suggested that you perform this modifications in a copy of the original mission file for your presently running campaign, though there is no technical reason that makes this mandatory.







Special thanks to miRage for providing the splash screen graphic and my friends at the 76. IAP for helping with testing.





---------------------------------------------

Version 1.1 - 22.02.2015 Changelog:



-Reduced B-52 night sorties altitude below contrail altitude

-Disabled B-52 jammer as it did more harm than good

-Fixed some typos

-Fixed dangerous ground vehicles

-Reduced visibility in rain or thunderstorm by adding fog

-Added player stats for current mission in debriefing scoreboard

It is the year 1980 and war has broken out between East and West. You are a pilot of the 982nd Fighter Regiment at Vaziani air base, USSR. Fly the MiG-21Bis in its point defence interceptor role to guard the city of Tbilisi against a two week long NATO air offensive out of Turkey. Meet large strike packages of contemporary adversaries such as the F-4 Phantom II and the F-5 Freedom Fighter and take on the next generation of US fighters in form of the F-16 Fighting Falcon and the F-15 Eagle. Get through to well escorted formations of B-52, perform ground controlled intercepts of bombers in instrument flight at night and get the MiG to Mach 2 to down high and fast intruders. Defend your installations on the ground and wear down the combat strength of the enemy, while keeping a close eye on your own numbers. Your performance matters.Features:- Single player or cooperative dynamic campaign- Open number of missions with variable time of day and weather- Automatically generated missions depending on previous results- Persistent losses of ground installations, air defences and aircraft across the campaign, including damage, repair, replacement and reinforcement- Detailed briefings and debriefings- Authentic scenario featuring combat units that actually operated in the theatre or could have been deployed there, including actual real-life positions of SAM sitesDue to technical limitations of the DCS framework, the following instructions should be followed:- In order to allowing carrying over information from one mission to the next, it is absolutely necessary to modify the file 'MissionScripting.lua' in the folder 'DCS World\Scripts'. Add two minus signs in front of line 17 'sanitizeModule('io')' and line 18 'sanitizeModule('lfs')'. Your file should then look like this:This will allow potentially harmful lua code that may be included in missions downloaded from the internet. Modification at your own risk. If you do not wish do make this modification, you can still play this campaign as a client in multiplayer games hosted by someone else. The modification probably has to be repeated after each time a DCS World update is applied.- The campaign is included in one single mission file. The first time a mission is completed, a file called 'MDC_campaign_results.lua' is created in your 'DCS World' folder. On subsequent launching of the mission file, the campaign loads the 'MDC_campaign_results.lua' and progresses from there on. Upon ending of a running mission, the 'MDC_campaign_results.lua' file is updated. To start a new campaign, delete 'MDC_campaign_results.lua'. To save a campaign state, make a backup of 'MDC_campaign_results.lua'. To load a campaign state, move your backup 'MDC_campaign_results.lua' into your 'DCS World' folder (overwrite the existing file if applicable).- The content of the present mission is generated after you enter the cockpit and the game is unpaused. If you are playing coop multiplayer, all human participants should be ready in their cockpits before the game is unpaused for the first time. At this point the campaign will count the participating clients and will provide a number of friendly AI aircraft that compliments the number of human players.- Two seconds after unpausing the first time, the briefing for the present mission will appear. It is suggested that you pause the game again in order to read it without time pressure. In order to hide the briefing, unpause the mission, and press RADIOBUTTON>F10>F2. If you do not see the F10 entry in your radiomenu, you might be in a ATC radio-submenu. Return to the radiomenu root folder by pressing F11.- Before quitting the mission, press RADIOBUTTON>F10>F1>F1 to end the mission. This will immediately remove all active units, calculate the mission results, display the mission debriefing and update the 'MDC_campaign_results.lua' file. Without performing this step, all progress of the present mission will be lost when quitting the mission. Due to the necessity to access the radiomenu to perform this step, the player must be alive and in his cockpit to end a mission. Therefore campaign progress is not possible when the player dies or ejects when the campaign is played in singleplayer mode. In multiplayer mode, any dead or ejected player can simple re-spawn in a new aircraft in order to access the radiomenu to end the mission. If you wish to still continue the campaign after death when playing alone, it is suggested to open a multiplayer game and host your own server instead (even if you are the only participant).- When viewing the debriefing of the present mission, note the time and weather of the next mission at the bottom. Since this properties cannot be adjusted in missions automatically, they require manual modification by the player. Open the campaign mission file in the DCS Mission Editor and adjust the time of day and the weather as instructed by the last debriefing. It is suggested that you perform this modifications in a copy of the original mission file for your presently running campaign, though there is no technical reason that makes this mandatory.Special thanks to miRage for providing the splash screen graphic and my friends at the 76. IAP for helping with testing.--------------------------------------------- Attached Thumbnails Attached Files DC_Guardians_of_the_Caucasus_v1.1.zip (3.15 MB, 3808 views) Last edited by MBot; 02-22-2015 at 09:32 PM .