Nereid

This is again nonsense. A missing feature that should be in place is a bug. The feature was added. Keybindings are there but some were OVERLOOKED. Overlooked parts of a feature are bugs. [even incomplete or missing features are bugs by some definitions and such bugs are to be expected in beta/EA, but this is not the topic]

This is nonsense. If there is a keybinding missing then it IS a bug by EVERY definition.

Why do you think it was added already? It wasn't so it is a bug. Nice to hear. Thanks. I will give it a try as soon as possible.

This is called a request. A missing keybinding is a bug and not a request. Here's your dictionary https://dictionary.cambridge.org/dictionary/english/request So I'm the one who has to facepalm and I'm missing a few hands to do it. But thanks for your silly reply.

If mirrors are on I'm experiencing some flickering on the whole screen every then and now. But only if the mirrors are toggled on and only on the Sinai map. Version 2.8.6.41363, ST (I have noticed it in MT too) It is similar to the issue descibed in but it happens just while looking forward without moving the view and the the whole screen blacks out for just 1/10 of a second or less. (well in some cases it looks like there a black box just on most of the screen and expands shortly after; and it is clearly not a displayport blackout because of this and the short time) I have also tried the solutions described in but they do not fix the problem. This problem (aside from not being mirror related) seems to fit my problem better. Other modules (I have tested the F/A-18) are not affected on the Sinai map and there is no issue for F-14 on the Syria map. It may be a map issue that only shows in the F-14. But because only the F-14 is affected, I'm reporting it here. The Sinai map is quite new, so maybe no F-14 owner has experienced it so far.

Yes, but it is clearly a Tomcat related issue and it is back in 2.8.6.41363 for the Sinai map (at least for me).

There is no keybinding for the altimeter pressure knob in the pilot seat. Version: 2.8.41363, ST (single threaded version)

Is there no keybinding for the Altimeter Pressure Setting Knob on the pilot seat? Or am I simply overlooking it? If there is none, I would call this a bug.

The last time I flew the Mi-24, it was tougher to fly.

I have just tried the AH-64D again after a few weeks of absence from DCS and with the new update. And for me it seems easier to adapt than before the patch. Still not easy to fly, but that is to expect. It's a helicopter, so it shouldn't be easy. Without any practise for three weeks or more, I was quite surprised that I could takeoff and land this beast without too many issues. Takeoff and landing were far from perfect, but that was to expect too. There were some strange behaviours as I was trying to land on a flat roof of a building, but hey I was probably a little cocky even to try this.

Well. It's the other way around. There is an uncage button (called "cage button" but it uncages the instrument) but none for caging. Indeed. A toggle would be nice. But at least they should add a button for caging. But a toggle would spare a button. And some HOTAS systems have encoder dials with a push. So the encoder dial could adjust and the push could cage/uncage which makes it easier to memorize.

Yes. Something like this. But in the AH-64D it seems more hard to compensate for it as in other choppers as far as I remember (and to be clear: I did not mean the countering by applying left cyclic; I meant the sudden drift to the left when airborne). But this doesn't mean it is a bad thing and it should be changed. It just that I need a few attempts to get used to it everytime (!) I try to have some fun with the Apache. And as Admiki said: We are not feeling it in a sim, so we have to rely on visuals or routine. But currently I do like the FM on the AH-64D. On its release in EA and even several months later.... well, not so much. Either it's me or something has been improved a lot.

Indeed. That's why a was imprecise about my feelings about the changes over the last few patches. I think I saw a huge difference between my experiences from last year and my experiences now. But I can not really tell what exactly was different but it felt easier and without surprises in behavior in flight. And I did a quick test with the new update this week. For me it looks more or less the same as last week. But it was a quick test only - ten to twenty minutes, not more and without attitude or altitude hold. And as admiki said: those are not like an autopilot in a jet. The only thing that irritates me (but it did this since the AH-64D was released), is that in a hover takeoff the bird tends to fall to the right - until it is in the air. Then any compensation for this will suddenly drift you to left. But maybe there is an explanation for this. But every day I try the AH-64D I need a little practise to get used to it.

I don't think so. I was struggling with some weird behaviors that were hard to get used to for me. They are hard to explain but most often I lost a bit to much control when I was hard turning or slowing down. Sometimes the tail rotor suddenly seemed to do not any affect at all in one direction. But there were other minor effects, that were somewhat counterintuitive. I do not see them anymore.

For me it's the opposite. Load times are much slower (about 5 times slower) in the multithreaded version.

Well. I have just checked DCS again after a few weeks and mainly because of multi-threading support. And I tried the AH-64D just afer the F-18C and I have to agree. The flight model has improved A LOT. Before I always was struggeling to land it or to keep it under control in some situations. Sometimes it seemed to behave weird. And now all this is gone. It just flies like a charm.

Here is some other realism: A human hand or finger hand can hold the covers open after releasing the button under it. But those springs are controlled by some R2D2 in the backseat and (suddenly) get way to stiff just after the button was released. So the pilot has to remove his finger after saying ouch! May you please tell us where we can get this R2D2 today? I would like one of those for my car. And ED: May you just add a voice that says "ouch!" Just for realism, please.

And they sould make a decision and stick to it. Currently to open the cover and to press the button 2 actions are needed. But releasing the button and closing the cover is 1 action - and there is currently no way to release the button but keep the finger under the cover so it won't close just to press the button directly again. It seems they did use some kind of "smart springs" that know whent to push the finger of the pilot out of the way, just after the button is released. But this kind of mess is common to quite a few modules - and those not from ED are often worse. We really need some kind of standard for inputs.

Then how do they stay open when the button is NOT pressed and the pilot is operating something else? Have your pilots more than two hands? As Bozon said: If you argue this way, it is one operation. And do something about the magical open covers if the button is never pressed. Problem is: I have bound a button to OPEN the covers. And as long this button is pressed they should stay OPEN, because the finger of the pilot is holding it OPEN. But your script is closing them despite being held open. If you can't grasp this, you shouldn't be talking about realism. (and do not even try to argue against it, by saying it was just held open momentarily; if you are correct and the covers are spring loaded, then they should close IMMEDIATELY and we could never start the bird). And even if it was momentarily: Because of my config after releasing the starter button the button for OPENING the cover is pressed automatically. But the cover still closes despite the pilot was holding it open again. So obviously it closes while the pilot is holding it open. Tell me: What springs did they use that could do something like this? We do not even have such springs today. So cool, because of your "spring-loaded covers that closes with the fingers of the pilot under it" (ouch!) I will have to check if Joystick-Gremlin can repeat a button press time delayed. Well done. And think about it: A pilot could hold the cover open AFTER he pressed the button under it. Maybe he just wants to press it again. If you want to simulate springs you have to use a button that has to be hold the whole time (this would be fine for me, but not for Bozon) - or you use a toggle as you do for opening the cover. But then there should be a toggle for releasing/closing it too. You can't have a cake and eat it too. And tell us: How should cockpit builders build a starter button like this? If they hold their cover open and yours close automatically then they could not press the button again.

Agreed. And their silly idea to close the covers automatically makes it just worse.

What realism? Did they had R2D2s in their cockpits in 1940 that operate their button covers for them? Is this some kind of Star Wars or what?

Indeed. What comes next? Will they raise the landing gear automatically for us after takeoff?

Do they work in the real plane in the same way? No? Then it is a bug and not a feature. And if they think it is a cool feature, why are they not doing it for other controls too? Why do I have to press starter and coil buttons together? Just press one, open the cover for the other and press it automatically too. Sounds silly? Because it is - like the "automatically closing" button cover is a silly idea too. And in some posts ED tells us they listen to cockpit builders and make it easy for them to adjust controls. Well, scripted button operations out of nowhere and for no reason does quite the opposite...

If you press the ENG/APU fire pusshbuttons with the mouse in the clickable cockpit they stay prssed after releasing the mouse button. If you press them by using a joystick/HOTAS button (or by a keyboard shortcut) the do not stay pressed and are released as soon as the button on the joystick is released. I think this is a bug.

Currently if you have mapped some controls to real switches and you switch from pilot to cp/g then they are out of sync with gameplay. E.g. the NVS mode switch may set to NORM in the pilot seat on the HOTAS but after switching to cp/g it shows no PNVS or TADS in the IHADSS, because it remembers the last setting. So You have to switch back and forth on the HOTAS to show TADS or PNVS. I would like that all switches are just synced if a switch from one seat to the other is done.