Hyperlynx

Anyway, yeah: user error. My bad. I should pay closer attention to the update notes.

Right, I see. Thanks. What I posted was from the DCS F-16 manual, but I guess it's out of date. That's the thing, I didn't mark it as the solution, and I got an error message trying to un-mark it. But, well, turns out it *is* the answer because they changed the procedure...

Why is this marked as the solution? If anything this is a workaround, not a fix. The ordinary procedure is to turn on MIDS at the same time as starting the alignment. That's also what's stated in the manual: null It also doesn't explain why most of the time it works fine but sometimes doesn't work. In any case, I'll incorporate this into my procedures and see how it goes.

I see. Thank you for checking. I'm reasonably sure it's not my procedure, because I do the same thing every time: all switches on the rightmost panel on, mids knob on, datalink knob to stored heading, then I'm careful to not move the jet or rearm it until ALIGN blinks in the HUD, at which point I set the knob to NAV. Then I enable GPS time on the relevant DED page. That would have been the procedure I used in that session, too. Does the trackfile capture what I did? Does it indicate that I deviated from procedure? Still, if it happens again I'll try the procedure from the start, and I'll post a trackfile here.

I'm a professional software engineer, and have been for over a decade. When a bug like this lands on my desk, it's up to me to reproduce it. Not the customer. And then I fix it. If a customer reports a bug, support asks them to supply logs, they do so, and then I come back to tell my boss "actually I need them to stand on their head and use a hula-hoop at the same time" then he'd quite rightly tell me to stand on my head and use a hula-hoop at the same time. That's my job, not the customer's! This has been a persistent issue for at least a year now. Just Monday it broke again. I've produced a reproduction case, the fact that it requires another product which ED also sell has no bearing on the matter. It's not easy to reproduce. It doesn't happen on demand, and at the moment only happens maybe 20% of the time. Those are the worst kind of bugs to try to reproduce and fix, my absolute least favourite, and I'm sympathetic. Perhaps it only happens when there's a certain combination of factors? Fortunately I've provided a case of exactly that happening. That's also why I'm not putting in my own time to repro it; I get enough of that at work. Its literally not my job to diagnose other peoples' software for them, specially for free.

This is STILL an issue. My datalink was broken again this Monday's ops, though my wingman's was working fine. This was on the Kola map, a co-op mission with no AI wingmen. And what on earth do you mean, "need non-paid campaign track"? You're telling me you don't have access to your own products, for testing purposes? Come off it. Don't just wash your hands of the problem. I'm not making it up, here. Fix it, please.

Well, to be fair, the guide for defeating manpads which is included in the mission does in fact work. I practised repeatedly using that advice - cut afterburner, go high, break into the missile, roll over it, then go NOE. It works. The catch is, you need to either know where the launcher is a head of time, or see the shot, or have your wingman tell you where the shot is coming from. There was nothing forcing you to have 20-30 minutes between start of mission and the shoot, though, which is a hell of a long time to have to burn to reset. I gave up after the third or fourth time (after having gone and trained specifically against iglas) and just skipped the mission.

First, I can't see the house called out by the JTAC from the IP, it hasn't loaded in at that range. Second, when doing the show of force on the road, the wingman's call that there's a missile launch is utterly useless because he doesn't say what direction to break. Third, it's like a half an hour's time wasted getting the jet started up and getting to the mission area only to get blown up and have to do it all again. Fourth, exactly how are you expected to do evasive maneuvers while carrying a full bomb load and two bags, never mind without over-G'ing the jet? Just YOLO it since DCS doesn't model over-G? Terrible!

Gamblers mission 10. No datalink whatsoever, despite taking care to set the time, even cycling all datalink switches to attempt restart. Track file exceeds 50mb, so I've linked it: https://drive.proton.me/urls/65YK2Q0D3G#V2hLHOe6uymN NB: confirmed to not be an issue with the mission itself. I first accidentally made this post in the bugs forum for the Gamblers campaign instead of here, and Baltic Dragon checked it out and confirmed no issues as far as he could see.

...oh. My bad. I totally meant to post this in the general F-16 bugs and problems forum! I'll do that now.

Really? Multiple people in thread have said the mav WPN page slews faster than the TPG, including an actual F-16 maintainer who says he sees it too but the real weapon does the same thing, but you're not seeing it happen?

I'm really struggling with the Gamblers campaign because of not being able to see details despite having my TGP on target and zoom cranked up all the way. I've just bombed the wrong house in M10 because they said "see the house with the solar panels?", I identified two rectangular blurs on the roof as the target, hit it dead centre, but it was the wrong one. Trees and details like solar panels only LODed in when I was well into my attack run. Any chance you can load in level-of-detail refinements based on where my TGP is looking too, rather than just my aircraft's distance? I can't just crank up the load-in distance for everything, I'm in VR. Track file at https://drive.proton.me/urls/65YK2Q0D3G#V2hLHOe6uymN

Gamblers mission 10. No datalink whatsoever, despite taking care to set the time, even cycling all datalink switches to attempt restart. Track file exceeds 50mb, so I've linked it: https://drive.proton.me/urls/65YK2Q0D3G#V2hLHOe6uymN

But how come in the video linked by Czar they don't seem to be uncrabbing on touchdown? https://www.youtube.com/watch?v=_-z2t5Zos4g I'm not sure this is the correct solution. I think Tenkom is probably right, that you do want to stay in the crab and let the wheels skid, with as little pressure on them as possible, until the nose comes down.

Given that the internet is international (I'm Australian) that's kind of splitting hairs, don't you think? But in any case: are you really meant to just skid down the runway during aerobraking after landing crabbed?