JethroTundra

In mission 3 after taking off and flying for a few minutes I noticed that I was 11.3 nm from waypoint 1, the same distance as at the ramp, and not getting any closer. It was apparent that according to the nav system I was not moving at all. I stayed the same distance from all waypoints no matter where I flew, and on the HSI/SA page my aircraft position showed at waypoint 0 the whole time. I'm not sure if this is a mission problem or a DCS problem, but I've never seen this bug before. I restarted the mission and before taxi, changed my INS knob from NAV to IFA in case it was an INS issue. Things then seemed to work normally on takeoff, but then sometime between waypoint 1 and 2 I stopped moving again according to the nav system.

I posted this on BD's Discord but reposting here. Finished the mission but still have some questions. Mr.Dieing's post about the waypoint bug answered some of mine. Deleting the questions that are no longer relevant. Have some Hornet systems questions that apply to mission 4 (spoilers). I'm at the stage where Knight is asking me to find a skunk at 265, 19 from WALL SOCKET. Several things are confusing me. Hope this is a good place to ask. 1. "Dolly" was referenced in the radio call, and Flip said "receiving," doesn't that mean I should see the skunk on my SA page? What am I looking for there? Yes my datalink is on. 2. I don't understand how to easily reference bullseye when searching for sea surface contacts. The radar display does not show the cursor bearing/range to bullseye like the A-A radar does, neither does the FLIR view, unless there's a way to do that I don't know about. I have been using the cursor on the SA page (which does reference bullseye) to get the approximate location, then trying to use that to focus my radar search. 3. I created some markpoints for the Udaloy and other surface contacts, but can't find them again - when I decrement the waypoint selected on HSI past waypoint 0, I believe it is supposed to go to the markpoints, but it isn't, it just cycles through my waypoint 0, 1, and 2. Appreciate any help - not sure if something is buggy here or if I don't understand the systems. Here are a couple possible glitches I noticed with the mission itself: 1. I eventually found the right ship and got shot at. When I was cleared to engage, I hit it with a Maverick, and it sunk after about a minute, leaving just the small speedboat. Flip's subsequent radio call said it was 'DIW' not sunk. Maybe I just hit it too hard. The briefing mentioned targeting the bridge, but I couldn't determine how to adjust the aim of the Mav - after uncaging, the TDC didn't seem to slew it at all. Seemed prudent to hit it from standoff range after being shot at. 2. The last voice comm I heard was Raven 21 off the tanker and inbound to my posit. They flew to me, then past me north about 15 miles, then came back and started to orbit above me. I expected more comms clearing me to RTB but never got any. I waited for 15-20 minutes after the last voice comm, then was below bingo so headed to mother. The only voice after that was the built in marshal comms. Still finished with score of 100.

Yes, I had antiskid on. I don't know what the problem was. I assumed it was that I touched down with such a large yaw in relation to the runway heading, but I don't know what to do about that.

Still just chuckling with joy at the level of challenge BD and his crew sees fit to throw at us in an introductory training mission. First attempt, last night, thought I was sierra hotel because I managed to plug with the tanker on the first try, my first time at night and in weather. Flew a good approach and wasn't expecting the waveoff call - it was 1AM already and I was worn out - thought I could catch a wire so I did. Mission score 50, failed to progress, probably would have been grounded IRL for ignoring the LSO. Second attempt today, waved off the approach, sitting in an air conditioned basement and sweating as I hope I will see some lights of Cyprus out there in the pitch dark before I run out of gas or screw up and crash. Finally a nice lit up runway! Piece of cake. Oh no, this crosswind is WICKED. Never had to fly one before where I have to keep the runway outside the HUD to stay lined up. I guess I need to read up on crosswind landings. I put wheels on the runway and thought I was home free, cut throttle and popped all the brakes. The Hornet leaned over on one wing like a main gear had snapped (but it hadn't), skidded off the runway and crossed over to the left taxiway, then skidded 180 around and came to a stop 5 feet from a parked C-130. Checked an external view and my nose gear tires were gone. I think IRL the jet is FUBAR and I'm stuck on Cyprus for a while. But I scored 90, all is forgiven and now I get to try mission 2 and see what crazy surprises are in store next. I absolutely love this, but I'm mad I couldn't keep that landing on the runway. I wish I could attempt it again without going through the whole mission. Thanks BD, Jello, Hozer and crew!

So I posted a couple weeks ago about Mission 5, I've been stuck on it for a while, different weird things keep happening that are usually my fault, but this one wasn't. Completed the primary objective. Received the call for urgent CAS. Followed all the steps, made 2 show of force runs. The enemy troops then started to move out and I was directed to do one more show of force (the one where you get a SAM shot at you). As I'm rolling in at low altitude, I think, what are those objects out in front of me that look like they are falling? Zoom in the view just as the objects hit and blow everything to hell including buildings in the village. Newt then radio calls to me "WHAT ARE YOU DOING" and I am directed by Sentinel to RTB due to an unauthorized attack. The debriefing screen said it was Newt's bombs that made the kills. Mine was still attached to my wing, and the enemy forces were at my 12:00 for about 4 miles when Newt killed them. I never gave the radio command for him to attack, in fact wasn't at that point in the mission yet where the forces are confirmed hostile. Flew home anyway and completed the mission with an 88 score, thought it would be lower. I actually had almost the same thing happen on my previous attempt, but I convinced myself I somehow fired the cannon when I wasn't supposed to, as I had just selected it, but now I think Newt dropped bombs that time too. I'm wondering if the recent update changed something. Also my autopilot didn't work the whole way home, and Newt did not rejoin formation, seemed to remain in the area of the CAS incident, in case that gives the author any clues.

Loving the campaign and the effort that has gone into it. Mission 5 started off well... I assumed from the briefing that my job was to put two JDAMs on a building, so I put them on the building. I therefore had no bombs when we got the CAS call. No problem, I have a wingman for that. I tasked Two with the attack. I watched him make two runs over the enemy, but didn't see any ordnance or anything go boom. Would the designer expect him to use bombs (he still had two) or guns? Since Two didn't accomplish anything, I made a strafing run myself, but got hit by maybe ground fire, maybe a MANPAD - I was still flyable but had a fuel leak. I think I could have made it back to base if I could have found a tanker, but couldn't find one. I believe according to the SPINS, Texaco would be expected to be near Lake Assad, which was close by. I tuned in to Texaco's TACAN and radio channel and made a call, but got no response, and the TACAN never picked up a signal. I could see a C-130 in the area on datalink - was that the tanker? Just wondering what I might have done wrong or if there's any other reason why I couldn't find the tanker, and also what happened with Two's attack runs. Also while I'm here, general question about ATC in the campaign. Specifically, arrival procedures and the approach corridors. These are pretty simple to follow in VFR conditions, but in one mission I did it was cloudy, and I couldn't find the landmarks like "Using Dorfyol as a reference point fly heading 302 to point FALCON, overflying Ceyhan to intercept the 050 radial for runway 23." This would be simple if I had waypoints or the data to make my own waypoints for Dorfyol, point FALCON, etc. (Or even the moving map visible, which I've also noticed the absence of). Wondering if there's something I'm expected to do here besides dead reckoning. Thanks again for all the cool stuff in these missions!

Thanks, that was very helpful, finally found it and completed that step. Unfortunately I had a DCS crash while RTB and didn't get to deal with the spoiler thingy I accidentally read about.

20 attempts, orbiting the valley until bingo, and I cannot make this FAC happy. Supposedly IP Bravo is a ridge with a radio tower. I do not see a radio tower anywhere. There is a barren tan peak, highest one around, that sort of looks like the pic in the kneeboard, which if overflown will give the right attack heading of 353. Flying this heading I still get "ABORT ABORT ABORT" when I call inbound. What am I missing here? How far is IP Bravo horizontally from the target? Any reason we can't make IP Bravo a waypoint if we have to overfly it so precisely?

Thanks BeerNfrites - binding a HOTAS to comm1 instead of Communications Menu solved my issue. Also appreciated the tip on datalink, no problem finding Poodle this time. Finished the mission with an 88, probably due to being slow to getting my FLIR onto the Fishbeds. Looking forward to the rest of the campaign.

That's correct. No comms menu at all following clearance for takeoff. I got as far as joining up with Poodle and him asking me to contact ATC into Syria. I couldn't do this either because the comms menu wouldn't come up. Quit the mission at that point.

Excited for this campaign but having some issues in the first mission. I followed all the instructions for comms - easy comms turned off, making sure to press enter on UFC after switching channels so the F10 menu would work. This worked fine up until my takeoff. I proceeded on runway heading at 1500 as directed by tower, then when told to switch to departure, my comms menu would no longer come up, either with key command or HOTAS command. No comms menu at all. Couple other oddities. Since I couldn't reach departure, I just headed for waypoint 1 to find Poodle. Partway there, my pilot said a voice line along the lines of "I'm heading into restricted airspace. I should change my course." At the time I was very close to the flight path line between base and waypoint 1. Is datalink expected to work in this campaign? Tried to use it with the SA page to find Poodle. I could see his symbol off and on (yellow 1 with a flight path arrow) but his location on SA page was way off from his actual location when I was able to find him with radar or visually. Would appreciate any tips. Thanks.

no, it specifically says to let him take off first

[spoilers] So Psycho dropped her 2 practice Mk20s and I dropped one, then got a call to intercept what turned out to be the two UAE Mirages. After I got them to turn away, things started to get weird. First I was prompted to reply either "affirm" or "negative" to something Psycho said, but I didn't hear her say it. I replied "affirm." I think I was on the right channels - I switched as prompted, and during the whole last part was on Strike and Tactical. After that I heard a lot of chatter about the Raven 2 flight intercepting some bogeys until eventually they were told to "skip it." Psycho and I flew around somewhere north of mother and south of Iranian waters for 20 minutes or so, until finally I got the prompt "Press space bar when you have Outlaw on your radar." I did not get any voice command about Outlaw. I'll try it again tomorrow but don't want to repeat that whole sequence if something is glitched. If I did something wrong with the radio or something, someone please let me know.

I've seen other posts about similar glitches but not this particular one. For Mission 3 I took off just a few seconds behind Smoke. I saw him circling to my right, assumed he would be forming up on my wing, and headed toward waypoint 1 and 2. A few minutes later, at angels 32, I noticed Smoke didn't seem to be close by and found him in F2 view, at angels 9 and headed in the wrong direction. Kept an eye on him and he landed on the carrier around the time I arrived at the tanker (while still chatting on the radio as scripted). The scripted chat directed Smoke to tank first and he wasn't there, there was no probe for me, so I couldn't tank and had to quit the mission. Wondering if I did something wrong with comms to cause this? I'm going to run as a single mission and restart after the tanking as directed by BalticDragon in other posts in order to continue, just wanted to mention this.

Finished mission 1 today. First time I'd done any DCS mission as a wing to an AI lead, and I'm unclear how landing is supposed to work. I called inbound to mother when Saint told me to, then I followed him to the vicinity of the ship, assuming he would land first, and then Saint seemed to just fly around at 1500 feet or so without entering a landing pattern. I was at a lower fuel state which started to become urgent so eventually I just landed. The mission was complete but I wasn't sure if I was supposed to do something different or if there's a radio command to get permission to actually land.