MBot

Now that we have the first true anti-ship strike fighter in DCS in the form of the Viggen, I think it is finally time that ships engage aircraft with their naval guns. Most naval guns are dual purpose, meaning that they are designed to engage both surface and air targets. This is evident by high rate of fire and especially maximum elevation angle (AK-176: 85°, AK-100: 85°, AK-130: 80°), which are design features that greatly increase gun complexity and that would not be necessary to engage surface targets only. Additionally, most naval guns are capable to fire proximity fused ammunition against air target (all Soviet designs from 76 mm on for example).

Wow, really. Mission scoring in DCS sure is pretty buggy. Funnily I haven't seen this bug myself for about a year now. But reading the feedback, it seems to affect users every now and then. Nothing I can do about it unfortunately, this is related to DCS.

I hope they will get trimming with FFB correct this time, it is still all wrong with the MiG-21.

You probably ended the mission immediately after loading, right? DCS needs a couple seconds to apply the correct mission scoring.

Thank you for the notice. I can see where the error occurs, but since there are thousands of different combination it is almost impossible to tell what causes it. I just run about 50 mission generations and could not reproduce it, so it seems to be pretty rare. For now I suggest you play the first mission again (you can end it any point without negative impact). It is extremely unlikely that you will be seeing the same error again. Meanwhile I will keep an eye open for it.

Doh, I made a thought mistake. You have to generate a new first mission and restart the campaign when updating to 1.01 (and I also should have regenerated a new first mission when packing up the 1.01 zip). There is nothing wrong with the code, I just didn't think that trough correctly. I will update the first post with a v1.01b (no new download required, everyone can just re-generate the first mission themselves). Sorry about that.

Ok, we probably have a little versions mix up here. I suspect you have already updated to to v1.01 but didn't play any 1.01 mission yet? In which case the DEBUG applies new 1.01 code to a failed 1.0 debriefing, which generates a completely new error. Please play a new mission again (just a few seconds, then end). I suspect the debriefing will fail as previously. Then run the DEBUG bat again and we should now see the true error. Edit: Forget about that, see below.

Those that are having problems with the command window only popping up shortly and no debrief screen, please do the following: Place the attached DEBUG_DebriefMission.bat in the campaign folder (where the other bat files are) and execute it. You should now see an error message that is lasting. Make a screenshot and post it, I can then have a look at it. Thanks. DEBUG_DebriefMission.zip

This particular campaign is (almost) air-air only, as it is a spin-off from the Tiger campaign which has blue attacking and red defending.

Fly the MiG-21bis interceptor for the Warsaw Pact in a 1976 simulated air war exercise in Nevada. Features: Single player or up to 2 player COOP dynamic campaign Intercept mission types Persistent damage and resources tracking across missions This is a MiG-21bis spin-off of the Desert Tiger 76 campaign. Download and discussion thread in Missions and Campaigns subforum

Fly the MiG-21bis interceptor for the Warsaw Pact in a 1976 simulated air war exercise in Nevada. Features: Single player or up to 2 player COOP dynamic campaign Intercept mission types Persistent damage and resources tracking across missions This is a MiG-21bis spin-off of the Desert Tiger 76 campaign. Download V1.05 Installation instruction in Read Me Changelog: V1.02 - 07.02.2017 -Fixed unable to spawn in COOP with more players than just the host -Used new F-5E skin V1.03 - 22.02.2017 -Fixed wingman not taxing V1.04 - 23.04.2017 -Fixed available weapons at airbases -Made weather 100% clear, as clouds cause severe FPS drop -Various small fixes and updates V1.05 - 22.12.2017 -Maintenance update Desert Fishbed 76 v1.05.zip

First post updated with V1.01 which fixes coop stats tracking. If you do not want to play coop, an update is not strictly required. [cross]If you want to update but keep your campaign progress, you can do so by only exchanging the Scripts folder.[/cross] Fingers crossed... Edit: Actually, regenerating the first mission and restarting the campaign is required. Better just download the whole thing again.

I doubt that launching multiple Mavericks per attack is something that is done IRL through. Especially with the A-model missile that is range limited by the seeker to about 3 NM. You are basically giving up any stand-off advantage that the missile had to begin with.

Also with the type of mission profiles the Viggen did, you wouldn't need more than 1 Maverick anyway. The same with the Rb 05. Unless you make a second attack run (which is a big no-no), you will probably bring the second missile back to base most of the times.

You don't even get the debriefing.txt upon ending a mission? Can you post your campaign installation path?

A little update on the coop front. After giving this a night's sleep, I decided to write my own custom events log. I am not terribly happy about that approach for a number of reasons. For single player this unnecessary duplicates event logging and I am not sure about the performance impact this has (especially if you do such things as dropping cluster bombs on a city, or when aircraft bump into each other and create hundreds of hit events). More importantly this replaces code that was extensively tested and debugged in SP and was confirmed to be working well, with new code that is largely untested. The event handlers are notorious for causing script errors in exotic situation which will again require countless hours of playtime to be discovered. I am sure this will still bite me in the butt with script errors down the road. It sucks to drop established SP stability overboard to fix a MP problem that will only affect a small percent of players, but I currently see no other way to enable coop. It works so far...

Well, I am completely puzzled right now. I am checking reports about no stats being saved in coop play and just noticed that the debriefing.log file after a MP mission is basically empty except for world state entries and a single "mission end" event. Are events not written to the log file in multiplayer? If so, you can basically forget about playing any of my dynamic campaigns in coop. As mentioned I developed this primary with SP in mind. While this campaign was very extensively tested in SP, I never actually bothered to play a coop mission beyond spawning the aircraft, assuming that since the code is the same it would work without issues. If it now turns out that events are not being logged in MP, that is a huge bummer.

Ok, played around a little and now can reproduce the problem. I haven't seen it yet because I always use a different procedure. Everyone needs to select his aircraft before the host unpauses the mission. After 2 seconds of runtime your aircraft will spawn and you can enter the cockpit. If you try to select a slot after the mission runs, try to change aircraft or re-spawn, you will not be able to enter. I don't know why it is that way, but it works. Since this is for coop MP play, it should have no impact.

I had to go for a compromise here, as this start-up time applies universally. If you park right next to the empty runway it will be plenty. But should you start at an airbase with 5 minutes to taxi to the runway and plenty of AI traffic, it will probably be needed. I figured better to have a few minutes extra than being late. Thanks for all the kind comments so far. I am looking forward to reading some AAR soon :)

Have you tried to re-generate a new mission (with the .bat files)? Someone previously mentioned that this is related to DCS trying to put clients on parking positions occupied by AI. Frankly I haven't tested the MP aspects beyond basic functionality checks and I did not notice this problem. In SP I have encountered the bug a couple of times that two AI aircraft spawn into each other at certain parking positions at Nellis. Perhaps this problem is more pronounced in MP?

Having the SA-2, probably the most significant SAM in history, would be highly desirable.

Actually the Viggen and the Tomcat were the reasons I started with the Dynamic Campaign Engine one and a half year ago. The first campaign is for the F-5E simply because it kind of cut in line :) Anti-ship missions against static ships are already possible. I will have to write a naval module for the DCE to let ships move around and do worthwhile stuff, but compared to the complexity of a ground war this should be pretty easy. My first campaign for the Viggen will be in Nevada though and therefore not feature anti-ship missions. A more naval centric Viggen campaign will follow when we get a more appropriate map.

No such plans from my side currently. Guardians would not be possible to be redone to the new standard. The new system works on the principle that every aircraft in the campaign is always existing in the game world, either in the air or on the ground. Since Turkey is not part of the Caucasus map, this would mean that for the Guardians campaign there are no NATO airfields available. My plans currently are to put together the final Desert Fishbed derivative of this DC, play a bunch of missions to confirm it is in good order, and release it later this week. Then I will have a deep look at the Viggen...

Frankly I haven't thought about that. That would be much more convenient. I will have to check if it works.

Join a F-5E Tiger II of the 57th Fighter Weapon Wing at Nellis AFB, Nevada and participate in a 1976 offensive air war exercise against period Warsaw Pact air and ground threats. Features: Dynamic campaign with a estimated length of over 50 mission Fully integrated into the DCS User Interface Single player or up to 4 player COOP A variety of Air-Air and Air-Ground mission types Persistent damage and resources tracking across missions Download and discussion thread in Missions and Campaigns subforum