Zabuzard

Yes, thats a good suggestion. Unfortunately, not as low hanging as it may sound, mostly due to the jet not having an easy way of understanding what kind of weapon you got. Its absolutely solvable, but would probably take quite some time to develop "just to save u one click selecting the weapon" and then likely still fail you in practice because you may be running a mixed loadout or not having selected the delivery type yet because you are still on the ground. IRL the "Bombing Tool" math is always done before even entering the cockpit. Its preplanned, you write down your solutions and then enter them midflight. That was also kinda the idea we originally had with the tool, hence the button to "save a profile". You are not really supposed to click through this UI midflight, seconds before attacking the target.

You might have missed a step as it did work for "everyone else" so far and also in the past years, as this issue keeps popping up very couple of months for some module in DCS. Id suspect you forgot to run DCS repair to get back the file that your Antivirus deleted :)

Jester cant guess the release altitude and speed you would want to use for your attack. This is a crucial piece for the drag coefficient, it is not static based on the weapon. What I could think of is telling Jester in advance, perhaps even on ground, that you plan on using this profile for this attack and that profile for that attack and then "attach" that to a waypoint as part of your flightplan. Then Jester could enter this preplanned data automatically when you approach the attack point as part of your flightplan.

They did not have any stabilization, nope. Thats how it was IRL [emoji106]

Yeah. Id wish there would be anything that can be done from our side to get rid of it. This will keep on happening for our modules occasionally and also for other thirdparty modules. Most of the time the AVs trigger on stuff that is more complex on the technical side. Which is why it doesnt happen that often on (coding-wise) simpler modules. For example the use of Jester, the UI, the recorders, having Special Options, the component system,... all those feature require doing things that can be AV sensitive like reading/writing files on your disk, spawning processes or talking to the internet. We (and ED) do send our files to the AV distributors for whitelisting but the process usually finishes only like 2-3 weeks after release of the update. Which is also why these problems tend to "resolve magically" after waiting long enough and why it rarely happens for modules that don't receive many updates anymore.

The main reason this is a rather uncommon sight for most games is because they delay all their updates by 2-4 weeks in order to whitelist the files explicitly at all AV software distributors. In case of bigger AAA studios they also pay them for premium and in order to speed this process up a bit. With the files being explicitly whitelisted in the AV DBs, they can then safely be distributed to users. This process often needs to be repeated whenever the file has been changed, i.e. on every single update. During development, also in those AAA studios, the AV triggers for the files as well, its standard practice to just locally whitelist the folders (you also gain some performance boost of that). For some Indie games its actually not too uncommon to run into the same problem as user.

You may have forgotten to run the DCS (slow)-repair feature afterwards to restore the files defender deleted :)

Your antivirus software is detecting false positives and deleting files. Before you continue you have to first teach your antivirus to stop messing with the DCS files. You need to add the files (or the entire DCS folder) to the antivirus exclusion/whitelist rules (not the firewall). Once your antivirus stops deleting files you can run a DCS repair to get back the lost files. Cheers

Ah, you are using the CTRL+1..8 binds. You can control the outer wheel (and also the inner wheel) using the CW/CCW binds (QWE by default). Cheers

Not sure I follow what your describing. What are the "last choices"? Which keyboard commands are you using? The wheel is fully keyboard compatible, mouse is not needed (only exception is the text entry currently).

This happens because your Antivirus program decided to delete one of the F-14 files (most likely a DLL because it thought its a virus). This stuff keeps on happening randomly to many modules whenever either DCS or the Antivirus providers ship an update. You can fix the issue by adding the DCS folder (or just the corresponding file) to the Antivirus whitelist and then running a DCS repair to get the lost file back.

The track has Jester working on my end: So whatever it is, it must be a local issue. Most likely your binds interfering with Jester and fighting his controls in some way. Can you check whether Jester worked at all for you? Like, did he respond when you select something in the Jester Wheel, does he do anything or is he completely gone? If latter, maybe he crashed (then there is a crashlog file in the SavedGames/DCS_F4E/Jester folder). Or you deactivated him accidentally somehow? (But that should also reflect in the track). I am a bit surprised that the track has Jester not moving the cursor when you replay the track in DCS yourself, as that should disable all your inputs and only listen for what the track says (which works on my end). Like, the experience replaying the track should be the same for both of us and only when you actually fly yourself I would expect Jester maybe to fight with your inputs.

Also when you now replay the track on your end? Thanks, ill check the track and see what commands ur sending and what Jester is attempting.

Can you send a track file? Your the first to report this for whom it didnt got fixed by checking the binds

This is a typical symptom of a bind clash. Where your bind fights with Jester trying to move the stick elsewhere while yours sends towards DCS "move it to 0 (center)". Try to remove your binds to the Antenna Control Stick - especially any axis binds. See if it works again then. If it works, then make sure you add a modifier to the bind so it is not actively sending inputs to DCS while inactive :)

Would you be willing to share a track of a landing attempt? We (and the community) can then have a look and identify what went wrong, trying to give tips

Yes, it is known. No ETA. The bug lies somewhere on the LUA side in the files that define the binds. (So it is something the community could fix until we get around to it.)

Eventually, sure

Those are iirc default ED animations. Yeah, needs to be deactivated and replaced by custom made effects.

Unfortuantely, the Tomcats Jester Menu (including the text) is written in C++, not Lua. There is no way for you to mod this for localization purposes. This could possibly change when/if we port the UI over to what the Phantom uses, which is accessible to modders. Cheers

Back online

Not sure why you are so negative. This is exactly the reason why people would not want to interact and rather prefer to stay in private channels. My advice is to think this attitude through to ensure your actions actually lead to the goal you pursue - which I am going to assume is having a nicer experience with the Tomcat.

During the work for the -A we made the Tomcat compatible with our component system. It could be reasonable to add a few wear/tear properties here and there. But ultimately it would probably be way too expensive to be reasonable to execute on a big scale. Like, we are talking about multiple months, possibly years, of pure porting-work just to get the Tomcat to the "Phantom Standard". But yes, having such stuff in mind for anything new, such as the -A or -B(U) is generally a reasonable thought.

Rail weights are modelled but included in the default aircraft weight. While the "no pylon"-selection in the loadout menu has negative weight to subtract it again. For multiple reasons this is the preferred way of doing it. Overstressing the aircraft has consequences in multiple ways, not all of them are easy to notice or directly visible. But ultimately for a super granular, dynamic and aircraft spanning feature you need the component system with wear/tear simulation that our Phantom and future modules have - probably too late for the Tomcat.

Aye, the site is temporary down since yesterday. Cheers