Zabuzard

The issue had been semi-fixed a week ago or so, for the next update. There is more to fix unfortunately, but it should be usable again soon.

From all the cases ive investigated so far it always turned out to be users confusing the interface and Jesters feedback. So it would be great if you can share a track, then we can tell you immediately what might have gone wrong or clear any misconception. Cheers :)

The gauges are modelled very closely to the manufacturer specification documents, maint docs and test results. The behavior was also carefully verufied by our real world Phantom pilots (inactive but also some who still fly the Phantom today). This btw also includes their variance and how they react to forces. Speaking of, make sure you select the "reference aircraft" in the mission editor for a good base of discussion. Otherwise you might experience whatever the mission maker had set up for you.

Everything marked in the manual as "todo" will eventually come :) Combat Tree is quite cool, but the very limited IFF-environment in DCS makes it challenging to implement it. (Currently you cant query any IFF info from other planes, such as if their transponder is turned on/off or what code etc.) What we have in mind is implementing it similar to friendly-IFF, that is it will show you any hostile aircraft (based on faction) on your screen, just like it was IRL. And then provide mission editors with options to either turn it off completely or a historic mode where it only works on certain planes that were equipped with the specific russian IFF transponders that the US were able to crack.

Now im getting confused a bit. The movements of the visual stick in the cockpit are, on a technical level, completely decoupled from the simulated aircraft stick for the actual movement commands and from the FFB simulation for your hardware. If you need a proper indicator for what's going on with the real stick or ur FFB stick then open the controls indicator display, it shows both. Whenever talking about the stick in the Phantom its important to hint at the bellows vs bobweight system that automatically moves the stick in pitch based on airspeed and G-load. So if you for example just fly straight but increase airspeed, your stick will automatically pull aft through the bellows. For FFB users this is very noticable IRL.

It is less about it looking "not perfect" but straight out bugged. For example if you make it less dark in some conditions the DCS engine will literally not render the glass at all anymore and it becomes completely see-through. Its not easy to tweak it properly. But it will be done eventually, as gas been stated earlier. Cheers

The animation is decoupled in order to smooth it out. Otherwise IRL you could jank your stick forcefully from top to bottom back to top within a split second, even with FFB (since it's not the real force but only a fraction of it) and without smoothing the animation ingame would have to move faster than DCS can animate it, resulting in the stick visuals literally teleporting. That looks silly, so the anims are smoothed. Same with the character model movements, yes.

The firewall is not the problem here. The firewall deals with which process is allowed to talk to the internet. But the issue here is that the Antivirus-part of your Defender decided that the F-14 DLL is a threat and quarantined (deleted) the file. Tell your MS Defender to stop doing that (exclude the file or the folder from the virus scanning), then ensure you get back the deleted file (e.g. DCS repair) and then you should be good to go

Right. Not sure what to tell you, this is how the radar in the F-4E worked real life. But again, possibly there are some things you can do to increase your odds while still going head-on. So a track file would be great

We do this with every single update, we always contact all vendors and create whitelisting requests on each update - even before you get the update. But it takes them around 2-4 weeks to process these requests, so sometimes you run into this. Kindly read through the previous messages of this thread, this has been explained in detail at least 3 times already throughout the 8 pages. Cheers

Its mostly the radar. Try a bomber, from the side (not headon!), over water and put urself below it. You will notice that you can spot it from like 50-100 nm now. Theres a lot of factors reducing your odds and especially a fighter aircraft approached head-on will have a very small RCS. If you then add clutter and bad positioning into the mix you will not find them early enough. Practice is key! If you need help, please send a track and we can have a look

That is correct.

You have to ask ED, we cannot communicate their plans for future updates.

Could you send a track. Then we (or the community) can have a look and tell you what to change to improve the experience [emoji106]

Its up in the air. This isnt a secret we are somehow trying to hide from you. The module is so far in the future that there was no reason to decide and commit on this yet. Sometimes things just are that simple

Both was done IRL. It was mostly crew preference. The main issue is that, lacking stabilization, the WSO gets thrown off when the pilot suddenly moves the aircraft around. Its easier for the pilot to know when to not touch the Maverick stick because they want to execute a maneuver than the other way around. But therefore it is of course easier for the WSO to focus on picking targets while the pilot focuses on flying. Ill bring it up with the team and the SMEs for clarification. I vaguely remember a discussion though that sth like this was for DMAS or later only. Will see, cheers.

1. no 2. yes 3. yes dont forget to enter ur attack profile in the bombing tool previously and hit "tell jester"

I understand your frustration. But please understand that there is nothing we can do on our side to "fix" this problem. If you want to fly the aircraft, you either have to go through this or you have to wait until the Antivirus software distributors updated their databases to not flag this false-positive anymore. This process usually takes about 2-4 weeks and often has to be repeated after each DCS update again. This is not a new issue, multiple modules in DCS are suffering from this problem for multiple years already. Please understand that this is not a "we are too lazy to fix it on our side" issue. Our hands are tied on this. The AV distributors decided to flag this file and the only thing that can be done to stop this is to send in the file to them via a whitelisting request (which we always do on every DCS update). This process takes multiple weeks and has to be repeated on every single update. If you decide to wait for it to get resolved globally by the AV software distributors, you will likely run into the issue again in the future. Perhaps in 3 months, perhaps on another module, perhaps on another DLL file. It keeps happening and there is no way to stop it.

The stick visuals are subject to animation smoothing to ensure it doesnt look silly when you jank around your stick IRL. Otherwise it would teleport and it would look really silly and break immersion. Its a compromise. Take note that this is visual only, your input is being registered and transferred to the FM instantly. The stick animations are decoupled from that (see the Controls Indicator UI). Afaik Cobra said some time ago that he might be tuning the animation again to find a slightly better compromise.

Kindly read through this and other similar threads in the Phantom subforum, as well as the Mirage and F-15 forum. It has been explained multiple times in detail, also already in this thread, why it is not really possible and why this is happening. Cheers

For the F-4E pre-DMAS? Not that I am aware.

As said earlier, we appreciate the input and have put it into the backlog for investigation :)

Active Pause bombing can easily lead your to incorrect results as you often drop with G in it, leading to wrong AoAs. If you run into an issue please send a track plus screenshot of what you entered into the tool, cheers.

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 :)