Zabuzard

Jester already performs IFF by himself constantly and you also can already ask him to IFF explicitly. When Combat Tree is added, I am sure Jester will also operate it so you get to benefit from it - if that answers your question

I feel like its important to stress this fact, you are doing low level attacks. You wont have such issues lofting from higher altitude. (Which is ofc obvious but I think its easy to overlook this when reading your scenario descriptions)

Sounds like you did not export the right display, can you share a screenshot or something? Yes, the Phantom is not setup for exporting yet. So you likely will have to standby.

Difficult to tell without a track or video. The vast majority of material I have seen so far turned out to be user error because the system is complex to use and not necessarily intuitive. Generally, these radar settings you are talking about are for "general search". If Jester already found people, he leaves his general search pattern and focuses on the bandits instead. Also make sure you have not entered CAGE mode (Pilot controlled radar modes) accidentally, in which case Jester cant do much anymore at all. When he sees bandits on the screen, he calls them out (dont confuse these callouts with the ones coming from the RWR) and moves his cursor over the bandit. When that happens, he will definitely lock them up if you tell him. If he says he cant lock them, he also didnt move his cursor on anyone, never called them out (through the radar) and did not see them on the screen yet (did you see them on the screen?). Ive also seen people click the context actions too often, effectively commanding Jester to "Lock, Unlock, Lock, Unlock, Lock, Unlock, ..." within seconds. It is crucial to understand the terrain ahead in order to position yourself correctly with respect to the bandits, in particular also to increase their RCS by choosing a proper angle (dont go head-on against a fighter). Otherwise they wont appear on the screen, or just very late.

They haven't changed. I suspect your situation doesn't provide enough contrast on the target. If you can send a track, that would be helpful :)

The hotfix didnt address the cabin issue. It will be fixed soon.

WRCS integration with the pod is only available with the weapon release in TGT FIND or DIRECT and the TGT FIND switch on the WRCS panel in NORM not HOLD. Further, the pod must be unstowed, ready for use and integrated with the INS. In your case you have the weapon release mode in LOFT, not TGT FIND or DIRECT and further you have the WRCS switch TGT FIND in HOLD, not in NORM. So WRCS integration with the pod is not available and the WSOs Antenna Hand Control is instead integrated with the radar system. See TO 1F-4E-2-38, p. 2-9, 2-14, 2-31, 2-33, 2-41, 2-45, further a direct explanation for NORM/HOLD at 2-48 and the electric wiring diagram for the WRCS panel towards the pod in Figure 2-11. And also the normal Weapon Delivery manual TO 1F-4E-34-1-1, p. 1-99, 1-100, 1-103. (If you can and have the docs available, please check the manuals before you question something to save us the time digging and verifying, thank you )

There is no extra feature for such a navigation. But, as you said, you can tune in on the TACAN station and use the HSI indication to manually navigate such that you end up at the right angle and distance - usually involving intercepting the radial. That said, you can bring up your map tools, put a spider card over it and figure the coords out that way.

FYI you can also do a LOFT for LGBs automatically out of the bombing mode TGT FIND with the Pave Spike. It works trivially, similar to CCRP. Pod on target, hold bombing button, pull up, bombs auto-release at the right moment.

Thanks. This has been reported already somewhere, the team is investigating and working on a fix. Would be super helpful if someone can get hands on a (working!, try to replay it urself before submitting) track that reproduces the problem when replayed

Is that all the time or just sometimes? If latter, possibly you froze your bellows intake? What does your ingame control-indicator say when it happens? Do you have a track file, fast would help a lot :)

Are you on the latest version? There was a sign bug on the dive angle. But if I recall it had been fixed in the latest patch. Could you redo the experiment with a dive angle of 0? Cheers

Manual stuff should be reflected in the track. Its just the UI (Jester Wheel, Bombing Table, ...) that isnt - because mouse movements are not captured.

Jester currently doesnt touch the altimeter.

Correct, but it does come after the INS alignment. Jesters order is correct according to IRL checklist. You may have a point though that this list can be continued before the alignment has finished. The team will have a quick chat with the F-4E SMEs and then adjust the logic if applicable. Cheers

Yeah, sounds reasonable. Also something that modders could add with Jester modding if HB isn't fast enough :D

No need to bump. It is in the backlog where it can't get forgotten and it will be delivered eventually [emoji108]

Did you use the bombing table in your flight? Replays don't capture what you did there, consequently nothing was entered into the WRCS panel during the replay. When you replay the track you need to press ESC when the tool opens and enter the same data again manually and press the button. Only that way your replay does the same as it did in the true flight :)

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) :)

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.

Thats the kind of micromanaging that we want to avoid. The plan is instead to add a superior and more general way of pointing Jester at targets. Think of a "Jester, look here" where you point in the sky or on the radar screen or on the rwr screen or similar. Further, Jester will learn to incorperate more data into his search behavior, for example AWACS calls, RWR, mission data and so on. So that he is able to find targets more proactively than now where he only performs a general search pattern. The majority of F4 WSOs hated 2-bar mode for various reasons and always used 1-bar instead, while controlling the elevation by themselves. In 2-bar Jesters logic doesnt really work well anymore, so such an option likely wont be offered soon. And again, its micromanagement that you, as Pilot, should not have to do. Jester will be improved so you can focus on doing your Pilot job instead.

It is because MS and friends processed the whitelisting requests. As explained throughout this and other threads, the problem is the Antivirus Software incorrectly detecting a virus in the DLL files and it takes them a few weeks to process the request to whitelist the files. If you have not made an explicit exclusion rule on your side this issue will likely get back to you in a future update that changed the DLLs again in a way that the AV software thinks its a virus again. And then it will eventually go away again as they processed the request.

There is no workaround for this bug. Wait until the needle on the gauge caught up and he stops.

The team and ED first have to design a proper solution. As explained, that file serves a good purpose. This will most certainly not be resolved in a "hotfix", no.

Yes. That cache file remembers the names of all sounds the F4 is supposed to contain. So if you add files with new names, due to that cache mechanism, they are ignored. If your new files replace the existing sound files, i.e. same name, they will get loaded again. I am talking about the new file DCS/Mods/aircraft/F-4E/Sounds/sdef.tar. If you look into the file, you can see it contains all names of the original sound files. DCS uses that file to speedup loading times. If you delete the file your loading times will be back to how it was before the update, but custom sounds (with new names) will be loaded again.