Zabuzard

Numpad doesnt seem to work for engine limitation reasons, unfortunately. Virtual keyboard and assignable keys are planned, cheers.

Its on the list. Cant tell you when it will be done though.

Seems this was fixed already by now, wasnt it?

This is a DCS engine bug caused by an unfortunate combination of settings. To fix it, go to your VR settings and select "Use DCS System Resolution". Then go to your graphics settings and pick as resolution something like 1920x1080 (not lower). Restart DCS. It should hopefully work now

Okay, thanks. I played it on debug mode. Possibly that change said method call order during initialization. If that's the case, the next update will hopefully contain my fix :) Lets check again with the update.

The sight can not be depressed in all modes. For example when your delivery knob is in TGT FIND, the reticle will be caged to the RBL regardless of HUD Mode setting. When you run into the situation, please send a screenshot of the entire front panel. It is probably easy to tell for us then why it is not "working". For reference:

For this sort of navigation you do not need Jester. Get the TACAN command by clicking the button on the right console so that the lamp lights up green - you are now in charge of the TACAN. Set up the TACAN channel (67X) on the right console and turn the system on (T/R): Then, select the TACAN as navigation input for your nav devices by moving the knobs on your main panel to TAC: The HSI now displays the bearing and range to the selected TACAN station. You are now ready to use it for the desired navigation. RAD/DME stands for Radial / Distance Measuring Equipment, which essentially refers to this type of navigation that is based on distance and bearing to a selected point. 065 is the radial, i.e. a straight line that goes out of the TACAN station at 65° and 5.5 is the distance to the TACAN station. For "fly outbound TCN 067X on RAD/DME 065/5.5" you would fly from the TACAN station into direction 65° for 5.5 miles as indicated by your HSI. The arrow would point with its tail to 65° and its head to 295° (360 - 65). Then you simply follow that course until the MILES window says 5.5. For "at DME 5.5, fly heading 108 and intercept RAD/DME 089/13.5" they want you to change your course so that the tail of the arrow points to 89° (head to 271°) as soon as you reached the 5.5 miles mark and then fly that until you are at a distance of 13.5 miles to the TACAN station. Essentially, the instructions are not telling you a course for your own aircraft but where to place the TACAN station in relation to your position. There are also a few videos showing how to intercept TACAN radials and similar: The concept is pretty much aircraft agnostic. So you can look for tutorials on other aircraft, sims or IRL as well and translate it pretty much 1:1 to the Phantom

Might be worth mentioning that the Phantom computer also helps you out a bit already using the ARI. (Which can be disabled by pulling the CB on the pilots left sub panel)

This is done on purpose as free mousewheel interaction is usually considered sluggish. From our experience, most users prefer single click on something that wants you to set a channel over rotating the mouse wheel or dragging the mouse until the counter finally reaches the desired number. Also allows clicking it clickly for example 4 times to jump from channel 1 to 5. The kind of interaction you are asking for makes more sense for variable knobs like a Volume setting or the brightness of the formation lights. If there is a way to offer both at the same time, we can try to do that. Otherwise it is probably better to keep the current interaction, I suppose.

Yeah. It seems that increasing the timer improves the experience. Ive now changed it to 0.1s instead of 0.01s

Which exact keybind are you using? The "Full Action (button)"? That bind is an artificial bind that will execute the full sequence programmatically. So it will go RELEASE -> HALF ACTION -> FULL ACTION and when you release it, it goes HALF ACTION -> RELEASE. So it mimicks the full travel of the actions. They are executed with a delay of 0.01 seconds each. If it only works sometimes for you, perhaps that timer has to be increased? Hard to say

In TGT FIND (and OFFSET, which TGT FIND is technically a variation of), the sight is caged at the RBL. For reference, TO 1F-4E-34-1-1 p. 1-27 This also makes it easier to use the reticle for attacking targets using the 12-VIS ACQ mode of the Pave Spike and allows reading the steering cues given by the roll tabs in all situations.

You are sending the wrong action. Jester says "Focusing on your guy", not "Locking". This corresponds to Jester Context Action SHORT instead of LONG. You must hold the context action command for at least 350ms so it triggers the LONG action instead of the SHORT. Here is an overview of the actions: https://f4.manuals.heatblur.se/jester/combat/overview.html

When I replay your track, everything seems to work as it should. Everything is warmed up: Can someone else try to replay the track to see if its only working on my end? Thanks. It is possible that the code has undefined behavior here, as the implementation makes an assumption about call-order during the initialization process that I assumed to be safe. But if it is not working for you and possibly others, it might be that the assumption was unsafe, resulting in code that only works sometimes. If what I assume is the case, I've just pushed a fix for it

Make sure you are not running into this: * Navigation: Fixed INS aligning to a wrong heading with the nav comp off- now only gyros are heat-up but the gyros erection does not happen until proper Nav Comp signal is provided Procedure details are listed in: * https://f4.manuals.heatblur.se/systems/nav_com/ins.html#alignment-options * https://f4.manuals.heatblur.se/procedures/pre_start.html#ins-stored-heading-alignment-wso

Could you elaborate a bit? What do you mean you ejected all four? Where they still visible on your pylons after firing? (If so, make sure you do not have unlimited ammo ticked in the mission or ur own settings). Is this something you can reproduce and possibly send a small (and working) track file?

The current (german) seats in the aircraft would be armed by removing safety pins when the crew gets into the jet (not modelled currently). From there, the Phantom automatically arms/safes the seats by the state of the canopy. Closed canopy = seat armed

Sounds odd, i can doublecheck on Monday. If you can send me a mission or track that would be helpful in case I cant reproduce it myself for whatever reason. Cheers

UHF should be there already afaik. Radar Altimeter is missing but planned. It requires some conversion on the backend first, as it is currently not compatible with our new bind system.

They are planned and likely to come rather sooner than later. At the moment there arent many. However, a lot of functionality is available through direct commands in the Jester Wheel already and these player-available binds (Jester Command: ...), like any other binds, can also be "pushed" from within the Mission Editor. They are virtual push buttons, so you would have to send a 1 (press) and then 0 (release) to activate them. That is also how most of our training missions are currently set up to control Jester. The full list of those commands can be found in DCS/Mods/aircraft/F-4E/Cockpit/command_defs.lua.

Thank you. Afaik it was fixed today for the upcoming patch. Ill ask tomorrow and possibly send the fixed mission here.

A few things to mention after watching the track: * Let the aircraft walk the pipper into the target, dont hold it there with the stick * Wait a second after hearing the beep before you start your maneuver * You probably have to dive a bit steeper before you level, so that you level out before intersecting the radar centerline from the picture you shared * When releasing at level and expecting pinpoint accuracy (hitting a ship without ripple), it is crucial that you fly your parameters even closer. Your pitch was rather 1-2°, airspeed and altitude were slightly off as well - should only cause the drag coeff to differ by 0.01 in this case though... That said, unless it was the intersection issue mentioned earlier, the track looks a bit sus indeed. I am forwarding it for investigation, thank you! Also, very good track quality

Thank you, fixed for the upcoming update. Cheers

Thank you, this is a known issue. Also see here:

Ive put it on the list for the team to investigate and callback, cheers