Zabuzard

Is that all the time or just sometimes? If latter, possibly you froze your bellows intake? What does your ingame control-indicator say when it happens? Do you have a track file, fast would help a lot :)

Are you on the latest version? There was a sign bug on the dive angle. But if I recall it had been fixed in the latest patch. Could you redo the experiment with a dive angle of 0? Cheers

Manual stuff should be reflected in the track. Its just the UI (Jester Wheel, Bombing Table, ...) that isnt - because mouse movements are not captured.

Jester currently doesnt touch the altimeter.

Correct, but it does come after the INS alignment. Jesters order is correct according to IRL checklist. You may have a point though that this list can be continued before the alignment has finished. The team will have a quick chat with the F-4E SMEs and then adjust the logic if applicable. Cheers

Yeah, sounds reasonable. Also something that modders could add with Jester modding if HB isn't fast enough :D

No need to bump. It is in the backlog where it can't get forgotten and it will be delivered eventually [emoji108]

Did you use the bombing table in your flight? Replays don't capture what you did there, consequently nothing was entered into the WRCS panel during the replay. When you replay the track you need to press ESC when the tool opens and enter the same data again manually and press the button. Only that way your replay does the same as it did in the true flight :)

It is a limitation of how the Jester Wheel is currently coded. I.e. it is missing another page. UI aside, there is no limitation. The aircraft itself isnt able to store waypoints (besides one) anyways. Jester memorizes them and enters them as you fly around (leap-frogging) :)

That wont help you much as the update included many more changes than swapping out a few sound files. The entire code was changed and improved. So replacing sound files would not give you back the old behavior.

Thats the kind of micromanaging that we want to avoid. The plan is instead to add a superior and more general way of pointing Jester at targets. Think of a "Jester, look here" where you point in the sky or on the radar screen or on the rwr screen or similar. Further, Jester will learn to incorperate more data into his search behavior, for example AWACS calls, RWR, mission data and so on. So that he is able to find targets more proactively than now where he only performs a general search pattern. The majority of F4 WSOs hated 2-bar mode for various reasons and always used 1-bar instead, while controlling the elevation by themselves. In 2-bar Jesters logic doesnt really work well anymore, so such an option likely wont be offered soon. And again, its micromanagement that you, as Pilot, should not have to do. Jester will be improved so you can focus on doing your Pilot job instead.

It is because MS and friends processed the whitelisting requests. As explained throughout this and other threads, the problem is the Antivirus Software incorrectly detecting a virus in the DLL files and it takes them a few weeks to process the request to whitelist the files. If you have not made an explicit exclusion rule on your side this issue will likely get back to you in a future update that changed the DLLs again in a way that the AV software thinks its a virus again. And then it will eventually go away again as they processed the request.

There is no workaround for this bug. Wait until the needle on the gauge caught up and he stops.

The team and ED first have to design a proper solution. As explained, that file serves a good purpose. This will most certainly not be resolved in a "hotfix", no.

Yes. That cache file remembers the names of all sounds the F4 is supposed to contain. So if you add files with new names, due to that cache mechanism, they are ignored. If your new files replace the existing sound files, i.e. same name, they will get loaded again. I am talking about the new file DCS/Mods/aircraft/F-4E/Sounds/sdef.tar. If you look into the file, you can see it contains all names of the original sound files. DCS uses that file to speedup loading times. If you delete the file your loading times will be back to how it was before the update, but custom sounds (with new names) will be loaded again.

Yes, ED changed something in regards to sound files. There is now some form of cache file in the sound folder to accelerate loading times, but it prevents adding custom unknown sounds. We have contacted ED and are looking for a resolution. In the meantime you can either rename your custom sounds to the original names (they will then get loaded again) or temporarily delete that sound-cache file.

Your impression is incorrect then. Everything shown in the Bombing Table is mandatory to enter and follow. It is just that Dive Toss, for standard attack profiles and low drag bombs, generally is quite forgiving and often ends up close to the default values.

Not yet. But most other BITs are (for example HUD or Pave Spike).

It is technically possible to add one of the existing Anti-Ship-Missiles to the Viggen instead and make it compatible with the aircraft. This weapon would then obviously lack all the unique features of the Viggens missiles and just be, well, one of the existing ASMs and thats it. This option is currently not considered by the team and instead HB and ED pursue transferring the weapons to ED to address this issue.

It is a technical limitation of DCS and a consequence of the fact that the weapon is run by Heatblur code instead of ED code (unlike most other weapons in the game). The only way to get rid of this issue is by having ED implement the weapon fully on their side and Heatblur then switching over to EDs code instead. This is of course planned and will eventually be done.

Its field modifications done to prevent the buttons from falling out during a catapult launch.

It is a button only, it can be pressed. The secondary functions are not about "weapon selection" but rather "weapon related". While hold down it enables slewing for Mavericks and Sidewinders. See the manual for details: https://f4.manuals.heatblur.se/cockpit/pilot/stick_seat.html#air-refueling-release-button

Great! (also, first try - yay [emoji16])

No, these methods are in the DCS SDK, C++ sided.

For cold start, yes. As per proper checklist.