Zabuzard

By the way, the manual is open source. It would be cool if someone puts all the neat stuff into the official manual so every user can benefit from it. You dont have to wait for a HB employee to do it. The manual is for all of us :)

Sounds odd. People report daily on our Discord server that stuff works fine and it also works when we fly with our testers. Smells like you guys might be missing a step. If tutorials and manuals dont help, perhaps you can share a video. Or at least some details what exactly you are doing. Cheers

They already do spawn with the ladder out - either the yellow external ladder or the onboard steps, which is randomized. It is theoretically possible for a mission maker to force the ladder by playing the animations manually. Like, setting the animation for the external ladder to 1 (and the anim for the onboard steps to 0). As soon as the pilot then clicks on "put helmet on", these "cold items" (e.g. also the red RBF flags and covers) get removed automatically by the code. I dont exactly recall how you can play animations via mission editor, but its possible. They are not per device like commands, just a global animation ID. You can find them by opening the model in DCS ModelViewer and/or by opening our draw_args.lua file.

What you are experiencing is a known "bug" with the tanker where it wont understand that it must not plug the boom in before you have reset the refueling system (flip flop refueling door switch) after a maneuver disconnect. The tanker doesnt understand it, sticks the boom in regardless and then misunderstands our code telling it "yo, u shall not connect" as "ah cool, so refueling done, right? right?", incorrectly making that callout and then instantly disconnecting. Until it is fixed this means you also have to reactivate the comms-procedure with the tanker when it happens (intent to refuel, pre contact,...). But yeah, as far as the Phantom is concerned everything works as it should - after a maneuver disconnect the system must be reset manually with the switch before fuel can be received again, cheers.

The Radar Altimeter has been ported over to our component system by now and hence received proper binds internally. It will be available with the update after the upcoming. Cheers

This is simply because there are too many weapons available and EDs UI does not feature a scrollbar (yet). It is a known issue - we cannot do anything here, the UI is completely on ED. Cheers

We can look up the electric wiring logic to be sure. Your description of the ingame logic is correct.

As Dom explained, the wind thing is a DCS engine problem. Can you produce a short working track, then we can see if there is more we can fix from our side. Cheers

Wheel Chocks unfortunately don't prevent mini movements in those situations. DCS shenanigans

Yes, the engine is simulated accurately according to our available data and first-hand Phantom Pilot/WSO feedback. This includes compressor stalls and similar stuff.

Usually this is due to ur spawn point or something slightly moving you during the alignment - in which case the INS reacts correctly by taking veeery long. Do you happen to have a track at hand so we could verify what exactly happened? Cheers

You say this as if this is intended behavior. What you are reporting is new to us, sounds like a bug and we will investigate. Cheers. That said, there are some minor differences IRL between the two sticks. The backseat for example has no force transducer on the stick. The only technical problem currently know to us (which cant be fixed easily - but will be eventually) is that in Multicrew if flying from the back you will be flying "with lag". That is, the aircraft movement computed on the pilots computer, meaning your inputs first have to travel from your to their computer before they take effect (and the effect has to travel back to your computer again before you can react). Can you elaborate on what you two have set in your Special Options regarding Multicrew Flight Control behavior and whether you pressed the "take control" bind? What was your and your friends ping roughly? Below 100ms?

Here are details on the CL Lamp behavior: https://f4.manuals.heatblur.se/systems/weapon_systems/multiple_weapons_system.html#centerline-tank-aboard-light

You can use this forums search function or the bug section in our Discord. Those combined pretty much sum up all known issues. It is planned to make our internal bugtracker somewhat accessible to the public but no idea how long that might still take. That said, its no problem for us to just tell you "thanks, known" whenever something gets "reposted". No worries :)

Nope, you get the option in the debriefing window.

Do you happen to have a track available? Or perhaps also a recording?

Aye, this is a known bug. Cheers

Please dont crosspost. See my answer on the other thread, cheers.

We are asking them to whitelist it. And it does work, it takes a few weeks. It is just that as soon as the file slightly changes with the next DCS update that these Antivirus softwares will flag them again, as the changed file is not whitelisted already. So the whitelisting process has to be repeated (which we and ED do with each update). This is normal. AAA studios suffer from this as well - normally these companies pay for business accounts at MS, Kaspersky and Co to speed up the process and they typically also delay their planned updates until the files have been confirmed to be whitelisted before sending them to users. Since this part isnt done for DCS (for a few reasons) you experience this problem as end user. If you do believe ED or us are shipping actual viruses then I do not think there is much we can do to convince you from the opposite. Then you either have to stop playing DCS at all if you do not trust the publisher or at least have to stay on an old version and wait with updates for ~4 weeks to be sure the whitelisting for those files specifically has been done already.

Lesson: Probably not JWheel: The automatic placement depends on your DCS resolution setting. Since you are running a custom multimonitor setup, I suspect you also setup a resolution spanning across multiple screens. In this case you can override the UI placement from the Special Options menu. There are options to override the resolution for the UI and also offset it in X or Y direction to get it where you want. Details in the manual: https://f4.manuals.heatblur.se/dcs/special_options.html#hb-ui

Yes, it doesnt influence your vision yet :)

The kneeboard has tables. Also, you can create yourself tables by using the Bombing Tool (RCTRL+B) - select DIRECT :)

Its a known bug that unfortunately isnt that simple to fix. Has to do with how DCS rendering engine works.

What kind of AntiVir program are you using? Dont forget to add the exclusions for Windows Defender. Looks sth like this (Windows 10): Also, after you are done with the exclusions you need to run a DCS Repair to get the deleted file back.

Looks like a crash happening in EDs code. I do not see anything coming from us in your stacktrace: Might be a non-Phantom specific issue.