Sedlo

Hmm. Master Mode Air to Ground and Master Arm on?

You need to change the laser code to a valid number. Code 1111 is a placeholder, the weapon won't get into a firing situation with that on there. Once the code is valid, click the MAV button twice to get into the page you're looking for. Cheers!

If there way a way to incorporate the full range of options of the training rounds into the simulation, I'm sure every campaign maker would do it. But for now, we'll have to stick with what we have. Cheers!

It's a limitation of the DCS engine... As a mission designer, you can go three ways with this... One is to launch actual weapons and blow actual stuff up. Another way is to do what Baltic does, is have a press spacebar when you get a valid shot method. The third way is complex, and requires either scripting or a heck of a lot of different triggers in the mission editor to make it work. I made a single player mission in the NTTR where the player will shoot actual missiles, but the actual missiles get destroyed before they hit the target. Once that happens, the other plane flies off to the regeneration point. I achieved this by using Grimes' missile script here: I have to say, it was very difficult to test and get it right for just one opposing aircraft, so making a Red Flag style mission with dozens of possible bandits would be very, very difficult. Anyway, if you want to give it a shot, here is a link to the Hornet mission: https://www.digitalcombatsimulator.com/en/files/3313262/

Nothing in the pipeline yet, I'm still hammering away at some other campaigns at the moment. I'm glad you enjoyed these, I really appreciate the kind words.

OK, brand new Warthog throttle owner here.... I have no idea what's going on, but I find myself in the situation below. I bought a Thrustmaster throttle a week ago. Works great out of the box, but I wanted to make some of the switches do certain things, so I set up some profiles in TARGET, and got things working well.. For example, in the Viper, I created a Viper profile that used the EAC Arm/Off switch to act as my landing gear up and down. Bingo, it worked fine, and every other function of the throttle worked fine, too. Today I loaded up DCS and Target, ran my Viper profile and....... Every other function that each throttle button/switch that I did not add an event to in TARGET does not work in DCS. (zoom lever, boat switch, mic switch). So right now, when I run the profile, my custom EAC Arm/Off works for the landing gear, no problem. But everything else that's bound to the throttle does not work. Once I stop running the TARGET profile, the regular DCS functions are enabled on the throttle (zoom, boat swtich, etc). But of course, the custom switch functions don't work. Any help? I don't understand why it was working before, and all of the sudden it's not. It's the latest Open Beta, I haven't changed anything from the other day when it was working before.

I had a similar issue that had to do with a corrupt .miz file. To confirm if that's what the problem is, try creating a brand new mission and add a sound file. If that works, the issue may be within your .miz file. If I recall correctly, I ended up opening the .miz file and manually erasing the line referencing the audio file.

Here is a script that will help you accomplish what you're going for.... This will increase the value of Flag 1 by one each time a missile is fired by the units named LAUNCH 1, LAUNCH 2, LAUNCH 3, LAUNCH 4, LAUNCH 5 or LAUNCH 6. The important thing is to make sure you input the UNIT names of the missile launcher(s) into the script, not the group See attached mission file for an example of this script in use. The flag value will increase by one each time a missile is fired. Once 5 missiles are fired, the group deactivates. (Thanks to Hardcard for helping me with this a while ago) Handler = {} function Handler:onEvent(event) if event.id == world.event.S_EVENT_SHOT and event.initiator == Unit.getByName('LAUNCH 1') or Unit.getByName('LAUNCH 2') or Unit.getByName('LAUNCH 3') or Unit.getByName('LAUNCH 4') or Unit.getByName('LAUNCH 5') or Unit.getByName('LAUNCH 6') then flag_value = trigger.misc.getUserFlag('1') trigger.action.setUserFlag('1', flag_value + 1) end end world.addEventHandler(Handler) MISSILE LAUNCH SCRIPT.miz

Keep in mind that those triggers are checked once every second, only. It might not register in a 20 metre zone because the missile may have transited it within that once second window. A script may be the answer here.

For both versions of the A-10C, you need to add some folders and lua files to the .miz file itself. Open up the .miz file in 7zip or winRAR (or whatever zipping program you have). Add VHF_FM_RADIO, VHF_AM_RADIO and UHF_RADIO folders, and within you'll need to create a .lua file called SETTINGS.lua. The contents of the SETTINGS.lua file look like this (this one for the UHF radio, but it the same principle applies. Also, this may change when the new ARC radio gets implemented in the A-10C II) : --cut/paste below -- These values overwrites the default settings for the A-10C, including hotstarts. To enable the server wide dials settings, remove the -- settings= { --["dials"]= { ["mode_dial"]=0, -- 0=OFF, 1=MAIN, 2=BOTH, 3=ADF ["manual_frequency"]=251000000, -- Overwrites the value set in the ME. Default=251000000 ["selection_dial"]=0, -- 1=MNL, 2=PRESET, 3=GRD ["channel_dial"]=0, -- See the presets below. 0=preset 1, 1=preset 2, etc }, ["presets"]= { [1]=361100000, [2]=264500000, [3]=278800000, [4]=313300000, [5]=364800000, [6]=325100000, [7]=270200000, [8]=319500000, [9]=336600000, [10]=374500000, [11]=271200000, [12]=235500000, [13]=272100000, [14]=233300000, [15]=394300000, [16]=225000000, [17]=297500000, [18]=251500000, [19]=259600000, [20]=341200000, }, } -- end Take a look at my Eastern Friendship A-10C II mission here to see how I've done it: https://www.digitalcombatsimulator.com/en/files/3312554/

Hi R.MES! I've only got a 1080p monitor, so the black dots appear for me when the aircraft are within about 10 miles. It's quite likely any resolution larger than that they will be harder to see, but I don't have the option to test. I will have another look next day off. As far as the overhead break trigger misfire, I think I know a way around it, and I'll try and incorporate that into the mission, next chance I get. Thanks for flying, and I really do appreciate the feedback. Cheers, SEDLO

Mod the mission if you must, but please don't post it.

Version 1.02 up for all aircraft.. I adjusted radio transmission quality for SD01, added some atmospherics and adjusted a couple of triggers. Thanks, CommandT for the feedback!

Hey CommandT, thanks for flying it and thanks for the feedback! I'll address the comments in order below: 1. Good call on the Russian paint job, I'll try and see if there is something I could do there. 2. I was debating the Hard deck thing too, and you're right, a test like this should be done much higher up IRL. I just found that the Nevada map looked so cool down low :-) Something to mull over, for now. 3. I had a bit of voice over put together that didn't get into version 1.0 (waiting for some voice overs to come in) re: Janet flight holding outside the area awaiting results of..... well, you know. I hope to have it complete and integrated soon. As for activity, yeah, during a test flight, there wouldn't be too much going on on the ground, but I can look at adding some static life to the area, for sure. 4. This was on me. The voice actor for SOUND 1 did some great lines, I just tried to edit it a bit to sound more like a MiG-29 audio I've heard on the ol' scanner. To me it sounded tinny, so I tried to replicate. I think I didn't do a very good job, in the end, and maybe should have left it similar to what the other ones have. I will dig into this in the next week or two and try to make it better. And just FYI, the ending that you had isn't always the ending you will end up having :-) There is some random variable which affect how the mission plays out.

Updated Nov 21, 2020 with new mission end message.,

[ATTACH=JSON]{"data-align":"none","data-linktype":"1","data-linkurl":"https:\/\/www.digitalcombatsimulator.com\/en\/files\/3313261\/","data-size":"custom","data-tempid":"temp_262858_1605726725326_929","height":"300","title":"TITLE_1.jpg","width":"200"}[/ATTACH]​[ATTACH=JSON]{"data-align":"none","data-linktype":"1","data-linkurl":"https:\/\/www.digitalcombatsimulator.com\/en\/files\/3313262\/","data-size":"custom","data-tempid":"temp_262859_1605726760427_10","height":"300","title":"TITLE_HORNET_1.jpg","width":"200"}[/ATTACH]​[ATTACH=JSON]{"data-align":"none","data-linktype":"1","data-linkurl":"https:\/\/www.digitalcombatsimulator.com\/en\/files\/3313260\/","data-size":"custom","data-tempid":"temp_262861_1605726800819_210","height":"300","title":"TITLE_TOMCAT.jpg","width":"200"}[/ATTACH]​ HAVE ARMCHAIR - VIPER: https://www.digitalcombatsimulator.c...files/3313261/ HAVE ARMCHAIR - HORNET: https://www.digitalcombatsimulator.c...files/3313262/ HAVE ARMCHAIR - TOMCAT: https://www.digitalcombatsimulator.c...files/3313260/ OVERVIEW S/NFD) The HAVE ARMCHAIR series of evaluations is designed to investigate the tactical capabilities of the Russian MiG-29A aircraft, the new R-60 Infra-Red Air to Air Missile and the upgraded Russian helmet mounted display when used against front line USAF and USN fighter aircraft. Results of the performance and flight test evaluations, system and subsystem characteristics, design features and technical information acquired from the exploitation will be presented in a future FTD technical manual and disseminated to the USAF Weapons School and USN Fighter Weapons School for incorporation into front line training and tactics. TEST ENVIROMENT AND OVERVIEW OF PROCEDURES 1. (S-NFD) Offensive and defensive tactical capabilities of the MiG-29A will be assessed during air combat maneuvering with selected tactical US aircraft. Basic fighter maneuvers used and described in AFM 3-1. 2. Both aircraft will depart the test site and proceed north west to the test ranges. The flights will be monitored and recorded by BLUEBIRD. 3. Flight test 1 will consist of four (4) head to head engagements over RANGE 74A, 74B, 74C, 75E and R-4807B. 4. Flight test 1 will also consist of neutral fight set ups only – Both test aircraft will approach each other in a neutral, head to head pass. No simulated weapon release will occur prior to the merge. 5. Since the goal of the mission is to evaluate both the R-60 seeker head performance, as well as the Russian helmet mounted sight, all simulated weapon employment will be IR missile and gun only. EXPANDED OVERVIEW OF PROCEDURES TAXI AND TAKEOFF 1. After engine start, flight will check in on VICTOR 16. 2. Flight will taxi to runway 14 via taxiway CHARLIE 3. Approaching runway 14, flight will switch to tower frequency 4. On departure, the flight will commence a right turn towards waypoint 1 and contact BLUEBIRD on UHF preset 10. ENTERING MISSION AREA 1. The flight will proceed towards waypoint 1 (REGEN EAST), at which point, SOUND 1 will break off and head to waypoint 2 (REGEN WEST), while SOUND 2 will orbit waypoint 1 and await the fight’s on call fr om SOUND 1. THE TEST MISSION 1. At the fight’s on call, both aircraft will turn in and merge over the KAWICH VALLEY. There will be no simulated shots until the merge. (DESIGNER’S NOTE: The mission requires the 2 aircraft to pass within 6000ft of each other. Failure to obtain this distance or less at the merge may break the triggers on the mission) 2. Once at the merge, both aircraft are free to maneuver as required to obtain a valid IR missile shot or guns shot. (DESIGNER’S NOTE: Make sure you have your master arm on and actually fire your missile or gun. The enemy is set to invulnerable, so your shot will not shoot it down) 3. If a missile or gun kill is registered, there will be a “KNOCK IT OFF” call, at which point, both aircraft will return to their respective hold points (Player returns and orbits waypoint 1 (REGEN EAST). 4. Once the player is established in an orbit within 1 nautical mile of waypoint 1, AND the AI MiG has returned over waypoint 2, the next fight will commence. 5. At the end of four (4) engagements, both aircraft will rejoin and proceed back to land at HOMEPLATE. MISSION DESIGNER’S NOTES HAVE DRILL and HAVE DOUGHNUT was a program in the late 1960’s in which the United States obtained Soviet built MiGs and flew test missions with them from the Groom Lake test site. The goal was to explore the capabilities of the Soviet jets, and to develop tactics and procedures to counter them effectively in combat. (see https://en.wikipedia.org/wiki/HAVE_DRILL or https://en.wikipedia.org/wiki/Have_Doughnut for background information) There are three versions of this mission, once having the player aircraft at the F-16C Viper, one with the F/A-18C module and the third the Heatblur F-14 module. Both versions work identically. NOTE: When referencing radios, UHF (Uniform) radio refers to COMM1 and VHF (Victor) refers to COMM2. My goal in making this mission was to imagine a HAVE DOUGHNUT type program, but using modern Russian and American jets. While I’m sure there have been actual programs that evaluated more modern Russian aircraft at Groom Lake, these efforts remain classified to this day. However, there have been several photographs of Russian built aircraft over the deserts of Nevada in modern times, as you can find here: https://www.lazygranch.com/groom_lake_birds.html. Below is a list of things you will need to know and/or perform in order for this mission to work successfully. COMMUNICATIONS / RADIOS I’ve tried to make this mission feature realistic communication calls and procedures. To that end, realistic comms forced on in this mission, and it will require you to tune your specific radios to specific channels or frequencies as required. For example, at the mission start, once your engine is running you will be prompted to contact your flight lead on VHF channel 16. You will need to switch your COMM2 radio to preset 16, and once you do, the next radio call will play. Each time you are required to change your radio channel, a text box will be visible in the top right of the screen. This message will remain on screen until you tune the correct radio to the correct channel/frequency. Once you do, the next voice over / radio transmission will play and the mission will continue. Do not forget to MONITOR GUARD! FLYING THE MISSION You are flying as the number 2 in a flight which consists of your lead, SOUND 1 (Russian Jet). Your callsign is SOUND 2. Once you check in with your lead on the ground, you will be prompted to switch your UHF radio to GROUND. Once that happens, you lead aircraft will start its engines and taxi out about 40 seconds later. Your lead aircraft will taxi fairly quickly to runway 14, so make sure to keep up. Approaching the runway, you will be prompted to switch to tower frequency. Make sure you do this prior to lead taking the runway. As your flight lead takes position on the runway, you should do the same. Try for a formation takeoff if you’d like, otherwise follow your lead’s takeoff roll as soon as possible. Once airborne, maintain formation with your leader. They will lead you to waypoint 1 (REGEN EAST), wh ere you will orbit, awaiting your flight lead to reach waypoint 2 (REGEN WEST). One your lead is at REGEN WEST AND you are overhead waypoint 1 (REGEN EAST) the fight will commence. Do not shoot until both aircraft arrive at the merge. You must pass within 6000ft of each other before the fight starts. Failure to get within 6000ft of the opponent will break the mission, so make sure you pass close. Once you merge, you are clear to fight the opponent. You will actually fire your AIM-9 or gun, but any fire will not damage any aircraft (it’s simulated, after all). The script is developed by one posted by GRIMES in the Eagle Dynamics Forums: https://forums.eagle.ru/forum/englis...42#post3579442 Once a hit is registered on any aircraft, there will be a knock it off call and both aircraft will return to their respective REGEN points, SOUND 1 to waypoint 2, SOUND 2 (player) to waypoint 1. You will fight a total of four (4) fights and then return to base. On approach to runway 14, you will the overhead break and land. One last thing: There are elements of randomization incorporated into this mission. Be prepared to deviate from the flight plan as necessary. ENJOY! image widget

Hi R.MES! Thanks, I'm glad it worked well (for the most part). I'll address the comments below: 1. Yep, the wingman is almost completely useless in this mission. Things have changed with DCS since this mission was first made, and it's a bit of a hit or miss situation now. Best not to rely on them, or just send them after some bandits in the meantime. I'll have to have another look at this mission in the future. 2. I've set this mission to be black dot labels for all aircraft to try and make it real as I can. But in order to set black labels, it will prevent the player from selecting the normal labels. I was told that having black labels would be something incorporated in DCS soon, but it haven't happened yet. I'm hoping that this change happens in the near future, so perhaps this can be addressed soon. 3. I'll have another look at the refuel option, I'm not sure if there has a been a DCS change yet. The way it was originally written is for "Alley Cat" to ask you if you want to refuel, you then answer with the yes or no. Once Alleycat tells you to push to the tanker frequency, you then push to tanker and THEN send your wingman to refuel. That way worked for me in the past, I'm not sure if there have been changes that made that different now. 4. Sounds like you did it right. If you were close to the base and you were offset to the right, that trigger may have fired. (if you're not overhead the actual runway (21L if I recall), then you may accidently fire the wrong trigger. Have a look if you've got TACVIEW, or if you recall being offset the right at all. 5. No idea at all! Could be a carryover of a mission written in an earlier version? Thanks for your comments, I will have a dig into this mission on the weekend and see if there is anything I can adjust. Cheers for now, SEDLO (BTW, sorry it took a day for the response, it seems the email notifications aren't working with the new forums)

Hi R.MES! Thanks, I'm glad it worked well (for the most part). I'll address the comments below: 1. Yep, the wingman is almost completely useless in this mission. Things have changed with DCS since this mission was first made, and it's a bit of a hit or miss situation now. Best not to rely on them, or just send them after some bandits in the meantime. I'll have to have another look at this mission in the future. 2. I've set this mission to be black dot labels for all aircraft to try and make it real as I can. But in order to set black labels, it will prevent the player from selecting the normal labels. I was told that having black labels would be something incorporated in DCS soon, but it haven't happened yet. I'm hoping that this change happens in the near future, so perhaps this can be addressed soon. 3. I'll have another look at the refuel option, I'm not sure if there has a been a DCS change yet. The way it was originally written is for "Alley Cat" to ask you if you want to refuel, you then answer with the yes or no. Once Alleycat tells you to push to the tanker frequency, you then push to tanker and THEN send your wingman to refuel. That way worked for me in the past, I'm not sure if there have been changes that made that different now. 4. Sounds like you did it right. If you were close to the base and you were offset to the right, that trigger may have fired. (if you're not overhead the actual runway (21L if I recall), then you may accidently fire the wrong trigger. Have a look if you've got TACVIEW, or if you recall being offset the right at all. 5. No idea at all! Could be a carryover of a mission written in an earlier version? Thanks for your comments, I will have a dig into this mission on the weekend and see if there is anything I can adjust. Cheers for now, SEDLO (BTW, sorry it took a day for the response, it seems the email notifications aren't working with the new forums)

Campaign is done, right now I'm working on getting things set up on the logistics of distribution. This is proving to be very complicated, more than I had thought. I hope soon, but I can't promise any time line at this point.

Yes, please DCS. Overlord bot is a game changing advancement and needs all the support it can get.

Yes, it'll be a Viper campaign. Early, early stages at the moment.

The story of mission 3 in the book is such an important one, I think not to include it would have been a bad idea. After all, the campaign is supposed to revolve around the missions in the novel. And as a beta tester, I voted to keep it in for that reason. I do understand the OP's concern about lack of detail in that part of the map, but I think the immersion may have been killed in another way if the action had been based at a UAE city, for example (not situationally, politically realistic). I think BD was in one of those catch-22 situations on this one. I am hopeful that, maybe, in the future, the Persian Gulf map may get extended up to Kuwait and at least Southern Iraq :-) I think you'll very much enjoy the rest of the campaign, the missions become more and more immersive (for me, stressful in a fun way!)

Bold Cheetah is a 13 mission campaign on Persian Gulf featuring the Hornet and Supercarrier. It will be a paid campaign and hopefully release will line up in the near future.

Thanks! My first real campaign was Vulcan Forge, it's a fictional Harrier campaign on NTTR. It's some of my early work, so not as smooth and refined as later stuff, but I still have fun with it and people enjoyed it when it came out. As for Eastern Friendship, if you really wanted to, you could change the dates in the mission editor to a summer time one, shouldn't affect anything that I can think of off the bat. I still kind of like the winter textures, but I do love winter as a season, too.

And just realized you did my Red Flag ones.... Eastern Friendship is pretty enjoyeable.