Zabuzard

Dont want to be that guy but from reviewing around 30 user reported tracks on that matter, it usually turns out to be user error. Mostly due to not understanding how the radar works, what its limitations are and sometimes also misunderstanding Jester. If you can share some details, ideally even a track file, I am sure we can get you on track asap As it stands currently there is not much in your thread we can work with to identify the problem and improve your experience.

Hey there, this is a known issue, already reported somewhere on the forum. Thanks and cheers.

No change since my last message above yet. Cheers

That is correct, these commands in the wheel will not have Jester claim UHF command. This is on purpose as the normal approach to using the UHF is to setup both pits with frequencies and then hop between both using the CMD button in order to be able to talk to two frequencies - which would otherwise not be possible. So after setting up Jesters frequency with something you can hop between yours and his frequency by using the COMM button on your panel.

If someone manages to send a short working SP track we can probably resolve the issue quickly (user error or actual bug)

That would probably fit better with adding a bind and adding persisted custom startup configurations. Something already planned down the road. Either case, since its in munkwolfs binds it will be added to the aircraft eventually [emoji106]

I wouldnt be surprised if such a bind already exists in munkwolfs community bind mod. If something is clickable it can also be offered as a bind rather easily and the bind files are all open to modding as they are just lua files. Since we will eventually add munkwolfs binding mod to the module like we also did with the Viggen, it would eventually get fixed that way.

Nothing should have changed. And works on my end. So yeah, need some details or a track file :) Is there a human WSO or are you flying with Jester?

Go to the F4 Special Options and play with the Resolution Override (for scaling) and the Offset X/Y (for placement)

A DCS track it would be then. As that allows us to replay the DCS scenario while the debugger is attached to inspect everything going on internally Mh, odd. But glad you figured out something

Would be surprising as none of that code was touched. You got a track at hand? Usually these things turn out to be some form of user error as there are soo many ways to mess up (no offense btw). Either case, a track would be supreme

The planned Tomcat variants are the early A and the B(U).

No ETAs, sorry.

Rip. Could someone supply a quick singleplayer track showcasing the issue? Makes it easier for the devs to work on a fix, thanks

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