Sabre-TLA

We have not heard of that issue before. What version are you playing the mission on? You could try a DCS Repair and/or uninstall and reinstall the campaign. The coding is the same in all missions regarding COLT 1-2 so I'm surprised he would work in the others but not this one. We will retest in the latest OB 2.5.6 and see if we can reproduce it.

This one has caught many players. Look closely at the ILS knob. Here is another thread with the details.

The blue on blue calls are usually due to blue being killed or damaged by a blue weapon so before you launch a maverick or some other weapon consider the weapons effects on it's detonation. If the blue party is in the range of the weapon effects (ie splash damage) it could be damaged by your weapon resulting in the blue on blue call. As the pilot you do not have to agree with the JTAC on the weapon used if it will harm the JTAC party. The mission is only concerned that the targets are eliminated, not by using a particular weapon. It could be the splash damage of some of the weapons has increased over time but given the above consideration you should still be able to pass the mission. We will retest in 2.5.6 to see if it has changed dramatically and will adjust the triggers if necessary.

It's not that voice overs don't align with the waypoints it's the waypoint labels don't align with the correct locations. The voice overs are correct for the trigger zone you are in. Here is what it looks like in the mission editor so in your flight it appears they are all shifted one waypoint ahead. We will retest and see if this is another 2.5.6 bug but if we cannot reproduce it then I suggest you do a DCS Repair and uninstall or reinstall of the campaign or ignore the waypoint listing on the F10 map.

No problem. Please let us know if you encounter any issues. We have not had a chance to retest everything in 2.5.6 but will fix any issues that get reported and we can reproduce.

A tactical air designator is a series of alphanumeric characters which can be used to identify frequencies and nets. These designators are usually listed in the Air Tasking Order (ATO) to prevent inadvertent disclosure of classified information. They are in the briefing under Radio Information: RADIO INFORMATION: RESTRICTIONS: EMCON LEVEL: 2 TACTICAL AIR DESIGNATORS: 08: 243.0 MHZ AM 12: 124.0 MHZ AM 15: 251.0 MHZ AM 60: 30.0 MHZ FM 61: 31.0 MHZ FM 62: 32.0 MHZ FM TACTICAL TRAINING FREQ: TAD 12 GUARD: TAD 08 - MONITOR AT ALL TIMES AIR CONTACTS: YOUR FLIGHT: (3xA10C) COLT 1-1: AIRMAN TAD 15 COLT 1-2: WINGMAN TAD 15 COLT 1-3: 2ND ELEMENT TAD 15 AFACS: (2xOH58) UZI 1-1: FE TAD 12 ENFIELD 1-1: TAD 12 CAS: (4xA10C,2xSU25) A10C:BOAR 1-1,1-2: TAD 15 A10C:PIG 1-1,1-2: TAD 15 SU25:SPRINGFIELD 2-1,2-2: TAD 15 CAPS: (2xF16C) DODGE 1-1,1-2: TAD 15 TANKER ESCORTS: (2xF16C) DODGE 4-1,4-2: TAD 15 TANKERS: (1xKC135) SHELL 1-1: TAD 15 AM TACAN: 5X - TANKER MEDEVAC / TROOP TRANSPORT: (3xUH60) CHEVY 1-1,1-2,1-3: TAD 12 STRIKERS: (2xF15E,3xB52H,4xTORNADO,2xL39) F15E: FORD 1-1,1-2: TAD 15 B52H: FORD 2-1,3-1,4-1: TAD 15 TORNADO: PONTIAC 3-1,3-2: TAD 15 TORNADO: PONTIAC 4-1,4-2: TAD 15 L39: SPRINGFIELD 1-1,1-2: TAD 15 GROUND CONTACTS: JTACS: AXEMAN 1-1 TAD 60 HAMMER 1-1 TAD 61 PLAYBOY 1-1 TAD 60 PINPOINT 1-1 TAD 60 BADGER 1-1 TAD 61 JAGUAR 1-1 TAD 62 MOONBEAM 2-1 TAD 60 DARKNIGHT 1-1 TAD 60 FIREFLY 6-1 TAD 61 TAD 12 is 124.0 Mhz AM For the JTACs you want to use TAD 60, 61 or 62 which is 30, 31 or 32 MHz FM. If you are not getting a response check to make sure you are transmitting using the 2nd radio and on FM or try using the Easy Radio option which will grey out those you can't talk to. EDIT: The FAC task for UZI 1-1 is using 124.00 AM so you should use that to contact them. The UZI 1 flight frequency is 127.5 but you shouldn't need to use that.

Great job!

Glad you enjoyed the campaigns. It can be very challenging to find a good balance that works for all players. We appreciate the feedback. We have noticed that the game engine will have ATC do that if there are taxing aircraft even if not directly in front of you. We suspect it is having to account for very large aircraft as part of its programming as it won't clear you from hold until smaller aircraft are well away from you. So not sure if it's a bug or not but ED is working on the ATC and AI so we can only hope it gets better over time.

Thanks for the trk. We will take a look. We have some updates planned so we can adjust the triggers if they are not working as expected.

The mission hasn't been updated for some time so the triggers should still be operating as intended (and as in the video below). For the altitude make sure you set your altimeter to 2992. That should ensure you are within the correct trigger range. For the speed issue try quickly pulling the nose up to reduce speed. You have 25 seconds from the dialogue before you get a warning and then at 45 seconds you will get the terminate if you haven't slowed down in time. If things are not playing that way then try a DCS Repair or an uninstall and reinstall of the campaign files. If it's still a problem, please post a trk file or email us at mapleflagmissions@gmail.com and we can investigate further. Here is a video of how the mission should play out:

We thought about that but decided we really want to count the player kills as real shoot-downs instead of some AI driver not paying attention. If the AI improves we will consider changing that perspective. Hopefully ED will implement a Hard Deck limit for the AI someday so it can be a programmed limit. As for UZI 2-1 on approach he should peel off when you get to the race track. If he is not doing that can you post a trk or video and we can investigate further. Thanks for the feedback!

Yes and it has improved the performance for many. Here are some thread references: https://forums.eagle.ru/showthread.php?p=4253020 https://forums.eagle.ru/showthread.php?p=4251559

We did make some changes to improve the performance. You can read some user feedback here.

Very cool! Thanks for sharing. Can't wait until we can replicate your flights with an F-4 module.

Glad to hear it! :thumbup: We experimented with different parking positions and settled on the new position as the best for fps. ED is still working on the overall fps issue so when that is corrected it should help even more. We are not sure how it would behave on different systems so please continue to report if you encounter any other issues.

Glad to hear it! :thumbup: We experimented with different parking positions and settled on the new position as the best for fps. ED is still working on the overall fps issue so when that is corrected it should help even more. We are not sure how it would behave on different systems so please continue to report if you encounter any other issues.

The docs are included in the campaign now that it's available on the ED Store.

Best to open a support ticket with ED as they manage the STEAM interactions. Include your dcs.log file located in the saved games folder. That might have some clues for them. Let us know if you get it resolved. Thanks.

It's acting as if the authentication didn't register. If you login to the DCS Website and look at your profile, on the left hand side at the bottom there is a button called "All active licenses" Under the campaign listing there is a red arrow that will check the status of the license key. Select that and see what it says. From what you describe it appears it may not be activated so you should open a Support Ticket with ED. Maybe there was a problem when it was activating. Let us know what you find out. Don't post any screen shots though as that would advertise your serial number and hardware codes.

Thanks for your support. I'm not sure why it wouldn't show up in the F-5E Campaigns section. It appears ok to us on our test system (OpenBeta 2.5.6) (see attachment). Are you able to open the missions from the ME? Try a DCS Repair and see if that corrects it. Note that 2.5.6 changed many things and we have an update in the next patch to correct the skins and improve FPS.

Our updated files didn't make it into the patch in time. Others are still reporting performance issues on other things so I don't think ED has addressed it yet.

We reviewed our missions and made some changes to some inactive and static units and FPS improved on our test system. The parking locations changed in the 2.5.6 update so we also corrected those. We have submitted the files to ED so hopefully they will make the next update.

They are hard to make out from altitude but if you look at the satellite view of the area north of Nellis you will see some triangular shapes. They are on the chart as a reference point. I've highlighted one of them in the graphic below so you can make them out.

My understanding is that RED Forces don't use GPS so ED programmed it that way so for Aggressors setup as RED they don't have GPS capability. However, ED have added a menu item option called 'Unrestricted SATNAV'. See below. When you select that then you should have GPS capability regardless of coalition color.

@Hippo ON FLEX means on the FLEX Departure route. Page 10 of the inflight guide describes the route and altitudes you should keep when on the route. For example below 3000 until past the race track then below 8000 while on FLEX until you intercept the 15 DME arc to turn south. Then you intercept the LSV R-267 radial at or about 10200 until you reach FYTTR. You should be at or above 14000 at FYTTR. Hope that helps.