primus_TR

That's what I thought also. In that case, it should not matter for Shrike where the tracking radar is directed at: me or some other target.

It is strange than how the shrike has zero difficulty hitting a rotating search radar; if it is indeed following the beam, it should be swayed by the rotating beam. That is not the case right now. I can hit a p19 without fail every time, but not the tracking radar. Based on what is described above, a split S would push the tracking beam down, and a lofted shrike, which would be way above the beam, would have zero chance acquiring.

I wasn't aware that shrike was a beam rider. Looks like this connects with the side lobe discussion above. Thank you.

So, the targeted radar must be tracking specifically the platform who launched the Shrike, for the Shrike to be able to continue tracking the radar?

That explains everything Good to hear that Shrike behavior in game reflects the reality so closely lol!

If I recall correctly, you need to use the Tail or Nose/NoseTail position of the arming switch to select between one of two fuses. It is also specified on the arming screen.

A 21bis without an imaginary look-down, shoot-down capable radar would be a plus.

After improving the current 21bis with a proper radar, why not?

Maybe put this important piece of information in the Corsair section, rather than under an obscure title as 2025 Post Release Updates in the general M3 forum? It'd be also a good idea to post module-related information on the DCS forum also.

So which kind do we have modelled with the M3 F4U and what is the correct mechanization and methodology? Best not guide players to rely on real world manuals by posting excerpts without commentary when it is not clear to what degree and in which specific respects the module correlates with the real world behavior of the real world aircraft.

Glad to hear The fix wasn't mentioned in the notes, hence my post. Will give it a try.

Correct me if I'm wrong but based on the update notes, the fix you mentioned didn't make it into today's update Any timeline on when we can expect a fix?

lol Side or not side, it is unable to reliably track anything. I'm sure 'skill' may be also an issue, but the agm45 is perhaps the crappiest weapon in whole of DCS.

Yes. After the last update, taxiing has been marginally improved but remains problematic. It should spin readily with differential breaking and a very small amount of power. Currently, you need nearly full throttle for making a 180 turn when stationary.

A naval F4 from HeatBlur would be amazing.

I use the boresight/cage mode to lock a visual contact, which gives the most reliable lock for a sparrow shot. Locking and maintaining lock in search mode is unreliable. It's also great that I can IFF a locked contact to make sure I'm not shooting at a friendly. Aim7Fs work nicely both up close and at range. Flood method also works great if you have selected the correct aspect/speed gate and are within 10 nm of a hot target.

Why does the aircraft pitch up when I retract the flaps? My experience is limited to small Cessnas and flight sims, but normally retracting flaps causes loss of lift and the aircraft sinks as a result. Is this a peculiarity of the Corsair?

I have noticed that the AGM45 has a new setting in the seeker head settings screen: WP Marker Charge, where you can choose Installed or Not Installed. Does anyone know what this setting does?

For me, the bug has been resolved after this update.

Great to hear! Thank you!

The nav signals are all over the place. When I am north of the carrier, it broadcasts S, instead of an R. Half the time, the signal is accurate; in some cases, it gives you the opposite direction. They really need to look at this issue, as radio navigation over the ocean (without F10 gps) is a key attraction of this module. At this time, it is completely unusable.

I did more tests with the F4U and the F14, and based on my observations, I can confirm that a carrier trap will not cause a crash, only if an inbound contact has been made beforehand (as so previously reported by @Scotch75 and others).

I wouldn't touch any thing from Razbum with a 10 foot stick. They're done, but they lack the faculties to realize that lol

With the Corsair, I had had landing clearance (the stock instant action carrier landing scenario); with the F14, I always contact the carrier for landing clearance. But strangely enough, last night I tried an ACL approach and this time DCS did not crash. So, this is one weird bug for sure.

Since the last patch, F4U and F14 both cause a DCS crash when the hook grabs the wire.