Zabuzard

No. And that wouldnt help in this case as the bug is within Jesters logic. Like, if such an action would be available that action wouldnt work either. Player made alignment should work. There are a lot of pitfalls with it though, so I suspect one of the many possible user errors that can be made here. Your video for example does not show the Navigation Computer panel. If you suspect that there might be a bug or need help, please share a track file with us and we can identify the issue

Could you provide a screenshot of your DCS Graphics Options? There are some options that can cause really weird stuff.

No update

Its in the backlog. So yes, it will eventually be done.

Mostly due to time. That said, unlike the Tomcat the WSO in the Phantom has a fully functional stick and throttle. And we exposed the autopilot control binds to the WSO for the time being. So you can for example engage Altitude Hold or similar.

Yes, just hop in the back and do the alignment yourself, then hop back to the front.

The fix is currently in testing and then waiting for a hotfix opportunity. Otherwise its distributed as Jester Mod. Please standby for more, cheers.

The neutral position of the stick in the Phantom is automatically moved around by the aircraft depending on G-force, airspeed (and indirectly also through trim). This setting affects the time period over which these changes are applied to your stick. So for example when you pull hard on your stick you will have a sudden G-spike, causing the bobweights to increase their weight and as consequence push your stick hard forward to counter (and vice versa with the bellows when you increase airspeed). The setting smooths out this counterforce over the time period you configure. So instead of being instant, the forces applied by the plane on your stick are smoothed out over a time period which you can select. This makes it easier for you to react to it and is mostly meant for people without FFB stick. Especially for the people who had trouble with the trim system, as this will as consequence also smooth out the trimming. With a FFB stick your hands should be able to hold the stick neutral at the position you want, regardless of the plane creating dynamic forces pushing the stick around in your hand - as your hands naturally counteract the dynamic forces as you hold the stick in place (provided the forces arent too big). Without FFB that is not really possible and players always have to counteract by giving explicit input. So this setting makes that easier to handle.

The team found the issue and fixed it internally It can hopefully soon be distributed via hot-fix. Otherwise the team might also distribute it temporarily as jester-mod (in this case you would just have to drag/drop a single file into your saved games folder - easy). Jester modding came at the right moment, lol

Yeah, multiple people reported such an issue. The team is investigating, sorry for the inconvenience. In the meantime, it seems if u hop back and align yourself, Jester will eventually roll with it and get his brain unstuck.

Yes. This aspect in particular has been carefully fine-tuned to match all available (very detailed) technical data and our SMEs all confirm that it felt exactly like that.

I suspect you did not actually finish the refueling but misinterpreted the events. There is a DCS "bug" with the tanker where when you disconnect due to maneuvering and then dont cycle the door quick enough while the tanker connects again, he will incorrectly state "refueling complete" instead of waiting for the door to be cycled first. When that happens you have to reengage the dialog with the tanker and continue with the refueling (ofc after cycling the door).

In case you run into an issue with us automatic deployment. There have for example been cases where it extends and retracts constantly, causing unstable flight. Mostly due to malfunction but there are also situations where u might anticipate it to trigger in/out and then you could use that switch to force it in one position. For example to prepare for a landing where you really don't need this thing to act up.

No worries. You are not the first to trip over this acronym. Also reminds me of doing that one feature I had in mind where you mousehover over abbreviations like that and it shows the full name, perhaps including with a link to where it is explained in more detail

There is an edit button in the top right corner ARR is correct, it stands for Air Refueling Release button, see here for more: https://f4.manuals.heatblur.se/cockpit/pilot/stick_seat.html#air-refueling-release-button Ill link it in the manual in that article to avoid confusion

Something like that is planned. Its not that trivial though. From a UX perspective it is better to approach this stuff from the use cases and less from a "let me control the switches in the backpit". Some things, like the AAR and landing stuff should be fully automatic by Jester, you should not have to tell him to switch radar off or anything - so the solution for that will consist of improving the automatic behavior. Other than that there will be situations in which you want to shutdown all emitting equipment, i.e. a "go silent" option that does not only turn the radar off but also jammer and similar. The existing option in the wheel just switches the knob, there is no persistence applied to Jester that lets him remember your choice - so he will switch the radar on again whenever his logic decides its time to turn it on again. Making your choice permanent isnt ideal either. 10 minutes later you are jumped by a Mig and complain that Jester isnt smart enough to figure out that its time to put the radar on again without you explicitly telling him. This stuff needs to be approached in a proper and more modern way that resembles the real cockpit interaction between pilot and WSO better than you trying to control both pits at the same time

Its on the list, cheers

This is WIP. It is because currently this is the best way for him to understand that you are doing AAR. The condition should be refined so it wraps the process better, but its important that its specific enough to not trigger when you are for example just escorting a tanker or waiting for your buddies to be refueled. Not that simple, so the AAR door has been picked as intermediate condition for the time being.

This is mostly due to technical limitations. Thirdparties dont have much control over how the cursor works or looks. The way the explain feature works is by setting a flag in the code (while holding down M) and if that flag is set the code will intercept any input/bind that DCS feeds it with, ignore its normal function and instead open the manual at a dedicated page. So its technically not only "click at something", the code cant differentiate that from someone pressing a HOTAS command or any other bind. The linkage from command/bind to manual is setup in a file called explain_table.csv, you can find it in DCS/Mods/aircraft/F-4E/Input. Your suggestions are welcome and make sense. But I doubt they can be implemented currently. Cheers

The team has repeatedly confirmed the bug and that it happened during test sessions already as well, that is not the problem. For finding the cause and fixing it its necessary for it to be reproducible in debug mode with the debugger attached. Not just once or twice but like 50 times in a row. Hence the need for a tracl that reproduces the issue when replaying the track :)

For clarification, CAGE mode is left by entering or leaving the B position - not by staying in it, its the impulse that triggers it. If you did that you probably did leave CAGE mode, unless you have accidentally entered it again. Possibly due to a bind conflict, Ive seen that a couple of times already. Otherwise, I would suggest you press Context Action twice and pay attention to what Jester says. You can also deactivate AUTOFOCUS in the Jester Wheel (Radar) to rule that out as factor. Hard to guess whats going on. A track would tell instantly if you can share one.

Are you talking about the kneeboard or where are you missing the QFE exactly? If former: Known issue, fixed internally already :)

Its as mentioned earlier in the thread. Some of them are supposed to be adjustable and as such the team will make them adjustable eventually. The difficulty is not adding the interaction and tilting the mirror. Its teaching DCS that the "camera view" inside the mirror has to change as well. See the little gif I shared earlier which has the interaction but the actual "picture" shown by the mirrors remains the same - not helpful. Someone from the team has to sit down, figure it out and make it happen. It's probably rather low on the prio list. But it will be done eventually.

You would start with them being set so you can see your control surfaces. Especially for the checks on ground. And then you might adjust them as needed later on.

When you replay the track in DCS (main menu > replay), does it reproduce the issue as well? The main problem with this issue is that so far no one was able to nail it on a track that reproduces it yet, unfortunately. Its a known bug and the team already did some blind investigations and attempts to fix it, but without a working track it probably will remain very hard to find and fix.