DSplayer

IRL you need to press the Weapon Selector to switch from Sparrows to Phoenixes. In DCS, they've provided an option to switch from SP to PH by going up again on the Weapon Selector but this requires you to double check your Special Options to make sure the IRL option of requiring that Weapon Selector depress is disabled.

I think it would be best to create your own thread since this a 5 year old thread discussing something else.

Idk what you mean by napalm bomb effect since such bomb doesn't exist in DCS rn.

Unfortunately the napalm bombs on the A-4E-C community mod is basically just a cluster bomb dispenser.

Would require DCS to add it unfortunately.

From GAF TO 1F-4F-34-1 page 1-157 it describes that the case/cartridge on the SUU-23 is ejected from the lower left side if the pod with sufficient velocity to clear the aircraft.

Iirc what I’ve found is that after firing one Sparrow, attempting to jettison that specific missile would result in the sound for jettisoning being played but nothing actually falling off the plane.

Hmm, nothing has changed in the files for any of the AIM-9s or R-3/R-13s that would change the FOV. Maybe it's an F-5E specific issue? Would it be possible for you to downgrade to a previous version and test it out?

Tested it out and it seemed like there wasn't anything breaking the mods.

I'll give them a look and see what's up. Probably broke because of a recent patch but I don't know if any changes actually would cause the mods to stop working.

Against an SA-3 site that is set up with a Flat Face SR and the SA-3 Low Blow TR, I would personally take the Mk 37 to take out the Flat Face (since it has a pretty unique low RF relative to the rest of the Soviet SAM radars), and a Mk 49 of any Mod for the TR since it covers what the Mk 36 does and more. I personally haven't had issues with the Shrike not tracking the Low Blow at certain angles however like what I had with the Hawk TR. I would refer to the new tables included in the F-4's manual for more details but like what I said in the bug report thread that Northstar linked, sometimes Shrikes track even though they don't give tone.

Yeah I'm using the "Full Action (button)" keybind. I attached a track in the original post that hopefully would be able to help but maybe a video would be better in this case since it seemed very inconsistent when it would enter a track. I didn't have any issues manually using the "Half Action (button)" then "Full Action (button)" very quickly to get a track however so it might be a timing issue like you said. One thing to note was that I wasn't having an issue with Pave Spike and firing the laser will the same keybind.

When using the antenna hand control's trigger, I have an issue where if you only press full action (and not pressing half action) on the trigger, it doesn't always enter a track immediately but it sometimes does it. Shouldn't using that keybind be similar to going through half action and reaching full action very quickly? I'm using the button keybinds and not the 2-stage trigger binds. I have a joystick that lacks a dual stage trigger so binding dual stage triggers are a bit wonky sometimes. F-4E_WSO_HCU_Trigger.trk

Sounds odd, i can doublecheck on Monday. If you can send me a mission or track that would be helpful in case I cant reproduce it myself for whatever reason. Cheers For sure! This track is made using the same mission that I used for the previous track provided in the first post F-4_ECM_Hotstart_3.trk

Just did a instant action mission and it seems like this still occurs in the latest patch. Double checked in a mission I made and I still have the issue in all hot starts.

Just did a sanity check test against the Hawk TR and just noticed that Shrikes, for some reason, only track it when below a certain altitude (even if its illuminating and launching at you). Another problem I've noticed is that for some reason, the Mk 50 (which according to the DCS LUA's frequencyRange) tracks even though it should be outside of its RF limit. I wasn't able to test every single Shrike against it at low altitude however. F-4E_HawkTR_Tracks_Only_Below_certain_Altitude.trk

Something that ED would have to change unfortunately

The Mk 22 shouldn't be able to go after the Flat Face search radar (and it didn't exhibit that behavior when I tested it).

I believe so yes. The ALE-46 isn't that sophisticated that it can exactly separate tracking from searching modes like modern RWRs but the Fan Song should only be used when it's tracking a target. For ships and combined STR units, you can set their AI up so they don't track you by making them go weapons hold so that's how I tested search radars individually where you couldn't separate them from track radars.

Here are some tracks with some scenarios that I came across while making the table. In the SA-2 track, only the Mk 22 seeker (on the #1 pylon) provides tone and track on the Fan Song (SA-2 track radar) while the other 3 (Mk 23, Mk 24 Mod 5, Mk 24 Mod 34 respectively) track without giving tone at all. F-4E_Shrike_SA-2_Tone.trk In the SA-19 track, this track has a similar issue to the SA-2 track where the Mk 23 seeker provides tone on the SA-19 and tracks but the Mk 24 Mod 5 doesn't provide tone and still tracks. This track also has the added issue where the Mk 24 Mod 34, which has a wider RF limit bracket that encompasses a wider bracket than the Mk 24 Mod 5 but narrower than the Mk 23, doesn't track the SA-19 at all even though it should since it should cover the same RF limit bracket as the Mk 23 and Mk 24 Mod 5. F-4E_Shrike_SA-19_ToneANDTracking.trk Another example of that is the Mk 36 being able to track the SA-10's tracking radar (Flap Lid-A) even though both Mk 49 seekers have an RF bracket that encompass the Mk 36's smaller RF bracket. F-4E_Shrike_SA-10_Tracking.trk Another problem encountered is that some radars seem to be trackable with all seekers for some reason. This can be seen with the SA-2's Amazonka rangefinder which can be tracked with any Shrike seeker model. F-4E_Shrike_SA-2RF_Tracking.trk Another problem encountered was the Shrike providing tone even though it didn't track the target. This can be seen with the Mk 23, Mk 24 Mod 5, and Mk 24 Mod 34 which all provide tone but all fail to track the Tarawa. F-4E_Shrike_Tarawa_No_Track.trk

I was trying to modify the "limits_6DOF" in order to more easily look around in the cockpit for switches. This works for other aircraft like the F-14, MiG-21, etc., just not the Mirage F1s. Here's the excerpt from my Server.lua (from Saved Games/DCS/Config/View/Server.lua):

Currently the AGM-45 has issues where it produces tone and doesn't track a target and sometimes it tracks a target without providing tone prior to launch. This is possibly connected to the AGM-45, for certain threats, tracking targets with all the seekers (such as the Fire Can radar being trackable with all the seekers) and the opposite being true (where even though the target can be tracked by one seeker, it cannot be tracked by another which also covers the same RF limit bracket as seen with some targets with something like the Mk 50 seeker and seekers that overlap with its RF limit bracket). Refer to the F-4 manual page https://f4.manuals.heatblur.se/stores/air_to_ground/missiles/shrike.html#seeker-heads which I created based on individual testing with Shrike seeker variant against almost every radar available.

Currently, the ALQ-131 requires warmup even on all hot starts and on all pylons. Track with all hot spawns attempted: F-4_ECM_Hotstart.trk

Currently the BLU-107 isn't listed in the Bombing Table/Computer even though it is listed in the manual. Excerpt from the HB manual (https://f4.manuals.heatblur.se/dcs/bombing_computer.html#type-of-bomb) In-game bombing table screenshot

What's occurring seems to be your lack of dive angle input in the bombing computer which provides a drag coefficient of 0.00 to Jester which he latter inputs into the WRCS (as the drag coefficient is required for DT). In both cold and hot starts, it appears the WRCS' drag coefficient is set to 1.02 (which is roughly what Mk-82s are in typical DT weapon release conditions) by default which is why you're seeing hits without the bombing table. What I typically do is put in a rough approximate dive angle and that is fine since the only bit required for DT is the drag coefficient. Hope that helps.