Zabuzard

Because its more complex than that. Either case, not really something you need to worry about. ED and HB will work together to fix whatever problem there is.

Can you check in the mission editor the "Reference Aircraft" checkbox and see if it still shakes then?

It is #1 though. The Viggen does not decide who is Jamming and who isnt. DCS does. The Viggen reads the "isJamming" flag from units and these ships respond with true for that. So DCS decided that those ships are jamming, consequently the Viggen "triggers the jamming effects" for that unit.

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.

The radar cursor is moved using the Antenna Hand Control Stick in the WSO cockpit. The Weapon Slew mini-stick is for the Pilot to move weapons like the Maverick. I would recommend going through the manual when you find some time, cheers. https://f4.manuals.heatblur.se/f4e_manual.html For binds we recommend our binding guide in the manual: https://f4.manuals.heatblur.se/dcs/controls.html#binding-guide

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

Difficult to provide. But it has priority.

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

The F4 does not have a pulse-doppler radar. It cant be "notched". Maximize the targets RCS by approaching it from the side. Reduce clutter by looking at it from below or move the entire fight over sea. Theres a lot of things to look out for and learn. I am afraid there isnt much more assistance that can be provided without a concrete track or at least a video. I understand your frustration. But this can be solved by learning and gaining more experience [emoji106]

Jester cant lock a target that is not showing up on the screen yet. The command will work as soon as there is a target on the screen - Jester then also announces it and moves her cursor on it. Approaching a fighter head-on at co-alt is a very bad position to be in. And possibly with mountains or ground at the same distance, adding clutter around the expected target and making it hard to pick a proper gain setting that could differentiate the target from the rest only makes it worse. For fighters specifically, you can expect to spot them at around 15-25nm if you are doing it right, for big targets like bombers perhaps 30-40nm. If you do not see the target on the screen yourself then its usually the pilot to blame, Jester cant do much then. Try approaching them sideways and from below, be mindful about where mountains and ground clutter are and also your own altitude, make sure all of them are at a different distance than the target. If you can't get the target on the radar screen so Jester could work with it, hit the CAGE button on your throttle to enter the pilot commanded dogfight radar modes CAGE/BST and CAGE/CAA. Especially former allows you to lock a target by simply putting your nose on it (5nm). You can also enter the regular boresight mode through the Jester Wheel to do the same for up to 10nm (realistically rather 7nm). If you can produce a quick singleplayer track we could give more specific guidance [emoji106]

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.