JupiterJoe

Amazing that so much detail is modelled. A 140 mile kill during that era is astonishing. Particularly when the target may not even be aware of the missile until it was too late.

I notice there's a volume knob for the ALR-50 on the early A. Is this not functional? I thought I heard a different (higher pitched) tone for the launch of an AIM-54 from an enemy F-14. It only happened the once, but I thought the ALR-45 didn't give a different tone for a missile launch, so is the ALR-50 also installed? I'm confused

Just so people are aware of Zabuzard's responses in another thread regarding this subject. The section of manual shown below seems to indicate there is no change of audio tone for an enemy missile launch from the ALR-45. I find that extraordinary. Is that accurate? So, if neither you or Jester spot the missile launch you're in serious trouble? Did all enemy missiles produce a vapour/smoke trail at the time? It does give you a sense of just how old the Tomcat A is I guess

Have you installed today's hotfix? Regardless, I have installed the hotfix and with the early A's ALR-45 I'm still only getting a vocal launch warning from Jester. I don't get a change in tone from the RWR for either a SAM or A2A launch, only the standard beep that I'm being painted. Is this accurate?

When I adjust the volume on the early A's ALR-45 with my HOTAS (set-up for the later A/B's ALR-67), I get a CTD. The ALR-45 is not listed in the controls.

Where was the GPS dome located on the later variants? I don't see any difference in the external models.

Yes, and more importantly than any of that, all of these issues still remain: If HB fixed the issue of ACLS not working with FFB sticks/Iceman trimming nose down when in the RIO position, all else would be forgiven.

Thank you @BIGNEWY, and thank the team for staying late please. Nothing for the Corsair? Just extraordinary for so recent and so eagerly awaited a module.

Okay, now I'm really confused by block numbers

Compulsory viewing for Tomcat fans. Great work Sir.

That was just a joke regarding how long we've been waiting for the early A. I have actually given DCS a break for a couple of months and been flying the Mercury, Gemini and Apollo missions in Re-Rentry (Reentry - A Space Flight Simulator). I was waiting for the early F-14A, to get back into DCS. I had a feeling they were block numbers, just surprised the very early A got all the way up to 95. Nothing better than a Tomcat in high-viz paint.

Time to dust this off?

Forgive my ignorance, but what do the numbers '95, 70, 75' refer to?

You mean apart from ACLS not working with FFB?

Just flying the first mission. This is literally a game-changer. A whole new experience from all the scripted campaigns I've flown. A giant leap towards greater authenticity. Things got hectic in a hurry. I should've stayed aboard the Carrier Bravo sir. Amazing work. "It's the first day of school fellas!"

Fantastic. Thank you for this Sandman. All F-14 content is gratefully received. Here's a link for anyone who wants to purchase: DCS: F/A-18C & DCS: F-14 Iron Tide Campaign

Do you use FFB? As we know the damage model is currently broken, the plane is never in a fully fixed state. Perhaps I had damaged something on the ground and there was no visual indication, hence I had this vibration. If that is the case, I welcome the new ffb for a damaged Corsair. "No initial damage that precludes take-off or landings", huh? Ask the ground crew to repair the moment you spawn in. When they're done, ask them again. You'll find the aircraft is perpetually damaged, so I don't understand what you mean by that.

I don't understand. I had a look at the files and the Corsair folder shows changes made at the date & time of yesterday's patch. I think something was patched, just not this particular problem. I have quickly tried flying the Corsair since the patch and it was shaking (visually and FFB) in the air, when it didn't before. It reminded me of the shake you get in the Mustang, when close to stall, but I was flying straight & level at 200 knots, with gear up, flaps up and cowl flaps closed. There was no reason for this shaking. So something's changed I think.

It's not the repair process that breaks the plane. It's broken from the outset, at spawn. The repair process doesn't solve the problem either. We can't test this when spawning in the air, but I guarantee no matter how well you land you'll find the plane is damaged, strongly suggesting it's damaged with an air spawn too.

I assumed (and perhaps I'm being an ass) the locked tail wheel (and for the sake of argument let's say it's currently permanently locked, with only 40 degrees of range), is spring-loaded by the nature of the suspension to return to centre, but not by a huge amount. This loading is easily overcome by differential braking and careful application of power when there's no wind, but with any wind acting on the large tail surface area it will take considerably more effort to turn the aircraft, hence the need for an unlocked, free-castering tail wheel, especially on a windy carrier deck. Isn't that what we're currently seeing, or perhaps I've misunderstood what you're saying? Plus, this: and this:

If you go to the exterior view as the aircraft is lowered from a levitation (it's shaking as it does so too, which is a bad sign), as it's coming to the end of a repair, you'll see it mis-aligns with (the tail-wheel drops below) ground level/carrier deck, this results in a sudden jolt as it realigns and I believe this keeps the tail-wheel in a perpetually damaged state. So it cannot freely castor as it should. Wind etc is irrelevant. The tail-wheel never 'works fine' as you say, never has, not for anyone. This is precisely what the Patch notes refer to as having been fixed, and it hasn't. The video below shows how the aircraft should handle with an unlocked tail wheel.

You guys think the taxi bug and the fact the aircraft is damaged from the get-go are unrelated? Occam's Razor anyone? In my opinion, this issue doesn't require separate threads, it requires consolidation. It's obvious they're related. Unlike you @OmasRachE, I am more disappointed than I already was, because the Patch notes suggested we were finally getting a fix and we didn't. I'd love to fly the Corsair and be as oblivious as @Art-J, but I don't because the immersion for me is so badly effected. I agree, it's absolutely unbelievable that this 'fix' wasn't tested before release of the Patch. I suspect it's more complex a problem than first realised, related to Magnitude's supposed bespoke damage model.

@-Rudel- The aircraft is still damaged at spawn.