Hi guys. I decided to go back to this wonderful plane a couple of days ago. I know it's very complex and it's probably some stupid error(s) I'm doing, but I can't seem to get the A/T to work at all. Every time I engage it thrust will go to about 82% N1 and won't move from there, no matter what target speed I command so it eventually overpeeds. Actually it doesn't hold speed in any mode (VNAV engaged, VERT SPD,....)I'm completely lost, been re-reading the manuals but can't find anything that might explain what's going on. My flight plan is filed ok in the FMS with the "Pre FLT complete" message and all. It happens in all phases of the flight (climb, cruise, descend...)Aircond switches are in auto (found in the Maddog forums a thread where they said having them in manual would have the same effect)Thanks in advance

No maddog experts? I wish I could ask in their forums but they need to manually activate my account there first and those boards are not too active apparently.I have tried unplugging my yoke, TQ's and usb panels. Happens regardless the mode selected in the TRP, phase of flight, and the thing is that I used to fly it no problem.

More information is needed. The auto throttle will do different things depending on the FMA modes. What were these in your instance? Additionally, manual hardware throttle movements will affect what the Maddog auto throttle does, so what was your hardware throttle set at?

More information is needed. The auto throttle will do different things depending on the FMA modes. What were these in your instance? Additionally, manual hardware throttle movements will affect what the Maddog auto throttle does, so what was your hardware throttle set at?

It does the same thing no matter what mode I select in the FGCP (SPD SEL, EPR CLB,...) or the TRP. As soon as I engage the A/T, N1 goes to 80 - 82% and never moves from there, even though the FMA reads SPD 250 for example, throttles won't retard once 250 knots are attained.While in VNAV mode, I can see in my CLB page the ECON Climb Speed in the FMS (308) but sometimes it will still get passed that. Even worse while cruising obviously.I ruled out (or at least I think so) yoke interference, since I unplugged everything and used F1 to bring the throttles to idle. Then engaged A/T and bang, 80% N1 againI'll take some screenshots

SPD 250 ignored, CL in the TRP:Cruising:Maybe try FMS OVRD? no joy:

And what about your hardware throttles? The Maddog will preference inputs from the hardware throttles over input from the software autothrottle. So this can also be an issue and given what you're syaing, I suspect is the root of your problem. Hardware control spikes in particular can be problems. What hardware is it, how is it calibrated, how are the axes assigned and what is the actual position of the hardware (particularly important if controller spikes are the cause).

And what about your hardware throttles? The Maddog will preference inputs from the hardware throttles over input from the software autothrottle. So this can also be an issue and given what you're syaing, I suspect is the root of your problem. Hardware control spikes in particular can be problems. What hardware is it, how is it calibrated, how are the axes assigned and what is the actual position of the hardware (particularly important if controller spikes are the cause).

Yeah, I unplugged everything, I mean the yoke, both throttle quadrants (Saitek, so yes plenty spikes :() the VRInsight MCP combo panel, a little custom panel I'm building... only keyboard and mouseI think I'm going to back up the system and try reinstalling

If this doesn't help, maybe check the FSUIPC version too. 4.70 should do it. There were some reported problems when using older releases.The AT implementation on that bird is somehow touchy. Some (few!) over-rev their engines at TO, others distract the (enabled) AT system when touching the throttles later.

If this doesn't help, maybe check the FSUIPC version too. 4.70 should do it. There were some reported problems when using older releases.The AT implementation on that bird is somehow touchy. Some (few!) over-rev their engines at TO, others distract the (enabled) AT system when touching the throttles later.

I tried the newest version and the mouse macros seem to be broken, so had to go back to V4.654. Will need to make sure it's not something on my end before I report that to Pete.Anyway, deleted the FSUIPC4 dll and A/T came back to life so I put it back in place and modified my throttle axis settings and it works now. Not sure if it was having two levers control each engine (now I use only 1 lever for both engines to avoid spikes) or sending the axes straight to FSUIPC calibration instead of as FS normal axis, or the axis filtering... I changed a number of things so don't know what did the trick, but it works like a charm now.Thanks for putting me in the right track

Glad to read this. :( What happens if you leave the FSUIPC calibration (of the throttles) out by going "aircraft specific" + unchecking the calibration data. Then setting up the two axes in FSX only, rendering them to pure and direct FSX controls for the Maddog only.This is necessary on some of my birds (VRS Superbug, Simcheck A300, so far the iFly 737) as they didn't seem to like the FSUIPC throttles at all, mixing up the AT then. Haven't tried the maddog a while, but will do later to see if this is needed there too. I'm running G940 throttles here, so another twin setup like yours.I didn't read about a macro problem at FSUIPC 4.70, but there's an updated module out which leads to 4.705, maybe this helps too.Oh, after looking, what about this option in the Load Manager?As you see, tons of things to still experiment.

Yeah, I already had tried the throttle filtering in the maddog's load manager settings, but that's just supposed to filter the axis while in clamp mode during T/O. Didn't make a differenceI have tried setting the axis through FSUIPC and direct to FS, switching on/off filtering and it still works, so there was probably something wrong with my dual lever setup. I don't know for sure, but I'll let go for now, I have a more pressing issue now with my GPU downclocking to 2D speeds while FSX is running. doh! man, this hobby can be so frustrating...

You are right about that option.I just took a ride again and must say that she still is a fine ship, and a fps eater. But she's ok with FSUIPC throttles of any kind, no problem here.That downclocking should be avoided when you go into the FSX Nvidia profile and look for the "Power Management Mode". "Prefer maximum performance" may help. You can also set that in the general profile for all games, but this may elevate the clocks away from any energy saving when it is useful.But who knows, maybe some overclocking app interferes there and doesn't think of FSX being an app to deserve high clockrates.

You are right about that option.I just took a ride again and must say that she still is a fine ship, and a fps eater. But she's ok with FSUIPC throttles of any kind, no problem here.That downclocking should be avoided when you go into the FSX Nvidia profile and look for the "Power Management Mode". "Prefer maximum performance" may help. You can also set that in the general profile for all games, but this may elevate the clocks away from any energy saving when it is useful.

yes, I just checked the Inspector thread and noticed I had forgotten to set that to maximum performance :( LOL I feel like a noob

Don't worry, I know that feeling oh so well. :(