SpikeGondorff

Greetings all, I have what appears to be a dumb problem. The Follow task isn't working for me, and I assume I've missed something. I'm trying to get a Red plane to follow a Blue plane, which precludes the use of the Follow Task in the ME UI. I created stole this script, and literally nothing happens when it's supposed to trigger (plane doesn't move to intercept, no error message pops up, no errors in the DCS log, nothing): local IranF4Follow = { id = "Follow", params = { groupId = Group.getByName ("Overlord"):getID(), pos = {x = 1000, y = 0, z = 1000} } } Group.getByName("IranF4"):getController():pushTask(IranF4Follow) The trigger condition in the UI is just a Time More - 5 secs, and there's nothing else in the mission. It's literally an Iranian F4 and a US E2 that are within about 3 miles of each other to ensure they can see one another. I've triplechecked the Group names (and even changed then copy/pasted them to be sure), checked the case sensitive commands, use the actual groupId instead of the name lookup, everything I can think of, but it's not following. The odd thing is that if I make it a Red following a Red plane, the ME UI Follow task works fine while this script still does not. So I assume it's something on my end. Any help would be appreciated, thanks.

Did you try forcing them to the next waypoint with the Command - Switch Waypoint? You could set up a Bomb/Missile in Zone trigger that increases a flag each time a torpedo drops. When the Flag = # of expected torpedoes, push the command to switch waypoint. If you're asking why they won't automatically move on to the next waypoint, I have no idea. Getting the AI to do what you want is an exercise in patience.

Draconus is correct, in general. There are a few things I can control that might contribute to it. For example, I'll hear the "Unable" call if the AI can't detect the enemy, and if I scripted the AI to turn his radar off... It could be something else, like setting the ROE to Weapons Cold and not changing it (although I thought the player ordering a wingman to attack would overwrite the current ROE). I'll take a look when I get some time. Congratulations on beating it the first time; that's always nice in a mission. And thanks for letting me know about the wonky behavior!

You can overwrite the campaign files without impacting your progress. Your progress is saved in your logbook, which the campaign files don't touch. And there's no cheating in using the ACLS. Another tip: you should be able to land anywhere to advance the mission. I (hopefully) set it up that way so people who weren't comfortable with night carrier landings could still advance (or if you just didn't want to fly all the way back to the carrier). Glad you like it so far! There is no ETA on the paid campaign, as I'm still working on tweaking the old missions and creating new ones. I'm still learning how to edit voice files to make them sound like radio transmissions, so it will still be quite a while. I'm not sure if I should build it out with the super carrier or wait until Forrestal comes out and use that. The super carrier will be nicer (I assume), but I think the Tomcatters and Aardvarks deployed on the Forrestal to help with Earnest Will at the tail end of it in mid 1988. Hmm... If you see any issues with the campaign, please let me know!

Updated the campaign to tweak Mission 9. Friendly forces shouldn't be so unfriendly now. Thanks!

Hah, that's funny. Sorry that happened. Should be a relatively easy fix to flip the RedFor to invisible once you head south. I'll play with it tonight. Sorry again.

Excellent, glad you were able to finish it! Sorry again for the delay in fixing it. Do you still get messages on the right side of the screen if you turn off subtitles? If you do, then this is the perfect mission to forget the subtitles. You will miss some chatter with other planes, but Jester is the boss in this one issuing the commands. If you're also missing Jester's chatter on the right side, then yeah, you might miss some commands.

I'm glad you're liking it so far! It's amazing how the "little" things like AAR and trapping can be such a big deal, especially when Jester gives a nice comment for a 3 wire. Let me know if you have any other questions.

I haven't tested it, but I've seen others state what you have: order of start is based on order of when it was placed in the missions editor. The only way I know how to affect the start order is to simply delay the activation of specific groups. Group 1 is spawned 1 second after mission start, Group 2 is 2 seconds, etc. Play with it until you get the planes where you want them. It's annoying, but until they allow us to set where each plane spawns on the carrier, it's the easiest way. The only quirk with that system is the 6-pack/street area on the carrier. My understanding is that you can only get planes to spawn there at the start of the mission. Any late activations after mission start will never spawn in that area.

Can you just have a separate flag that triggers when entering the zone? Flag 1 is off at missions start. Unit enters zone, Flag 1 is on. Unit is outside of zone and Flag 1 is on = Unit is outside of zone after killing SAMs. Hope that helps.

This should be all 11 Mission Summaries and Blue Tasks. Let me know if something is awry with the PDFs. :) I'm actually working (very slowly) on updating it with the -A version with voice overs as a paid campaign. And at least 4 new missions. :) I've noticed a few missions don't work as well with the -A, as some of the speeds stated in the kneeboard aren't ideal with a max loadout for the less powerful TF30s. Some of the triggers are time sensitive, which need updating with the -A. EarnestWillPDFs.rar

There isn't. If I have some time tonight I can copy them out of my Word document into a txt/pdf and attach them here.

I set the player's plane to Late Activation to ensure where it spawns, which might be the problem. Remove that while adding Client, and it might work. I haven't tested it, but just giving ideas.

Greetings all, Got snowed in with intermittent power outages, so I couldn't test/tweak like I wanted to this past week. Finally got it done and updated the Campaign in User Files. Mission 4 - completely overhauled the way the laser targeting works (i.e. - got rid of the duct tape solution), and it should now correctly target the rigs. Also tweaked the AI and they should (hopefully) drop their bombs. Mission 7 - The Airbase name in the Mission Editor was changed, which broke the scripting for determining the runway health. Fixed the script by updating it with the new name. Also added a radio item to show the health of the runway at any time in the mission, will allow you to see how much damage you did. Mission 8 - The name of the Silkworm missile was changed in the Mission Editor, which broke multiple triggers for this mission. I updated the triggers with the new missile name, and it works as it should. Please let me know if you see any other bugs or issues, and hope you all are staying safe!

Thanks, glad you're enjoying it! To let everyone know, I've fixed the 3 missions with issues (missions 4, 7, and 8). I need to fully test them this week, but hopefully by this weekend or early next week they should be ready for upload. For Mission 7 (the infamous runway bombing mission) I've also added a radio option to immediately tell the health of the runway at any point in the mission. This will allow you to see what effect, if any, your bombing run had. I need to update the mission briefing to explain that new feature and specify the necessary HP level to advance the mission. Stay safe all!

I'm glad you like the campaign! I'm not sure if I'll convert it to the -A. I'd either have to drop the -B completely (and I don't know if people would like that), or I'd have to support 4 campaigns (the -A with Super Carrier, the -A without SC, the -B with SC, and the -B without SC...and I know I wouldn't like that ). I kind of wish I'd split out the SC and non-SC uploads so I could if one had significantly more than the other. I feel like most people have the SC, but I don't know for sure. On a separate topic, I think I figured out solutions for all the issues I mentioned earlier. I just need to implement the various solutions in all the missions and then test them.

Hahah, that's good to know. I love it when stuff starts working again. I'll still look at the mission again, as I know the AI wingmen are a little wonky, and I'd like to see if my new plan for the laser actually works. Thanks for letting me know!

Hello guys and gals, sorry for the long delay, but I'm reading through the issues now. I found the problem in Mission 7 when dropping bombs. The official name of the airbase in the Mission Editor apparently changed at some point. I tweaked the script, and it seems to be working fine in my test. I still need to play through the entire mission to make sure it's working. I'll also reduce the amount of damage needed to trigger the success, since that seemed to be a problem, too. I haven't looked at Mission 8, but I'll take a gander and see what's up with the launching parameters. I had issues originally with them not finding the target, even with radars included, and had to use an An-50 to get them to spot the ships. Maybe something is broken there. I'll also take a look at mission 4 and the LGB drops. I had to do a workaround to laser the rig correctly (I placed an APC on the rig so the FAC had a target), so maybe that duct tape solution broke. I might have found a more elegant solution, but I haven't tested it. Thanks to everyone who enjoyed the campaign and their kind words. I'll start working on those missions and see if I can get them working again. Thanks for the patience, and apologies for the lack of responses!

Glad it helped! I don't think I tried it with an SA-6, but when I played with the Hawk batteries, they had a tough time hitting all 4. I think in one of my tests one of the decoys actually hit the ground despite multiple launches against it. So (at least several months ago), the Hawk SAM system would thoroughly engage. Good luck with it!

Sorry for the delayed response (real life kept me busy this past week), but are you still having trouble? As Draconus said, your wingmates' actions have no bearing on the mission success. Even if they are shot down, you can still succeed as long as you bomb your target. Are you seeing the automatic message about the lasing? If you're not seeing it, then the laser isn't firing (and as others have said, you can also see it through the NVGs). I'll try the mission tonight and see if one of the recent updates messed it up.

Ahh, I understand. I should be able to work the triggers with some redundancies in case that happens. Or at the very least make sure the directions are clearer that you're not supposed to intercept the first time they pop up. Thanks for the feedback, let me know if you have any other issues.

That's great; glad you completed it. I just ran through it again and it worked, so I'm glad it worked for you as well. Spoiler for the logic: Hopefully the rest of the missions won't be as frustrating. And I'll also look into changing the fuel when you Continue. I never thought of that and it's a good point, thanks!

I just ran through the mission in OB, and it worked fine. I only tried the Continued version of the mission, but I'll try the full mission tomorrow. Were you on the full mission or the Continued one? I assume the latter based on your tip about fuel tanks, but wanted to confirm. There should be another intercept of F4s after the F5s, but I don't know why that didn't happen. They should be heading south to you when you're intercepting the F5s, and it should just be several minutes after you chase off the Tigers that you're requested to intercept the F4s. That's what happened when I just ran through it, but I'll look around some more tomorrow. The E-2 isn't technically operating as an AWACS, which is why you don't hear anything from him. I am running the excellent Random Air Traffic script, which, when I tested it initially, made the AWACS go crazy from random contacts. There was also the issue of asking for bogey dope would return the "wrong" contacts, hence the F10 menu option for BRA. Later missions have the AWACS working properly for data link information, but there is a Mission Controller that filters out the E-2 chatter. Sorry for the difficulties with it. I'll poke around tomorrow and see if I can't figure out what's up with that 2nd group.

1. I don't know of one. I noticed the same thing: the setting doesn't actually do anything and I still have to hit the Backspace key. No big deal, but the setting is there, so.... :) 2. There are some mods that clean up the cockpit. A quick search found this one: https://www.digitalcombatsimulator.com/en/files/3303911/?sphrase_id=3438495 I have no idea if it's any good or not, as I haven't used it, but check the comments and in the User Files section for others. 3. I have no idea because I don't use that program.

Ahh, I bet that's it. There are no voiceovers in the campaign, so everything is text. The only sound you hear when AWACS "talks" is the radio crackle. When you turn on subtitles, you'll see that all subtitled messages that come in by radio appear on the upper left part of the screen, even the default wingmen AI messages like, "rolling," "wheels up," "mud spike 9 o'clock," etc. I used Jester's custom speech as a message sent to the player so you don't need to have anything tuned. For custom radio messages, there is no voice over (like with Jester), but there are subtitles. I didn't even realize that was a setting, to be honest. Sorry for the misunderstanding, and I hope that was the issue and the rest of it works well! On a separate topic, I did come across this bug for the -159: https://forums.eagle.ru/showthread.php?t=272071 The Preset setting on the -159 doesn't work as a preset setting. I think I had to flip to Guard before I could turn the knob to select preset channels. I don't think there is any custom chatter from your wingman in mission 2, but there will be in other missions. Let me know if you run across any other issues! Thanks.