Nereid

I just did a time comparison for the load times: Instant Action (AH-64D, Caucasus, Cold Start) MT: 95 seconds Non MT: 21 seconds

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.

If you select an instant action for the AH-64D for a map then it loads within a few seconds in the non multithreaded version even the first time. In the multithreaded version it could take minutes or it won't even start at all (within a reasonable time). This happens not all the time but the first time or after choosing a different map in between. The map loading times are huge compared to the non multithreaded version. This happens sometimes (but rarely) with self created (and simple) missions too. (corection: I start them from the editor most of the time. And loading the map into the editor takes forever in the MT version) Otherwise: Congratulations. Aside from a little stuttering every few minutes for halfd a second or so, it works great. version: 2.8.3.38090 drive: SSD RAM: 64 GB CPU: i7 13700K Win-10

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.

This very annoying bug (it stops my from using my Virpil controls as I intended to use them) is still present in 2.8.3.38090.

This bug is still present in 2.8.34437.

Seems we have to wait for an after early access manual...

Thanks. So the P8 is just a backup. That explains a lot - and it's a pain in the *ss to read it. So what is correct? Is the compass just a backup ore the main source for a heading? I'm confused now...

Yes. But it is currently broken, because the covers do close automatically after the button is pressed. If you want to support cockpit builders remove this "feature" (it is a bug IMHO) and yes, an option to "simplify" it with a shortcut to open the cover AND press the button would be nice. Not all virtual pilots do have the equipment to assign extra buttons for operating covers...

They have done extra coding to close the covers automatically (but not to open them automatically which makes no sense). So extra coding is no excuse. This is another valid point. I have bound the flap lever lock to a two state switch. So the button to unlock is ALWAYS pressed, i.e. the lock is held OPEN by the pilot. But the lock closes without input automatically so my switch is out of sync with the cockpit. In my opinion: If there is a control to open a lock, it should stay open - at least as long the control is pressed. And if they want realism, by forcing to open the lock, they should not give up realism by automatically closing covers that would not close automatically in the real plane. You can't have a cake and eat it too. Best option would be extra controls to allow people with less input options to operate switches levers by automatically open locks and covers but provide single controls to operate all separately too. And they should add controls for the states for all levers/swiches and not just up/down binds as it is done for the flaps currently. They should think about a standard for all modules to do it this way.

Then they should stop this. This is not helpful but a nuisance. And because the covers won't close automatically in the real plane I would call it a bug - until they add an option to disable this. And if they like it, they should make the buttons clickable even if the cover is DOWN (or open it automatically if the button is pressed). To emphasize it: I would NOT have bought the module if this behaviour was in place as I tested it or I was just not aware of it. It is a mess at this point. Exactly. I in my opinion they should remove it ASAP or fix it by adding new control options.

What should the R.I. Compass Repeater display? Magnetic heading? So it is linked to the compass or it has its own? Or should it display true heading? Then how it is adjusted? And currently it displays neither. Not true heading nor magnetic heading but it is always a bit off. A bug? Or is it working as it should?

The flap lever lock is automatically locking after flap lever is pulled up (from the lower position). Is this intended? This happens even if the unlock button is constantly pressed. This behavior makes it diffucult/impossible to bind (two state) switches to this lock.

Can we please have three state shortcuts (up/middle/down) for the flaps lever? The up/down controls does make it impossible to use an axis/button lever on some control hardware (virpil throttle in this case).

If you open the cover for a start or booster coil the cover closes automatically when the button is released (for no apparent reason - I don't think it does this in the real aircraft). This is very annoying, because for a second try you have to reopen the cover. For people using virpil control panels the buttons stops working for no reason, after the button is released (we have four switches with covers that do not work anymore since this behaviour was introduced). This happens if the button is pressed by a key/button shortcut or with the mouse. Version: 2.8.0.33006

So the windscreen wiper is now at last animated and is working if the wiper control switch is clicked with the mouse. But the key/button bindings do not work - at least not for me. Version: 2.8.0.32235.1

No problem. I was just asking if they binds are working. Currently they are not and that was the answere to my question.