Zabuzard

It appears that you are sending the SHORT (next target) action instead of the HOLD (lock) action to Jester: You must hold the context action button down for 350ms to trigger the HOLD action instead (see our manual for details). If I take control in your track and hold it down, Jester locks your bad guy!

You must have misunderstood me here. No one is invalidating anything, we are taking the feedback very serious and are always interested in improving our product so that everyone has an enjoyable time. I am just trying to understand the underlying problem better to develop the best solution for it. For example, if you say its visually distracting and blocking parts of the main panel, an alternative approach could be to make it more transparent or move it elsewhere or make it show/hide more dynamically instead of following the suggestion of "just remove the feature entirely".

Yes, thanks. This is due to some refactoring, lol. Thanks, will have a look. While odd, this is actually according to its specifications. It is indeed laggy and should only be interpreted when it stabilized itself.

You can "fix" it by using the Special Option to Offset the HB UI horizontally (X Offset) with a negative offset. This usually happens when the system guessed your resolution incorrectly, but can also happen when you are using "unusual" aspect ratios. Could you share a screenshot of your DCS graphics settings page (the first page)? I would like to see the monitor and resolution setup shown there, cheers!

Thanks for the track, will check it tomorrow and callback :)

MAP mode is correct. Could you hand in a quick and short SP track for the situation you are describing? That would be very helpful, thank you :)

It does matter to us, because knowing the reason helps in finding alternative, possibly better, solutions. It is helpful for us to understand the pain point and friction rather than only getting a proposal to change something. Your request of disabling all UI is probably easier to be accomplished through a mod (edit the files in the UI/JesterDialog folder), but then you have to memorize the response options by heart if you want to use it. Which will likely run you into issues in the soon future when we greatly expand on the dialogs and mission planning features. Regarding brevity, we tried to capture the spirit of how it has been back in the '70-'80, a time where people smoked in the cockpit, ate steak and where efficient and precise communication also among the crew was something that was still currently being worked on. It is understandable if you prefer a more modern approach to crew communication and your best bet for that, as of now, will likely be user mods. Ultimately, if you do not enjoy Jester in his current EA state, it might be preferable for you to wait a few months until a lot of these early-day issues have been fixed. Until then, you can also mute Jester through the UI, or perhaps prefer flying with a human WSO.

That is something we will fix. I am not sure why this is a problem for you. You can just ignore it. We can also reduce the time its there, but the menu was designed in a way that it is completely okay to just ignore the popup when you do not want to engage it at the moment. And user feedback so far was that this really isnt a problem for anyone. So I would be interested in hearing why it is annoying for you to "wait for it to disappear"

The files it likes to delete are in the Mod not CoreMods folder of the F4. Also, unless you have Windows Defender disabled, you have to tell it the same. You could probably also add the entire DCS path to it, if you feel like it. Hope that does the trick, cheers [emoji106]

Thanks. We asked our Phantom SMEs on this topic, specifically regarding the fuel gauge and all of them said that it was impossible to see the fuel gauge and it was common practice to ask the pilot during flight regarding fuel state, especially during combat. Which lead to us adding this sort of interaction to Jester. And yes, it needs fine tuning to not trigger in odd moments. The "refuel speed" is actually higher than for those other aircraft. That is, for the internal tanks (about 1-2min). If you want to top off everything, including the ext tanks, it can take up to 5-7min from empty. The upcoming patch also has a bugfix on this topic.

Can you share some screenshots of what you have set and where? In terms of AV exclusion. Perhaps you have missed something on that front. So far it seemed to have worked for everyone. You can also reach out to us on our Discord if you prefer a faster interaction. But we need to see some details in order to provide more hands on help [emoji106]

It is unrealistic to have that much possibility to lean and move your head around IRL. Usually you would be strapped in extremely tight. So we have made the decision to not allow Jester to access this value. Do you remember if he was saying that after ejection happened or just after he announced his ejection but was still in the aircraft?

Most of the things you are mentioning are bugs that have been fixed for the upcoming patch already, for example ejection. He is supposed to only eject milliseconds before impact. When he ejects in another situation, it is simply a bug. Regarding the fuel, he can't see the fuel totalizer, so he guesstimates the state based on time and how you fly and then asks the question occasionally. Especially during combat when having a dogfight with afterburner, this was something a real WSO would have done very often and the pilot would then have aborted the fight if fuel was low. Jester asking the question in a moment where it's not applicable is a bug. Report it and we fix it, that's the nature of development. That said thanks for the feedback, it is on our list and some of the items have been fixed already or are currently being worked on [emoji106]

Right, that is your AV program detecting a false positive. The file is clean, it is not infected. As hinted earlier in this thread, put your DCS path as exclusion to your AV program and then run a DCS repair, it should work again then. If you need help with that process, please share some screenshots and similar. Cheers

Could you elaborate? I feel like you are misinterpreting what is happening. Unless you caught a virus from elsewhere, there is no malware whatsoever in your DCS files. Possibly you also did not set the exclusion rules correctly, in which case it would be helpful if you can share some screenshots or similar of what you have configured. Cheers

It could also be that Jester is currently on the TV page because of a bug (fixed in the upcoming patch) when moving the knob to DT through TGT FIND. Theres lots of possibilities and some extra material like screenshots, video, track, list of steps to reproduce, would likely expose the issue immediately

Could you share a precise list of steps, a video or a quick track file? A screenshot of the WSO pit could also solve the mystery. That would be super helpful, thanks! When you are saying you change AA or AG, are you talking about the HUD Mode? Jester operates based on the Delivery Selector.

I mean, there isn't really any need to defend a mod. It is there for whoever wants to use it and these people will appreciate it a lot, so thanks for making it! :) In terms for addressing the issue outside of mods, the best approach would probably be if ED adds a checkbox or similiar next to the livery selection that would allow users to toggle country lock on and off.

Well, the knob, if clicked, would release any stores on pylons marked by ground crew as nuclear store (using a special pin). Since you cant load nuclear weapons and there is no one putting in that special pin into any of the pylons, clicking the button simply doesnt do anything. Like, if you would jump into the real Phantom with a non-nuclear loadout, you could also click the button and it just wouldnt do anything. So thats why its clickable, its correct behavior. The problem with offering binds for stuff that doesnt do anything is that when we eventually come around to implement it, it would break backwards compatibility and you would have to reassign your binds. So we rather not offer such binds

There is no bind for it since it wouldnt do anything. Nuclear weapons are not planned, so you also cant jettison them. Hope that makes sense, cheers

Makes sense. Perhaps this is better suited as a request to ED to add some form of checkbox next to the livery selection that removes country locks? Then all modules could put in country lock on the livery and users can always access all liveries if desired regardless - without the need for module makers to decide or users to rely on mods. Best of both worlds, so to speak.

Yeah, I understand. Its always good to have options, people who want country locks can pick the mod and everyone is happy Shouldnt, as DCS works based on the livery IDs, not display names. I just checked in-game and it seems all liveries are already grouped by airforce and have the airforce name in there, for example "F-4E - ROKAF - ...". So I guess the issues rather arise from not everyone knowing who IAF, IIAF, IRIAF is etc?

That has been fixed for the upcoming patch already. It is a coincidence though, you probably tend to land when you are about to reach bingo fuel.

Cool mod, thanks for the efforts! Perhaps the underlying "issue" trying to address here is just that it may not be directly clear which livery belongs to which country just based on the names? If so, perhaps we can just add the country names to the Display Name of the liveries in the editor without adding actual country restrictions? Cheers

As pointed out, this is usually due to Windows Defender and similiar AV software detecting false positives. Some other aircraft in DCS are also affected. It started to happen on the recent Windows Update. ED, we and other thirdparties already contacted them for whitelisting. These things happen every couple of years unfortunately