Jayhawk1971

Do I type that in all caps or....? Well, I'll do mission 6 over again later or tomorrow; let's see if I can give Mr. C a more timely simulated demise.

Maybe he considered the KC to be the bigger threat (me being a lowly nugget)? Too bad I didn't have Tacview enabled (performance reasons), I would have liked to watch what happened there. My best guess would be that when he launched at me, he was also facing the direction the tanker was in (when I came around from my turn I saw both Paco and the AIM-9 that had missed me in front of and flying away from me). Maybe the long range of the AWG-9 (as opposed to, say, a Viper's radar) made him pick up the tanker, and since I was behind him, he "forgot" about me?

Worked for me with regards to "missile first, then guns". I did start pre-flaring when he called out 5000' (or whatever the second range call was), because I knew (from my previous attempt - DCS crashed while loading the next set) that when I heard him call "Fox 2" it was already on its way. I've got a question about the time frame within you are supposed to kill Paco, in both defensive and offensive perch. Both times I got an "Average" with the only remark being "took a little too long to kill the bandit". How fast do you have to hit him to not get this message? While also staying within 6.5G. It's not that I dragged this out into an epic dogfight. While I can see where I could have been faster during defensive perch (I chose an energy fight as we were already in a two-circle due to the setup), I thought I was pretty damn hot during offensive perch. My initial AIM-9 actually hit him, then I high yo-yo'ed, held him in lag (above canopy bow) for half-to-two-thirds of a turn to set myself up, pulled him into the HUD for a guns kill. "Knock it off".

I just flew mission 6 again, was doing well (all average) until the one-circle abeam set. Then AI-Paco went nuts. After the second merge he got behind me and launched a Sidewinder at me, which I managed to dodge/flare away. As I came around the turn, I saw him way in the distance, running away at full speed. I chased after him. Turned out he was going after an AI KC-135 which he shot down with a Sparrow. Here's the relevant part of the debriefing log, as the trackfile is probable way too big a file (saved it just in case, let me know if you need it). [27] = { ["initiatorMissionID"] = "324", ["initiator_coalition"] = 1, ["initiator_object_id"] = 16778240, ["initiator_unit_type"] = "F-14B", ["initiator_ws_type1"] = 1, ["t"] = 380.141, ["target"] = "KC135MPRS", ["targetMissionID"] = "281", ["target_coalition"] = 2, ["target_object_id"] = 16778496, ["target_unit_type"] = "KC135MPRS", ["target_ws_type1"] = 1, ["type"] = "shot", ["weapon"] = "AIM-9M", ["weapon_type"] = 1443604, }, [28] = { ["initiatorMissionID"] = "324", ["initiator_coalition"] = 1, ["initiator_object_id"] = 16778240, ["initiator_unit_type"] = "F-14B", ["initiator_ws_type1"] = 1, ["t"] = 384.771, ["target"] = "KC135MPRS", ["targetMissionID"] = "281", ["target_coalition"] = 2, ["target_object_id"] = 16778496, ["target_unit_type"] = "KC135MPRS", ["target_ws_type1"] = 1, ["type"] = "hit", ["weapon"] = "AIM-9M", ["weapon_type"] = 1443604, }, [29] = { ["initiatorMissionID"] = "281", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16778496, ["initiator_unit_type"] = "KC135MPRS", ["initiator_ws_type1"] = 1, ["t"] = 384.771, ["type"] = "ai abort mission", }, [30] = { ["initiatorMissionID"] = "281", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16778496, ["initiator_unit_type"] = "KC135MPRS", ["initiator_ws_type1"] = 1, ["t"] = 384.771, ["type"] = "pilot dead", }, [31] = { ["initiatorMissionID"] = "324", ["initiator_coalition"] = 1, ["initiator_object_id"] = 16778240, ["initiator_unit_type"] = "F-14B", ["initiator_ws_type1"] = 1, ["t"] = 384.771, ["target"] = "KC135MPRS", ["targetMissionID"] = "281", ["target_coalition"] = 2, ["target_object_id"] = 16778496, ["target_unit_type"] = "KC135MPRS", ["target_ws_type1"] = 1, ["type"] = "kill", ["weapon"] = "AIM-9M", ["weapon_type"] = 1812, }, [32] = { ["initiatorMissionID"] = "281", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16778496, ["initiator_unit_type"] = "KC135MPRS", ["initiator_ws_type1"] = 1, ["t"] = 385.78, ["target"] = "", ["targetMissionID"] = "0", ["target_coalition"] = 2, ["target_object_id"] = 16794112, ["target_unit_type"] = "", ["target_ws_type1"] = 1, ["type"] = "eject", }, [33] = { ["initiatorMissionID"] = "281", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16778496, ["initiator_unit_type"] = "KC135MPRS", ["initiator_ws_type1"] = 1, ["t"] = 386.78, ["target"] = "", ["targetMissionID"] = "0", ["target_coalition"] = 2, ["target_object_id"] = 16794880, ["target_unit_type"] = "", ["target_ws_type1"] = 1, ["type"] = "eject", }, [34] = { ["initiatorMissionID"] = "281", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16778496, ["initiator_unit_type"] = "KC135MPRS", ["initiator_ws_type1"] = 1, ["t"] = 387.78, ["target"] = "", ["targetMissionID"] = "0", ["target_coalition"] = 2, ["target_object_id"] = 16795136, ["target_unit_type"] = "", ["target_ws_type1"] = 1, ["type"] = "eject", }, [35] = { ["initiatorMissionID"] = "281", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16778496, ["initiator_unit_type"] = "KC135MPRS", ["initiator_ws_type1"] = 1, ["t"] = 391.4, ["type"] = "crash", }, [36] = { ["initiatorMissionID"] = "0", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16794880, ["initiator_unit_type"] = "", ["initiator_ws_type1"] = 1, ["t"] = 404.16, ["type"] = "pilot landing", }, [37] = { ["initiatorMissionID"] = "1", ["initiatorPilotName"] = "Reflected", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16780544, ["initiator_unit_type"] = "F-14B", ["initiator_ws_type1"] = 1, ["t"] = 419.9, ["type"] = "land", }, [38] = { ["initiatorMissionID"] = "0", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16794112, ["initiator_unit_type"] = "", ["initiator_ws_type1"] = 1, ["t"] = 433.12, ["type"] = "pilot landing", }, [39] = { ["comment"] = "winner: , msg: ", ["t"] = 437.255, ["type"] = "mission end", },

...or transfer to JAG corps.

Maybe (hopefully) the planned switch to multithreading/ multicore will help with that.

Yep, S&A has definitely taught me to fly more aggressively and "proactive". Before, I tended to treat the Tomcat too much like an Airbus sometimes (the Hornet as well; incidentally not the Viper for some weird reason, and the A-10 I right out abuse ...it can take it.). Precise, but somewhat "stolid".

Yup, saw the vid in my YouTube recommendations earlier today. Strange that no one from Heatblur posted that here.

I noticed that, too! Thought I was seeing things. It's some weird lateral sliding motion, as if the AI is trying to compensate? And don't get me started on the AI's instant accelerating/ decelerating! Something that has been driving me nuts for ages in DCS. Maverick: "Gonna hit the breaks, he'll fly right by." DCS AI: "Hold my beer......"

Yeah, I did that. It just would have been easier to have a more prominent visual cue. And I mostly blame the poor VR resolution, which is so pixelated that it's actually hard to see the exact tip of the intake. Well, VR is a tradeoff. Overall, "being there" quality > resolution and performance, for me personally.

You don't get any further scripted events (like custom radio comms, voice overs), so your flight home is silent, but once you come to a stop at Nellis, you'll get the mission complete message and you can advance to the next mission without having to skip it. You could even land at 21L and no ones gonna say a peep about it.

Shhh, don't tell Paco. I bet he'll come up with a choice callsign for me.

Yes, I do that, that's how I know I'm drifting off, either too far out or too close. The problem is once I see 6 miles (or 4, respectively) on the HSD, it's already too late. I watched Red Kite's video a couple of times, he did seem to nail it perfectly, but I have no idea how. After the third time trying I got the initial break right (to 5 miles), but after that my turn must be either too tight or to loose.

I guess I played too much "Zone 5"? I think I never was instructed to land on 21R before in any campaign on NTTR (isn't 21R/ 03L supposed to be reserved for the bigger aircraft like AWACS and tankers and such IRL?), so I suppose it was force of habit. So the trigger zone was offset to my right as I landed on 21L? Still weird that the trigger fired as I was taxiing halfway down Foxtrot (abeam Alpha North EOR), though. Edit: Funny that I never really noticed until now. Other than the fam flight I was "unsupervised", meaning missions 2 and 3 I RTB'd without any further comms due to AI being stuck with the tanker, and mission 4 triggers worked fine (just like in Zone 5). So I guess I completely forgot about 21R between missions 1 and 5.

"DCS: Unbreakable" Tomcat pilot is Bruce Willis, Viper pilot is Samuel L. Jackson's character.

I finally made it through all sets, working my way up from "below average" (LANTIRN and CCIP) via "average" (strafe) to "above average" on the low pop sets. My main issue is that I'm having a hard time maintaining the correct abeam distance during the fist two sets. I either wander a mile too close or too far at some point in this "vulture circle" of a pattern. The racetrack patterns on the final three sets where much more up my alley. Does anyone have any tips or hints on how to better judge an maintain the correct abeam distance throughout these circular patterns, while also managing to manage speed and altitude?

Found a slight glitch after landing. I got the whole "turn right onto Bravo" and following radio messages trigger well after I should. I got them while already taxiing back to parking, right around where you would turn off to the parking spots in Zone 5. Either the trigger zone wasn't where it should be, or I got some lag after landing? Mission ended without any problems after I came to a full stop. No biggie, just wanted to let you know. Some more information: I was at taxi speed at about where the trigger zone should be (the Tomcat is so "sticky" that I actually have to add power after landing to even make it to Bravo) I turned off at Bravo, crossed 21R and then turned left onto Foxtrot Then I got the triggered messages No mods installed (mod folder in saved games/DCS only contains tacview and VAICOM) In retrospect, I assume I was supposed to turn left this time to Golf and the disarming area? Tower said something about "Golf".

Here you go.

NP, I can see where timing the mission sets can become an issue, and taming that wild AI must be a massive pain in the butt as it is. Speaking of butts, mission 5 has been kicking mine! The fact that I hardly ever did air-to-ground in the Tomcat isn't helping.

For both day and night cruise formation training parts, you included an additional "press spacebar when ready" option after mission start, which I found very helpful, as it gave me time to get settled (trimming and catching up). Even though I "pre-trim" during active pause and set the throttles in anticipation of the briefed speeds, it still takes some time to get settled. This option would be very helpful for other mission sets as well.

MIssion 4 was actually quite fun and not all that difficult, somewhat of a "break" from the previous 2 missions (=not as nerve-racking as flying formation with suicidal maniac AI in the dark ). On to the next one: I've already watched Redkite's video preview of mission 5, so I'm forewarned. Unless I'll be getting an "unsat" in upcoming missions, my plan for now is to go through the campaign without repeating a lesson, then do the whole thing again more thoroughly. Hopefully by then ED has finally fixed some of the AI bugs and quirks.

Nice! Do you plan to make this campaign into a playthrough-series on your YouTube channel? It's always nice to see how others are doing. And I'm glad I wasn't the only one surprised by the very abrupt heading changes by the AI.....incidentally, I did use pretty much the same vocabulary as you did

I see you did use the CAG bird in mission 3. Made my VR-life a lot easier. Still hard enough, though (I opted not to mess with the gamma to see how I'd do; average, average, and below average for the formation stuff) BTW, nice touch with the sound effect during night AAR.

The bog-standard comms menu with which you contact AWACS, ATC, order your flight around and so on. Some campaigns/missions give you an additional menu item, accessed by the F10 key on your keyboard when the menu is "active". You need to use this in order to interact with the missions. You access this menu with the radio buttons that you have assigned.

While we're on PSA's, here's one for the "HUD-cripples": No one said not to switch the HUD display mode to either takeoff or landing to get a more fine-tuned pitch ladder for those mission 1 maneuvers; at least not after you arrived at Stuckey's Peak. Not saying you should, of course. But who's gonna know?