Zabuzard

It isnt supposed to. But if it gets better after checking that "Reference Aircraft" option then it most likely does and then thats something we can potentially fix.

Yeah but the aircraft behavior should be deterministic within the same DCS version. So I am thinking what the cause could be. Perhaps its the Wear/Tear/Condition system, which is why I am asking to see if it gets better with "Reference Aircraft" selected

Do you happen to have a mission file or even video to share? Would be useful [emoji106]

Note that you can "read" the target altitude also through the antenna elevation symbol plus the distance. All crew trained to do this within seconds so they can leave the Aspect Knob to display Vc the entire time (the single most important value). The rule of thumb for that math is: delta altitude = antenna angle * range Example: target at 10nm, antenna elevation pointing 5° up, gives you 5 * 10 = 50 (x100) ft. Your target is 5k ft above you. But as said, there is a plan to provide the info you are looking for. Likely through some sort of a "Hey Jester, where is the target?" thing - which would then also work in other contexts

That exists already. Look under the Jester Commands. And there is also the Context Button that allows switching through that conveniently with just a single button. See the manual for more: https://f4.manuals.heatblur.se/jester/combat/radar.html#dogfight Or are you talking about the ability to see the targets data and not the aspect settings for no-lock shots? That will be handled differently to achieve a better UX.

The AVTR is currently using more something like a demo implementation than what we actually envisioned for it. Unfortunately proper video recording is not that simple to get working. It is planned though to fully fledge this out, at which point the F4 will also receive its iconic gun-camera. The TARPS could follow after, will see. But currently not planned/promised. Cheers

Yeah... it is super unfortunate that DCS cant natively capture the UI interaction in the track. Hopefully the team can find a way to get it working in the future.

Sounnds like you opened the Jester Console (RCTRL+L), not Wheel (A). Please doublecheck your binds, thanks.

I understand that you are curious as to how things work under the hood. However, going into those details would go beyond the scope of this thread and likely also touch topics under NDA. Perhaps another time. For now lets focus on the experience. So if you find a bug or something that seems odd, please continue to report it and it will be fixed eventually

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