Moxica

I know. I was just pointing out how the "greyed out" is looking in the picture. Those fields are "greyed out" which is a Windows term. DCS does this with a different color nuance. Because I have to pull it down, and up again for it to work. "Up" represent both functions. "Up" for arm, and "Down/Up again" to turn it off. ..or wait a minute.. Hmm.

Yes, the "EAC 2-pos Switch : ARM<>OFF" reacts to doubleclick. But that function is not appropriate. I would like to use button 24 and 24 off. I do not understand any logic that will disable that? ..and the entire unit? Que? :)

But yes, there are four fields that are "greyed" out in that picture: Keyboard and joystick for the "EAC 2 pos..." and Throttle EAC arm on and off. (They are merely a notch less brighter blue) I have cleaned, slow repaired, just to find there are more of those: APU start, Engine start.. plus a few more. I have reset, and loaded default cathegories to no avail. And nothing happens when I right-click.

First try was after entering module. Screenshot is from the main screen, as I just did it for this forum thread. And I doublechecked just now; It is Disabled/greyed out/inactive. Edit: It worked on the A10A But I can't assign engine start buttons either.

Here, Max! Thank you (Its the same for the HMCS)

As title say; Double clicking on the assignment does nothing. It seem to be de-activated. HALP!

Vehicles on roads are hard to lock on, because the maverick seem to prioritize telephone/power/lighting poles. Should this be normal, or are someone pulling our legs?

Nope. They just played it wrong. Very strange, because it was my first landing in a tight spot with AH-64, and the replay landed on the other side of the road with plenty of space.

No special software: Device manager and "Settings/Bluetooth and units/units

Orly?

In that case, it should be enough to link to the mission, if it is downloaded from the user files section. Or if it is one of the default ones.

Update for success report; I deleted blindly four or five USB controllers with a dubious report about "settings not migrated.." in device manager. -Until my Thrustmaster went dark, and I could not use them. Those were a few minutes of horror. But I disconnected/reconnected to another USB port, and back to original, and they came back to life. But today, the PS3/PC/Android thing was gone/replaced by another unused, and not-connected Xbox controller. That one was removed easily, and the annoyance seem to be gone. -Even after reboot. Thanks again for your engagement, which in my eyes is pretty darn close to heroic for such a tiny and self-inflicted pickle. Much appreciated!

I don't have any problems, but I'm just curious: Are tracks rendered in real time during playback? If so, how can they diagnose performance issues if played on a different rig? How are they useful, when they dont play the same as the actual mission/flight? (One of my tracks had me landing on a totally different spot than actual flight, for example Another had me chrashing into a tree right after takeoff, which did not happen during flight)

Thanks, gentlemen! I have a few options to try when I get home from work today. If none succeed, I can still live with that little nuisance. Thank you so much for your contributions.

Built in where? I don't seem to have it.

Yes. I found it i the DXdiag. Thx again. DxDiag.txt

Hi again. Here it is: export.log

Thanks a lot for hanging in there, F! Will do as soon as I get home from work.

Happens to me as well on occations. There is some detail I'm doing wrong. Has to do with flaps or trim setting. -Because I've fumbled with those more or less randomly, and sometimes have success. But in spite of seeing it once, I can not remember the correct settings, and those two details are kind of hard to find. (Unless willing to plow through a lot of documentation/kissing a lot of frogs)

Darn! It keeps coming back when I reboot, and creates these files: PC_PS3_Android {E876A040-26C3-11ed-8001-444553540000}.diff.lua null

I have had some success hitting hidden tanks by targeting adjacent Toyotas etc.., and sending more than one Lima on same target. 2nd. missile took out annoying, sneaky, hiding tank to my great satisfaction. Probably because the *Toyota* was no longer there.

T'will be imminent soon in a while. -Waiting for the "soon to be imminent" announcement release date.

Well, all my former three sets of muscle memory are out the door. I'm almost at scratch. Must start at the beginning. -Or do something radical. -Which I did. -Ordered a stick extention.

..aand that worked. Thank you. I've been struggling with this for months! Your answer put me in the right direction thought-wise. (If there is such a term in english)