Zabuzard

This is intended and correct behavior. Kindly see the manual, thanks:
https://f4.manuals.heatblur.se/cockpit/pilot/weapon_management.html#flight-instrument-brightness-knob

This is intended behavior as the intermediate position would otherwise result in the frequency 220.00, which is outside of the supported range. So the knob "blocks".
You first have to move the third knob to 5, then you can move the second down to 2. In general, prefer setting the frequency from right to left.

They would have the flight on COM and the other forces and commands on AUX for receive-only.
Then, when needing to talk to the AUX people, they would have these channels on COM as well and switch there quickly for talking.

A neat trick was to setup for example channel A on COM and B on AUX of the pilot and for the WSO the other way around, channel B on COM and A on AUX.
That way, by simply clicking the COMMAND button, one could swap talkinh between both channels by transferring which panel is in command and always still listen to both channels.

Actually... I thought a bit about it and dont see any issues by just offering the reversed orientation for all 2-way switches in the entire aircraft.
So here we go, you now have 128 new binds that you can map 😆👍

Thank you, all of that is already in the making. Cheers.

Thank you. Its the manual to blame.
The thin needle is the Nr.1 needle and the thick is Nr.2 needle.
Will be fixed asap 👍

Thank you, this will be added.

There is a common misconception with the yellow ADI needles.

They are not the ILS signal but the flight director, which is a different system.
The actual ILS signal is shown on the sides, no needles.

A home bind has been added for the upcoming patch.

Voice compatibility for the wheel is a feature that is important to us. Which is also why so many of the actions now have direct binds that can be used without having to navigate the menu at all.

Aftterburner has a range as well. Full and minimal afterburner provide different thrust.

Fixed 👍

thanks, known issue. will be fixed :)

Its on the left wall, a black switch mounted on a weird looking yellow/black striped block.

The difference is actually so subtle that you would barely notice it at all unless you know what to look for and have a direct before/after comparison.

Yes, it affects Jester in the same way because Jester isn't cheating. He is interpreting the smudges like a human based on the final image.

Correct, this topic hasnt been addressed in this patch. It is still on the list of things that will be improved. Cheers

The crash occurs when you enter empty coordinates and has been fixed for the upcoming patch :)

To enter data, you need to have the pit field focused. Try clicking it with the mouse.
Then use the number keys above qwert to input something. Improvements regarding the focus and input are planned and on the way.

"Just giving a bind" isnt a good fix for this for a few reasons. Mostly because it will confuse and partially break Jester and he will also constantly reset and fight it.

It is easier (and planned) to just teach Jester to operate the knob properly on his own, without you "playing wso from the pilot seat", than it is to teach him to support players messing with his knobs without consent.

That said, in the meantime you can just add the bind yourself by copying it from the Dcs/Mods/F4E/Input/Wso/keyboard/default.lua to the pilots lua. (u can do the same with any aircraft in dcs)
But be aware that it's a hacky solution that will have the above mentioned issues. Cheers :)

Known issue, thank you. Will be fixed

The bind is missing until the system can be implemented.

It redirects hot engine bleed air across the canopy, heating up the canopy and blowing away rain.

It must not be used on ground to prevent overheating and melting the canopy, there is even a warning lamp for it :D

Currently, the Phantom dkesnt yet support EDs rain system due to some technical difficulties that will hopefully be resolved soon. Unfortunately the system doesn't offer us to interact with it in a way to implement "rain removal" yet.

Thank you for your work! :)
We will put in the same or similar changes.

Cutoff issues in VR can be fixed by selecting:
Use DCS System resolution, BOTH EYES, a graphics resolution that isnt too low /such as FULL HD), then resetting our HB UI special options that you might have messed with, and then (mandatory) restart DCS for the changes to take effect.

In the meabtime, ED is working on a fix for the ubderlying cause of the issue :)

The Pave Spike is fully implemented indeed. It is just that Jester has not learned how to use the pod much yet. So you have to do these advanced things with a real WSO instead.
As AvroLanc describes, the WRCS mode will let the pod look at the current WRCS target. You can set such a target by using the FREEZE/INSERT buttons. You can either create it via OFFSET coordinates to a known position (IP). Or by using the radar offset cursors, provided you can see the target on the radar screen.
Latter also allows you to guesstimate a target position quickly if you for example get a relative call like "the targets are roughly 10nm from your position, 30° to the right". Then you can just put your radar offset cursors at 30° right, 10nm out and enter. And boom, your pod will look in the general target area, easy.
Now, if you are flying solo with Jester, he supports only the 12-VIS ACQ mode. Allowing you to put your target area on the nose, hitting Jester Context Button and he lets the pod enter TRACK mode. From there on, you can then fine tune the pod yourself (using the provided binds), search for targets, lock them, fire the laser, ...

You would need to be precisely parked at exactly the same spot where you parked and stored the alignment before for this to make sense.
A stored heading alignment is executed by ground crew previously sitting in your jet, executing a full alignment for this exact geo-position and then shutting the aircraft down again while memorizing the alignment. Meaning, as far as the jet is considered, there is no shortcut - someone (ground crew) executed a full alignment in it. It is not meant to be used for subsequent starts.

First of all, make sure you are under the F-4 WSO binds, not the Pilot binds still.
Generally, as WSO, I would reocmmend binding your joystick axis to the Antenna Stick. So to the X/Y binds in the Axis Section of DCS. The Antenna Hand Control should move ingame now whenever you move your joystick.
If you also occasionally want to fly the aircraft from the rear seat, I would either bind the flight stick to something like keyboard arrows, or bind the axis also to the joystick, but with a modifier. DCS offers two modifier categories: Switch (toggle) and Modifier (hold). That way, you can essentially bind one axis or button to multiple functions.
If you need further help, it would be helpful if you can share some screenshots of what you are binding. Otherwise it is hard to follow what you are doing 🙂

The standby compass lighting is WIP and will soon be added 🙂