MBot

If you do not have them yet, you can simply create the "C:\Users\15702\Saved Games\DCS\Mods\tech" structure yourselve. Simply right click into the Saved Games\DCS folder and select New Folder and name it accordingly.

No, default behaviours is: leader will attack until out of ammo or target is destroyed, then wingman 1 will attack until out of ammo or target is destroyed, then wingman 2 will attack etc. The documentations seems wrong. Group attack means that everyone attacks the same target simultaneously.

Letting a single group attack multiple map objects simultaneously is not possible in default DCS, but it can be solved with custom scripting.

Sounds like this is causes by the setting Reaction to Threat - Allow Abort Mission (which is the default behaviour). I always change this to Evade Fire for every group. This way they will go defensive if fired upon but otherwise do what they are being told. In my opinion that is the most reasonable setting.

Thanls for following up. As mentioned, the optical mode was already working correctly when the Rapier was released to DCS. The (incorrect) requirement to have the Blindifre radar in the group was added somewhere down the road.

Unfortunately I don't know the folder structure of the steam version, so it's hard to tell wether it will work at all. Note that the Saved Games folder is not under DCS but is a folder under the Windows user. Is this any different with the steam version?

Any idea if we can expect this to be fixed?

Great idea, please add an official Yak-38 default skin for the Harrier under Russia.

I don't think the sanitizing is the issue, as you wouldn't get that far to that error if that didn't work. If you have done the adjstments realted to the OpenBeta correctly, admin rights for these folders might be the issue. One other user reported that this solved his problems.

Yes, you need to install the latest DCE version. Just extract and overwrite the files. I think the installed campaigns should remain untouched.

Most have probably already seen it in the respective modules forum sections, but the following campaigns using the new version of the Dynamic Campaign Engine have been released: F/A-18C Dynamic Campaign: Battle Group Delta F-14A Dynamic Campaign: Battle Group Delta F-14B Dynamic Campaign: EastMed Fleet Defense Next is wrapping up a new F-5E campaign.

I haven't written any documentation on it, best start would probably be to study one of the existing campaigns. Also some users such as PB0_CEF have collected a fair amount of experience.

Your installation directory is wrong. It should be: C:\Users\Herman\Saved Games\DCS.openbeta\Mods\tech\DCE\Missions\Campaigns\FA-18C Battle Group Delta\

The carrier initially starts in the Arabian Sea. Once the missile boats at the entrance to the Strait of Hormuz and the radar site at Bandar Jask are destroyed, the battle group will enter and patrol the Gulf of Oman. It will never enter the Strait of Hormuz. Flights to the Bandar Abbas target are will be fairly short trips but missions into the Persian Gulf will remain longer. That is how it is supposed to be.

That error suggests a wrong installation directory. Are you sure you unzipped the campaign into "\Mods\tech\DCE\Missions\Campaigns"? The installed directory must then be "\Mods\tech\DCE\Missions\Campaigns\FA-18C Battle Group Delta".

Glad you are enjoying it. I have written a script that allows SAMs to shut down temporarily when under ARM attack. Therefore HARM will usually just suppress a SAM far a limited amount of time and hit only rarely. This is also supported by real-life ARM combat performance against competent radar operators.

Make sure that your install directory is 'Saved Games\DCS'. If you need to install it under DCS.OpenBeta: a) Adjust filepath in camp_init.lua from 'Saved Games\DCS to 'Saved Games\DCS.OpenBeta'. b) Edit FirstMission.bat to point to your DCS installation directory c) Run FirstMission.bat I have also updated the first post. Another user also reported that you need to make sure you have admin rights for these folders.

Soviet Black Sea Fleet naval aviation is threatening NATO sea lines of communication in the Mediterranean. To keep vital SLOC open, Sixth Fleet has ordered the Saratoga Carrier Battle Group into the Eastern Mediterranean in an effort to blunt Soviet offensive operations and attrit their naval bomber force. This mini-dynamic campaign servers to explore the Tomcat's fleet defense mission. This is a limited scenario, putting the Saratoga Carrier Battle Group against a Soviet Tu-22M3 Backfire maritime strike division. There is no elaborate story-line or strike operations, just pure fleet defense. You win the campaign by running the Soviets out of bombers, you loose the campaign when your carrier gets hit. Emphasis is on carrier ops, air-air refueling, combat air patrol and interception of multiple supersonic targets. Expected campaign duration is usually 3-5 missions. Enemy strength, attack direction and timing is random for each mission, so if you enjoy the basic mission type this campaign should provide some replayability. The first campaign mission is fixed as a necessity for integration with the DCS campaign interface, it is therefore set up as a light introduction. It can be played fully or quit at any time without any adverse effects on campaign progress. The campaign takes place on the Black Sea map due to lack of better options in DCS currently. You will quickly notice that the Black Sea, legal issues aside (which would be void in wartime anyway), would be too small to operate a carrier battle group in a hostile environment. The carrier's defensive screen would basically overlap with the enemy's own air defenses. You have to apply a little imagination and assume that the campaign takes place in the Eastern Mediterranean instead and that the Soviet Backfire strikes are coming across Turkey from their home bases on the Crimea. Hopefully in the future we will get more appropriate maps for these types of scenarios. I am pretty proud about this campaign. The scenario might seem comparatively simple, but considerable effort was made to make it work. The involved units, tactics and force levels are fairly realistic to the best of my knowledge and inherent limitations of DCS. The Backfires will apply dangerous simultaneous, multi-axis, supersonic attacks with squadron sized groups. Soviet doctrine assigned one maritime strike division per carrier, which is what is being portrayed here. In fact, the 2nd GvMRAD on Crimea had a 3rd Tu-16 Badger strike regiment in addition to two Backfire regiments, which is missing here as we do not have this AI aircraft. Also, each strike regiment (Backfire and Badger) would have had its own support squadron of dedicated Tu-16 escort jammers and electronic warfare aircraft, which are obviously missing here too. DOWNLOAD If you already have the Dynamic Campaign Engine installed, you need to update it to v20200111. Installation: 1. Download Dynamic Campaign Engine and extract to "...\Saved Games\DCS\Mods\tech". 2. Download EastMed Fleet Defense campaign and extract to "...\Saved Games\DCS\Mods\tech\DCE\Missions\Campaigns". Make sure that your install directory is 'Saved Games\DCS'. If you need to install it under DCS.OpenBeta: a) Adjust filepath in camp_init.lua from 'Saved Games\DCS to 'Saved Games\DCS.OpenBeta'. b) Edit FirstMission.bat to point to your DCS installation directory c) Run FirstMission.bat MissionScripting.lua modification: Dynamic Campaign Engine requires the following modification of your DCS installation to work. Open the file "...\DCS World\Scripts\MissionScripting.lua" with a text editor. Add two minus signs in front of line 16 "sanitizeModule('os')" and line 17 "sanitizeModule('io')". The code block from line 16 to line 20 should then look like this: --sanitizeModule('os') --sanitizeModule('io') sanitizeModule('lfs') require = nil loadlib = nil NOTE: This modification has to be repeated after every update of DCS World, as each update reverts the file back to its original state. WARNING: This modification will allow the execution of any LUA code included in any downloaded and played custom DCS mission and is potentially harmful to your system. Modification at your own risk. Notes: - S-3B Tanker as placeholder for KA-6D (pending KA-6D AI by Heatblur) - CVN-74 Stennis as placeholder for CV-60 Saratoga (pending Forrestal-class by Heatblur) - Oliver Hazard Perry-class frigate as placeholder for every USN ship - Alert 5 fighters are set up to launch and intercept incoming AS-4 missiles with AIM-54. This has been working 6 months ago but is now broken due to a DCS bug, so interceptors will currently do nothing.

Here is a little illustration why I have a problem with the map size: This is a Tomcat/Backfire fleet defense scenario. The red circle is the range at which the Backfire will launch their Kh-22 missiles at the carrier. The orange circle is the distance from the carrier from where they will start their attack run. The Tomcats will fight the fleet defense battle between those two circles. As you can see, even if we put the carrier at the center of the map, Backfire simultaneous multi-axis attacks are limited due the the map size (~300-060°). Also, Guam will always be in there, you cannot place the carrier outside of the air cover of land based tactical air if you wish for a scenario where the carrier is on its own (or you have to close your eyes and pretend that Guam isn't there). Sure, you can make it work. But you basically have to lock the carrier in the same spot of the map all the time. I was hoping this map would provide more freedom for carrier placement.

These are Intruder loadouts. The F/A-18A serves as a placeholder until Heatblur releases the AI A-6E.

I was rather disappointed to read about the planned 1000x1000 km map size in today's newsletter. For a map whose main appeal is to provide sea space for naval operations, that is very small. Let's consider a Backfire attack on a US CVBG. If we assume a supersonic dash of 200 NM and a missile launch range of 200 NM, that means that a Backfire will initiate its attack run over 700 km out from the carrier. With the mentioned map size we basically would have to always put the carrier on one map side and start to bombers on the other side of the map. With Guam at the center, Backfires could basically fire their missiles at ships around the island from the edge of the map. Considering there is no major land mass for 2000 km in any direction around Guam, I was hoping this would be exploited to the fullest. It's all water after all (I think there is no harm to leave out some minor islands and atolls). I hope this will still be considered.

That is the best reason you can think of for the Soviets to attack Guam? Let me help you out with some more: -To neutralize the biggest Strategic Air Command base in Asia. -To neutralize a major anti-submarine warfare base in WestPac. -To neutralize the biggest US logistics hub for operations in WestPac. -To attain freedom of operations in WestPac. -To interdict vital SLOC to Asia. Sure, North Cape, Kamchatka or Kuriles would have been more relevant areas. But these have never been for disposition, as the aim was to create a simple to produce, free map. And while the relevancy of the Marianas is rather low, the ratio of relevancy/"effort to make" of the Marianas is extremely good.

Soviet Naval Aviation had staging bases for bombers on the Kuriles, for example on Iturup. 3500 km vs 2500 km is hardly twice as far. In geostrategic terms it simply means both are out of range for land based tactical air and in range for medium range bombers. Sortie of the Soviet Pacific fleet into the Pacific would depend on neutralization of Japan and foward deployed US air-naval units just as much as sortie of the Northern Fleet beyond the Norwegian Sea would depend on the neutralization of Norway and foward deployed US air-naval units. Both is possible, while equally unlikely. I don't see a big difference here. In fact the Pacific Fleet would have easier access to the open ocean with the major naval base at Petropavlovsk on Kamchatka, provided timely forward deployment of major surface units before the outbrake of hostilities. On option the Norther Fleet didn't have. So what is the Cold War scenario that you could play on an Iceland map that you can't play on the Marianas map?

Though, from a Cold War standpoint, Iceland and Guam are almost identical scenario wise. Both islands are a similar distance form Soviet bases and would have to be defended against Soviet bomber strikes. A Soviet amphibious assault of both islands would have been about equal likely (or unlikely). What would you expect to do with Iceland that you can't do with Guam?

The good news is, as annoying the the required DCS restart may be, is that the next mission is still generated and you can play the campaign by opening the next mission (_ongoing.miz) as Single Mission or through the Mission Editor. Playing through the Campaign user interface is probably not possible though, because I assume there you are stuck with the first mission.