Zabuzard

He starts the warmup phase, not the actual alignment. This is the correct procedure.

Yes to all you said. With our condition/wear/tear system you have to get away from an on/off thinking. Your hydraulic system consists of like 100 components and all of them have properties that are influenced up and down. There is no "now the system works, now it doesn't". The result is a highly dynamic composition of everything together. I would also take battle damage aside as extra topic, as this can fail things as well. Sometimes as on/off, sometimes as 0-100%. It is extra, next to the other systems. Battle damage can also apply to all components in the entire aircraft based on their location. The failure list in the ME (and what random failures applies to) is a handcrafted list of manual failures that we put in "on top" of the condition/wear/tear and combat damage systems.

The random failure option covers the failures listed in the Mission Editor only. It is an ED system that we do not control. We can add new entries to the list of failures but thats it. The aircraft itself, with its condition/wear/tear system has way more "failures" than just those, although I wouldn't really call those failures. It also wouldn't be meaningful to add them all to this list, as its around 3000 individual things that all influence each other. And its not just on/off, but varying between ranges of values. The condition/wear/tear system isn't compatible with the ED failure system. Not only technically, but also UI-wise. It wouldnt be meaningful. Instead, you control that aspect with the condition/wear/tear sliders in your Mission Editor and with how you fly in-game. There will likely be more detailed options inthe future when we come to making it persistent for campaigns and similar.

Tracks dont work with the HB UI yet (unless all interactions are done only through keyboard commands). So a video would be needed here, unless you also give us a screenshot of what to enter into the bombing table for ur track to work while it replays :)

Im occasionally hearing similar stuff but no one got it on a proper working track yet sadly. We haven't been able to find the source after a few blind investigations.

thanks we are aware, it's on the list. cheers

Would it be possible for you to record a quick attempt. Doesn't have to be pretty but it would help a lot to rule out any procedure issues such as for example pressing bomb button not exactly on target or flying ias instead of tas etc.

I remember a similar report from some time ago and when the user send a track and we checked it revealed that the user didnt hold the button down but instead pressed it multiple times. Probably not intentional but rather hardware issue or sth.

Hello, this is a known DCS issue caused by an unfortunate combination of settings. Go to your VR settings and check "Use System Resolution", "BOTH EYES", then select as resolution one that is not lower than 1920x1080 and restart DCS. That should fix it. Otherwise you can mitigate by using the Special Options of the Phantom to either offset the UI or to reduce its size.

Yes, because we are smoothing the pilot animation in the Phantom heavily so it looks nice. In other modules, if you move your head around fast, it can look really silly at times.

This is actually a "bug" or rather oversight. Its not supposed to drop down all the way to 0% brightness. Thanks, fixed.

Yes, it is because animations are smoothed and interpolated in order to not look silly and choppy. By design this adds (small) lag. Its a compromise. Its not an issue with the mirrors, they just reveal what's going on with your virtual pilot model. We are aware of the issue, it's on the list. Cheers.

Thanks, known issue :)

Yeah, totally agreed. The entire lighting concept in this plane is weird if u ask me. Once the main instrument panel lighting is correctly linked to the knob it will look less confusing as what you are currently seeing with this knob is rather its secondary function and not the primary :)

This is correct behavior. Kindly see the manual for a detailed explanation, thank you.

Define a NAV FIX point as part of your flightplan and then overfly that point visually (see manual Jester/Navigation for details).

no

This is a choice the mission editor has to make. Check the "HDG MEM" option and you can fast-align. See the manual for details.

Yes, the entire aircraft is subject to these settings. For the INS specifically, there are around 40 components in and around the INS system that are affected by condition/wear/tear which will some way or another influence the system. We simulate INS drift in detail by actually moving the gyros around and such. There is no magic here, the drift happens the same way as it would happen IRL and all the small parts that play a role here can degrade in multiple ways, influencing the system highly dynamically.

Most AI weapon issues have been fixed for the upcoming patch.

As explained somewhere in this or similar threads, most of the times we actually get to see a track or video of someone experiencing this it turned out that their "short clicks" are not short at all. Not necessarily because people dont click short enough but also because some hardware has a too long minimal-impulse setup and hence sends the command longer than it was actually hold to DCS. I.e. your actual ingame experience might differ from other users and our intended design. In which cases it helped for some to adjust their stick hardware settings, if available. We acknowledged this unfortunately issue and are planning to add a way to mitigate the issue from our side as well.

Most of the times when getting this report it was either a procedure mistake or the hardware setup not actually reaching full deflection. Do you have a track at hand, then we can investigate. Cheers :)

Known, thanks. The TACAN system isnt compatible with our (new) bind-system yet and has to be ported first.

You need to be in the corresponding NAV modes for the knob to move anything. Bump it around and the knob should start to do something.

Kindly see the manual, thanks: https://f4.manuals.heatblur.se/dcs/mission_editor.html#flight-plan-preparation This happens when you try to start the game while some files got deleted/removed or modified. Most likely the cause of your AV program messing with the modules files. Add an exclusion and then run a repair to get the files back