Zabuzard

It happens during taxi because putting it into STANDBY will start the heatup, leading to the radar melting if you take your time on ground.

aaand fixed, available with the next time HB uploads a build to ED 👍
the trigger signal was correctly send to the A2A weapons but the pylon wasnt armed.

Development is continuing and we have shared a lot of new features, bugfixes and additions to the F-4 in our Discord over the past weeks. Most of them are also already in the manual, if you want to read more about it there: https://github.com/Heatblur-Simulations/f-4e-manual/releases
To list some of these additions: EFB, Maverick Gyros, Combat Tree, Zunis, Aircraft Persistence System, ...
All of that will be available to you as soon as we finish testing. Unfortunately, this step takes us a bit longer than expected this time. But it will eventually be ready and then you can get your hands on it 👍
In regards to the DMAS, there is currently no news or ETA that can be shared. F-4-wise the focus currently lies on delivering the MSFS F-4 (a lot of recent bugfixes and features for the DCS module are a byproduct of that).

Yes, this feature is called "focus" in Jester for the F4. You can use the context command (V) or the Jester Wheel for it. Details in the manual:
https://f4.manuals.heatblur.se/jester/combat/radar.html#target-selection

An actual realign isnt possible that easily and would require a lengthy procedure.
It is possible to do a nav-fix though, similar to how you would do it in-flight when overflying a nav-fix waypoint. Jester support for that on the ground is in the works. That will only get rid of your current accumulated drift though, not realign anything. So you would accumulate new drift quickly again.
The Jester Wheel already features an option to "upgrade" your alignment in case you for example didnt do a full alignment beforehand. Further options are in development.

Fixed the issue. Available with the next build, cheers 🙂 
Looks like DCS changes lead to the CATM not reporting "is infrared seeker" in the API anymore. So our F4 code didnt recognize it as Sidewinder variant anymore.

The trimming behavior is implemented correct with respect to real life behavior of the aircraft. You gotta do very short taps, it was known to be wonky. The response by aircrew usually was to "just fly the aircraft".
That said, there is a Special Setting available to counter this especially for people who have hardware that physically cannot send super short impulses. Like, for some joystick even if u you click something only for a very short amount of time, the actual impulse send by the hardware to the system is much longer.
I believe it was this setting: https://f4.manuals.heatblur.se/dcs/special_options.html#stick-neutral-position-smoothing-period
(Trimming in the F-4 acts as a modifier of the lever that the bellows use to pull the stick aft as opposing force to the bobweights who push the stick forward, and is hence heavily dynamic and dependent on factors like speed and G)

What the others said is correct. Unfortunately, the in-game experience with what the tanker tells you is misleading.
After an accidental disconnect the tanker is not allowed to connect to you before you cycled your door (restarts the AAR system). This is mandatory to do in The F-4 (IRL as well, ofc) before it can receive fuel again.
The tanker in DCS doesnt yet understand this special situation and will gladly put the boom in again - just to immediately receive a message from our code that he must not do this. The tankers reaction to that code-wise currently seems to be to disconnect and conclude you are fully refueled and happy. ED is aware and looking for a solution to improve the user experience.

Yes, it is modelled. The electric system is simulated down to volts, watts and individual wires. This is also why Jester specifically waits and asks if you are done with moving the generator switches around before he starts the INS alignment.
A more indepth look (but still an approximation) will be available with the next Phantom build that features the EFB (more specifically its Electrics page) - details in the manual. Cheers

Make sure you click with your (real) mouse into the field first so it gets keyboard focus.

The blades you are looking at are fixed (IRL and ingame) 🙂 
The actual compressor blades that move are further down behind the blades you see.
See here: https://youtu.be/Or6mIaSWZ8g?si=9bSqzVlPkqCTmqhG&t=33

It will be available with the next update :)

Hey there, this is a known issue. It can safely be ignored for now. Fortunately, modern browsers are resilient enough these days.

Yeah, this has been reported somewhere already. Its on the list, cheers 👍

Note that you can "read" the target altitude also through the antenna elevation symbol plus the distance. All crew trained to do this within seconds so they can leave the Aspect Knob to display Vc the entire time (the single most important value).
The rule of thumb for that math is: delta altitude = antenna angle * range
Example: target at 10nm, antenna elevation pointing 5° up, gives you 5 * 10 = 50 (x100) ft. Your target is 5k ft above you.
But as said, there is a plan to provide the info you are looking for. Likely through some sort of a "Hey Jester, where is the target?" thing - which would then also work in other contexts 🙂 

For the tracks to work you need to enter the bombing table details during the track again. Because their input is not captured by DCS tracks. If you do not do that, it is as if you never used the bombing table and hence your bombs drop immediately.
You can for example press ESC during the track replay, then enter the details quickly and hit "tell jester" and then it will work.

Sounnds like you opened the Jester Console (RCTRL+L), not Wheel (A).
Please doublecheck your binds, thanks.

Mind sharing the mission file or a short track of your attempt? Im sure we can easily identify whats going on that way 👍

The bombing tool does not include loadout currently (for technical reasons). You have to add that yourself.

Yeah that's what I meant. I believe this video was edited and did not have the tone in the actual gameplay either.
(I remember people talking about it on Discord when the video came out)

Offset mode utilitizes the INS data, so your speed and altitude is not of a concern as long as it matches the speed and altitude you used when computing the drag coefficient right at the moment of release.
But yeah, this mode is more meant for attacking perhaps a factory facility or something - and ofc with multiple other F-4 in trail 🙂 
Same here, also based on INS. So you just need to ensure your profile at release matches the data you used during planning or the weapons ballistics will be off.
By the way, you do not need to visually see the target as long as you have another way of determining you are right above the IP. So if its a landmark or you use your TACAN or a waypoint (ofc a bit less accurate) you can also use laydown mode without seeing the target. The technique with depressing the sight and pressing the button once it aligns with the target is very neat but optional - it is just one of many ways how you would know that you are right above the IP.
Should be, yes. Maybe someone else from the team can provide you some details on it.
Yes. Essentially all bombing modes in the F4 are fully implemented. There are currently no known bugs with them. (The bombing tool has some known bugs though, but not the systems in the aircraft).
Worth noting that a lot of the loft modes are meant for nuclear delivery and hence do not need to be very precise. Since they are all timer based and not using the INS you indeed need to fly the profile accurately all the way.

Are you sure you actually have to hit the lower part? Afaik the full center area is clickable already.
That said, there is also an extra back bind. And if you hold the Jester UI Action bind (A) long, it will close the wheel (no need to navigate back all the way).
Worth noting that you can adjust the sensitivity in the special settings (max angle).

CAGE mode is a pilot controlled "panic" radar override (for when you get jumped by Migs). It is 5nm only.
You need to explicitly leave CAGE mode again to get back to the normal radar modes. You do so either by moving the Weapon Knob in or out of the B position or the WSO needs to press the A2A button. Jester can do latter if you press the context button twice.

That wont help you much as the update included many more changes than swapping out a few sound files. The entire code was changed and improved. So replacing sound files would not give you back the old behavior.

It is a limitation of how the Jester Wheel is currently coded. I.e. it is missing another page.
UI aside, there is no limitation.

The aircraft itself isnt able to store waypoints (besides one) anyways. Jester memorizes them and enters them as you fly around (leap-frogging) :)