Zabuzard

The manual is just a manual. The real world fuel numbers are slightly different. An empty tank also isnt fully empty, it still has some fuel in it, the valves dont sit at the very very bottom of the tank. Further, the actual amount that fits into ur tank depends on the pressurization as well. Note that the indication is in lb (weight) and not something like gallons or liters. So this depends on density and so on (which is fully modelled). Also worth noting that this stuff is subject to aircraft condition (slider in the ME) as well.

Just FYI. This has been fixed for the Viggen already last year and for the Tomcat recently (upcoming update) Fixed already, upcoming update. This in my opinion is not fair. No other module than the F4 features a mouse-clickable UI and the F4 only has it because the team spend six figures in extra development effort to make it happen, developing a completely new technology. It is very complex on the technical side. As for the other comments, the reason you are seeing these nice QoL things in the F4 is because its development benefited from the lessons learned with the Tomcat. You will generally have this with all modules in DCS, especially also the art quality and how it interacts with the DCS engine. That said, in case you have not seen it already: It is planned to port this technology over to the Tomcat (and Viggen), so they can benefit from it as well. Debatable. You can always delete the voice files u dont like, then they wont appear anymore. A setting for a more serious Jester is on the list and has been confirmed already, so it will be done eventually.

Yup. He will run with what you set him up with though. Like, you should still know the interface in your and his cockpit so when he presses the dispense switch it releases what you think is meaningful. Especially in terms of "program", as that is fully configured in the pilots cockpit :)

The CMS settings are split between both cockpits, always on the left console aft though. The WSO sets the master mode for chaff and flare individually to either: OFF, SINGLE or PROGRAM. If set to PROGRAM, they will do what the pilot has set up on the program settings on his panel. Both have a dispense button that dispenses whatever the WSO has selected as master modes. Additionally the pilot has a FLARE override switch that allows him to activate flares even if the WSO disabled them. Details in the manual. That's all there is to it :)

Its a bit hard to judge how much ur going up/down without some form of video or track. Make sure you have the "Use FFB" option deselected in the DCS settings in case you are not using FFB, that can cause issues like that. Similar extreme issues if you froze up your bellows intake or received combat damage on a area belonging to the system (for example around the rudder area). Other than that its important to note that due to the bellows/bobweight system the Phantom constantly pitches up or down whenever speed or G-load change. Hands off it will oscillate up and down, more or less holding the altitude over a longer distance. It is some form of mechanical "autopilot".

We have seen this issue in the past with people who had some specific mods (cant recall which though). So yeah, I would try to exclude mods and run a repair as well.

(note that these weapons are defined on EDs side, not ours. cheers)

Mind elaborating, which issues?

I understand and you are being heard. It will eventually be tackled, I cannot tell you when though.

The team is working on DCS EF and DCS A6. But as explained that at the same time means doing progress for any other platform as its the very same code. Whether the remaining MSFS 20% will be coded for these aircraft hasnt been confirmed yet. But is ofc generally a reasonable assumption - provided everything goes well with the MSFS F4 business-wise, I guess.

There is no problem. But it requires someone to sit down, context switch, spend time on the topic and do it. Something that has not happened yet. But I wanted to let you know that you are being heard, like any other post on the forum or Discord. Even if there was no explicit response, it was read and "put on the list".

Hey there, all messages are read by the team and bugs are put on the backlog. It will eventually be fixed.

Thanks for the track, the team will have a look [emoji106]

FYI the MSFS F4 will be identical to the DCS F4. It is not a "new aircraft" and it will not use the MSFS built-in FM, unlike the MSFS Tomcat. It shares 90% of its code with the DCS F4. We have done that starting with the F4. Our modules are developed cross-platform. So there is no porting in that sense. 80% of the code works on both platforms and then you "just" have to add the remaining platform-specific code on top to wrap it up.

It looks to me like ur releasing trigger? IIRC u need to keep holding trigger (hold the lock) and bomb button (release). If I take control of ur track and do that it releases and hits the target.

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