MBot

Do you get the freeze everytime you end the campaign mission, even if you just stay 10 seconds into the mission, or only after prolonged durations? What you could also do to narrow down the problem is deleting all the triggers in the ME and then checking if you get the freeze. If there is no freeze, this would point towards a poblem with the scripting system. Not that this would be of any help for a solution though... I have also seen such freezes when extiting a mission from time to time. Mostly when doing heavy testing and running multiple large missions after each other with tons of activities and with extensive use time acceleration. I was always under the impression that this was somehow related to memory usage accumulating from mission to mission.

I build what I like to play personally, and I like the Cold War era. Great effort has been made to make this as period correct as possible. For example the composition of the Independence battle group is how it actually sailed for real in the summer of 1990. So there won't be anything more modern from my side. Given the choice for a Hornet, I would have even taken a 1980s F/A-18A. Well, actually I would have taken the A-7E ;)

Yes in this case it won't help then. Once a debriefing has been created successfully, various temporary log files are deleted. It then can no longer be recovered. Closing the (wrong) promt window in this case equalled to answering 'no' (do not accept mission results).

Thank you, it is my pleasure :)

You can try to run DEBUG_DebriefMission.bat (edit it first to your DCS installation path). If the error is not a recurring one, that can sometimes salvage a mission result. Getting two comand promt windows sounds strange indeed though. That is the first time I have heard of that. Are you sure that one didn't remain open in the background from a previous mission attempt?

Keep in mind though that the mission profile speeds and altitudes are sometimes nudged to help the AI and may not necessarily be optimal for the player flight model. It is a bit of a compromise sometimes. Obviously you are stuck with the cruise speed of your package but adjusting cruise altitute may help. Generally it is unnecessary though and you should have sufficient fuel to follow the flight plan. Gianky makes some excellent points. Keep and eye on FPAS and be mindful of afterburner unsage and you should be fine. In a previous iteration of the campaign I had some long-range strikes to Shiraz and even those were possible withouth refueling. Regarding enabling EPLRS for AWACS, that would not be a simple edit and would include additions to the mission generation code. I am very glad you guys are putting some time into this and are flying missions. For me it is most satisfactionary to see that people are playing my work.

The problem is your installation of DCE in the 'Saved Games\DCS.openbeta' folder. You should either: A. Install DCE under 'Saved Games\DCS'. B. If you need to install it under DCS.openbeta: B.1 Adjust filepath in camp_init.lua from 'Saved Games\DCS to 'Saved Games\DCS.openbeta'. B.2 Edit FirstMission.bat to point to your DCS installation directory B.3 Run FirstMission.bat

Before using the bat files by hand, open them with an editor and make sure that they are pointing to your DCS installation directory.

AI aircraft with with a Search Then Engage task with targets "missiles" will not engage missiles. Please see attached sample mission with a F-14B with a Search Then Engage task, encountering various anti-ship missiles and not engaging any of them. This was still working correctly last June and it seems this bug was introduced since then. This problem affects Tomcat fleet defense missions. Missile_Intercept.miz

Yes you can install the F-14 campaign the same way, it has its own folders. Both campaigns are designed to exist next to each other and run on one common DCE installation.

You know, everything I will ever do will be pre-1991 :)

No there won't be any CAS. The campaign's emphasis is strictly on strike operations and related support.

I am glad you are enjoying it so far. I did not set up anything specifically to accommodate the Hornet datalink. For the Tomcat this works out of the box, are there any special requirements for the Hornet? In any case, the Hornet probably didn't have any DL yet in 1990 anyway.

Ok I see. The content in the Zip file has a folder structure that should be extracted completely. Your installation then must look like this: ...\Campaigns\FA-18C Battle Group Delta.cmp ...\Campaigns\FA-18C Battle Group Delta_first.miz ...\Campaigns\FA-18C Battle Group Delta_ongoing.miz ...\Campaigns\FA-18C Battle Group Delta\Active\ ...\Campaigns\FA-18C Battle Group Delta\Debriefing\ ...\Campaigns\FA-18C Battle Group Delta\Debug\ ...\Campaigns\FA-18C Battle Group Delta\Images\ ...\Campaigns\FA-18C Battle Group Delta\Init\ ...\Campaigns\FA-18C Battle Group Delta\Init\base_mission.miz ...\Campaigns\FA-18C Battle Group Delta\Init\camp_init.lua ...\Campaigns\FA-18C Battle Group Delta\Init\camp_triggers_init.lua ...\Campaigns\FA-18C Battle Group Delta\Init\db_airbases.lua ...\Campaigns\FA-18C Battle Group Delta\Init\db_loadouts.lua ...\Campaigns\FA-18C Battle Group Delta\Init\oob_air_init.lua ....\Campaigns\FA-18C Battle Group Delta\Init\targetlist_init.lua

Difficult to tell, but looks like an incorrect installation. Can you make a screenshot of the campaign folder structure?

Just saw today's newsletter. Kh-22NA would be the weapon of choice for Backfire or Bear-G to strike Andersen AFB on Guam :)

I don't think there is really a need for TACAN fix. The carrier will probably move under a mile from your WP0 location by the time you have completed INS alignment. The is plenty accurate for navigation. The INS would also drift be that amount by the time you reach your target, which is not modelled either.

From what I could gather, the land attack version can be conventional or nuclear just like the anti-ship version. Regimental sized missile strikes with all nuclear weapons only would be a huge waste of nuclear warheads. I think the Kh-22P anti-radar version was only operational with the Tu--22P Blinder and the Kh-22MP for the Backfire was apparently cancelled.

Workaround Intruder until we get the A-6E by Heatblur :)

It would be nice if the Kh-22N anti-ship missile currently in game could be copy-pasted into the Kh-22NA INS+TERCOM guided land-attack variant. This could probably be set up fairly quickly (no new 3D modeling required) and would provide the Tu-22M3 a stand-off strike capability against land targets in addition to sea targets, providing additional options for interesting mission building.

Here is what I found regarding alignment without GPS on this forum after a quick search: https://forums.eagle.ru/showpost.php?p=4116515&postcount=2 I assume the Hornet should also somehow be able align on a moving carrier.

I am glad you could get it to work.

I think there is some trick for the INS alignment without GPS (mission is set in 1990 which is pre-GPS) but I don't know the details. Any Hornet expert please feel free to chime in. Frankly I haven't flown the Hornet for a long time. I have spend about 50 hours test flying the campaign with the Hornet one year ago, but have since switched to the Tomcat completely. The campaign was further developed with the Tomcat only, but I tough I would release the Hornet variant too as a courtesy for the Hornet players.

I am also having frequent issues with the Tomcat not launching. It is a DCS/Tomcat bug that hopefully will get solved finally with the new carriers (together with the annoying deck sliding that is also screwing up the INS alignment). When you did the camp_init.lua modification, did you also run FirstMission.bat? The new information will not be loaded into the mission until you generate a new first campaign mission (which has the information to start a new campaign baked into it). Also, in order to use the bat files, you have to edit them as well with a text editor first. The bat files need to point to your actual DCS installation directory to use DCS's LUA interpreter. This is not required for regular campaign play, only if you want to use the bat files by hand. Too bad that so many people are having installation issues. I was not aware that the DCS Saved Games folder is called differently for some open beta users. I am running the open beta myself, but my installation is just called regular DCS everywhere.

What is the error you are getting?