Zabuzard

Worth noting that you have to be careful when you compare with other aircraft on YoutTube etc. The Phantom shown in the video is not the same as the one we have in-game and features some quite important differences when it comes to FM behavior. And even within the same aircraft variant there are different configurations leading to different results. For example the AOA unit conversation and especially the bellows/bobweights system had been adjusted and tuned a few times. We have observed similar when people compared the exterior sound with videos of F-4, not knowing that those have the BLC producing a very distinct sound. Im not an expert on the topic though, so I leave it up to someone else to elaborate.

The latest update on Discord was that the artwork/model is done and that integration work has begun. Latter mostly includes the main lua files, including loadouts/pylon definitions, FM parameters and similar properties. Cobra recently posted that the top priorities right now are the A-6E AI, Jester TGP for the F4, the early F-14A and of course also the F4 for MSFS. As you know, there arent really any official ETAs at the moment. So please stay stuned, cheers.

This particular patch had no changes from HB. According to Cobra (see Discord), a larger July patch is being prepared instead.

It is slated to release before the other stuff.

Dont forget to setup the Bombing Table tool with your planned release parameters (at least roughly), so that your computer uses an appropriate drag coefficient. Otherwise your bombs will miss. Unless you are flying an uncommon attack profile (shallow angle, high altitude, high drag - anything that increases impact of ballistic physics) you do not have to fly the parameters exactly. But they need to be roughly right at least.

Definitely the second.

Please open the Control Indicator window to make sure you are actually "holding" the stick full aft. You can also check the stick visually in the cockpit. Because due to the bellows/bobweight system as soon as you land the system will start to push the stick forward as your speed decreases. Which means you have to progressively increase the strength with which you pull aft to counter the system.

No. But Jester modding is available by now. So if a modder feels fancy, could create that feature yourself and share it with the world :)

Thanks for your feedback. Please note that the weapon itself is an ED topic. So best post it on their forum section so they have a chance seeing your feedback as well [emoji106]

We tried that but couldnt get hands on the creation time. Same with author. Needs someone to sit down and figure things out and likely also talk to ED. Which the team didnt get around to yet. But its on the list :)

Most likely latter. Or you interfering with the sequence in some way. Could you throw a quick track file at us, would be very helpful, thanks :)

Its being worked on. It is planned to be Heatblurs next DCS module. No ETA.

FYI, have you seen the binding guide section in the manual? https://f4.manuals.heatblur.se/dcs/controls.html#binding-guide

Hey there, thanks for the report. This one is actually correct since those switches are located on the Fuel System Control Panel (the fuel switches are right next to it)

Yeah, this has been reported somewhere already. Its on the list, cheers

Hey there, this is a known issue. It can safely be ignored for now. Fortunately, modern browsers are resilient enough these days.

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