Zabuzard

Definitely possible, yes. Without track hard to tell though. But that would be my guess as well.

But are you saying that you still hear a clunk sound when you "jettison" an already empty bomb rack (which then correctly stays on the aircraft)? That could be a bug then - playing the sound even when there is no ordnance to jettison anymore.

This is a known bug that happens in certain situations. Try out the radar performance special option. Afaik it gets rid of it.

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.

(JFYI, no one implied that)

Either case, afaik it was fixed internally. So lets just wait for the next patch :)

Yeah, bit hard to read. Nothing jumps my eye though. So we probably need a trackfile instead. You may also share a screenshot of your trigger binds, possibly you bound the wrong thing (1st stage, or using a physical 2stage on the button binds instead etc)

(That feature is broken since DCS moved to multithreaded. It is unlikely to come back.)

Could you share a screenshot of the pilots front cockpit area? Usually that solves the issue (Track file would be great as well of course)

Hehe, glad to have helped out. I get what you mean and I had the same concern when designing it. Couldnt come up with a better UI that still has the center area free for "Jester Wheel INFO" and "Jester Wheel User Input" (two features which are used occasionally in the wheel that take the center area).

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

No ETA. The jet is not arround the corner, module development takes years. Cheers.

How did you determine this? In multicrew with a human pilot and a WSO? Or by sitting in the rear seat and moving your head so you can see the front area from behind? Or by binding the WSO switch to the pilot controls and clicking them from the front magically? Or by sitting in the WSO seat and going external view (F2)?

Could you share a screenshot of the pilots front cockpit area when you are in that situation? Usually that answers all those questions. If the racks are an issue your CTL INTL lamp would be on.

I doubt that will happen as it would mean HB needs to officially support a weapon that this aircraft could never use (even if someone would hang it on a real F-4E). I understand you wanting to cosplay another Phantom variant though. Cool that the mod at least lets you fire it and it works even though the aircraft has no code to support it.

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)

I have no experience with the mod, but did you witness the tone in-game before? Or did you only see it in a video? Cause some of those videos are edited, adding sound effects. I've seen that a bunch of times before.

Our F4E is not supposed to carry HARMs. If you got hands on a mod that allows you to carry it, it is not official. Either case, whether a weapon works or not is decided in the C++ code, not in Lua. Lua allows you to visually add anything you want to any pylon, but that is not enough to also make the weapon "work". That requires the actual aircraft code (C++) to understand and explicitly support the weapon. Which is something only Heatblur could do, not modders. If a weapon happens to "just work" regardless (often the case for dumb bombs), its coincidence and any future update to the aircraft might "break" it.

Could you share a screenshot of the binds you are using please? That would be helpful, thanks

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.

This is a known issue and the team is already working on it. Partial fixes had been pushed already as well. It happens on subsequent spawns and the exact conditions vary depending on DCS version and selected mission (for the coders: its so called "undefined behavior").

Can you show a screenshot of your ministick binds? Ensure you are maximally deflecting the stick, the threshold where its supposed to jump to the outer ring is afaik at around 90% or so.

Yeah. So the upcoming patch will include slight changes to slat behavior in such configurations IIRC and also plenty of hydraulic fixes. So possibly after the update it might be better. But in general it is definitely correct behavior that you can end up in a situation with the slats going out, that causing you to change angles and speed, causing them to go in again and vice versa. IRL they would just grab the stick and throttle and just change the setup so you are not crawling around this edge case anymore.

Generally, up and down is completely normal behavior for the F4 (due to bellows vs bobweights). That said, there are known hydraulic issues in the current patch which are already fixed internally for the next update. Possibly you had your slats extending and retracting constantly (which btw is correct behavior in certain situations and is countered by simply changing the current flight configuration - make sure that your tanker flies at a speed that is appropriate for the F4 and not around a speed that triggers this situation for you).