Ran a flight from HOU to DAL.. Noticed something kind of weird,and doesn't seem right. When you get to TOD, it switches to ARMmode. So I start descending, and I decided to check the hardwarethrottle blue markers to see if they now worked in ARM mode.Nope.. But worse.. When I moved my throttle, it was overriding theA/T when in ARM mode. If I'm not mistaken, it should not do anything,same as in FMC mode. I know it didn't on the earlier versions.But now, if I move the throttles, it's overriding the A/T and seemsto have an effect on the throttle setting even if I leave it at one spot.I tried turning off the A/T and pushing the hardware throttle up a goodbit, then turning the A/T back on. It does reduce the thrust, but thelowest thrust setting still seems to be slightly effected. IE:.. If I rollthe hardware throttle back to zero, I get a slight further reduction inthe A/T as far as it's minimum setting.I then turned around and flew back to Houston.. Same thing on thatdescent.. What is kinda weird is that it seems to operate fairlynormally at TOD. IE: it reduces thrust, etc to a fairly normal level.But the second I adjust my hardware throttle, it takes over.Doesn't seem right, and I think the earlier versions had this correctwhere the hardware throttle had no effect in ARM mode..I'm thinking maybe they were trying to fix the "blue marker" issuein ARM mode, but just guessing. I much prefer it the way it was,particularly being that the blue markers are still not working.Actually, I rarely ever need to use those markers at that stage inthe flight. So really wasn't a big deal to me.. I use em when onapproach, and they have always worked at that point, being inFMC mode.Anyone else notice this?

Come to think of it, I noticed this when I flew the tutorial again to test the HF. I inadvertantly moved the throttle lever forward and the ac began accelerating at full throttle, I just instinctively throttled back to idle and it returned to ARM mode.

Guys check your settings. Setup, Options, Simulation, and then Page 2 Show Thrust Lever Position - Options are (No, Yes, When Moving) A/T Manual Overide - Options are (In HOLD/ARM Mode Only, Never, Always) I have mine set to When Moving and HOLD/ARM Mode Only.

You guys have a pretty serious misunderstanding on how this system works in the real airplane I think: ARM mode means that the A/T servos disconnect from the thrust levers - there is no position being commanded. It is fully possible to move the throttles manually while in ARM - that's how the system is designed. If you need to manually increase thrust slightly to account for a headwind while descending or something like that you can do it in ARM mode. There's an A/T mode just like this in the MD-11 called "CLAMP" btw. If you don't want the physical throttle to ever move the thrust levers while A/T is active, set the A/T Manual Override option to NEVER. This is unrealistic though - in the real airplane, ARM always allows manually movement. ARM doesn't show the blue physical throttle arc because the AT is not commanding anything. You are free in that mode to move them however you like and they will match up with the sim's thrust levers. At T/D when VNAV does the RETARD to ARM transition - it is assumed the throttles are at idle - they'll never be at anything else unless you put them there.

Since applying HF4, I experienced issues during take off runs. I usually advance throttle quadrant to 3/4 power and then press AT hot spot. You can see the AT take over but half way down the runway the power starts coming back, maybe almost to the location of the physical position of the throttle quadrant. Recovered by pushing power all the way up via device. This is a new behavior. Regards, Fabio van Roon

OK, thanks for the explanation.. Yep, I thought they were still beingcommanded. And it's quite possible that the settings I had were areason this didn't function on the previous versions.Before, if I manually operated the throttles in ARM, they had no effect, andI thought that was normal. So I guess it's now working more realisticallythan before. I haven't noticed anything really different on take off runs,but I'll keep an eye out for anything unusual.

Since applying HF4, I experienced issues during take off runs. I usually advance throttle quadrant to 3/4 power and then press AT hot spot. You can see the AT take over but half way down the runway the power starts coming back, maybe almost to the location of the physical position of the throttle quadrant. Recovered by pushing power all the way up via device. This is a new behavior. Regards, Fabio van Roon

The throttle does go to ARM mode when it reaches the takeoff N1 - there's probably some jitter in your joystick throttle and it causes it to go back to the physical position while in ARM mode like that. Calibrate the device, try setting a small dead-zone etc. I always push my physical throttle up to align it with the target TO N1 anyway - turn on the Show Physical Throttle Position option and it makes it very easy. This type of issue can't happen if you do that.

The throttle does go to ARM mode when it reaches the takeoff N1 - there's probably some jitter in your joystick throttle and it causes it to go back to the physical position while in ARM mode like that. Calibrate the device, try setting a small dead-zone etc. I always push my physical throttle up to align it with the target TO N1 anyway - turn on the Show Physical Throttle Position option and it makes it very easy. This type of issue can't happen if you do that.

The throttle does go to ARM mode when it reaches the takeoff N1 - there's probably some jitter in your joystick throttle and it causes it to go back to the physical position while in ARM mode like that. Calibrate the device, try setting a small dead-zone etc. I always push my physical throttle up to align it with the target TO N1 anyway - turn on the Show Physical Throttle Position option and it makes it very easy. This type of issue can't happen if you do that.

The throttle does go to ARM mode when it reaches the takeoff N1 - there's probably some jitter in your joystick throttle and it causes it to go back to the physical position while in ARM mode like that. Calibrate the device, try setting a small dead-zone etc. I always push my physical throttle up to align it with the target TO N1 anyway - turn on the Show Physical Throttle Position option and it makes it very easy. This type of issue can't happen if you do that.

Yes Ryan,... I noticed during take off my engines suddenly throttled back to Idle.I seems that without me advancing my CH throttle position in line with the increasing N1, the period during THOTTLE HOLD it sensed that my throttles were in the last position which was approx 40% N1, so retarded Take off Power.So now I advance my throttles in sync with that excellent feature 'Show Thrust Lever Pos' to the calculated N1 & no more problems! Stewart Thompson

Thanks for explaining this, Ryan. It totally clears up my questions about the throttle.

Ryan, thanks for the information. Will apply during my next flight. Regards, Fabio van Roon

Since applying HF4, I experienced issues during take off runs. I usually advance throttle quadrant to 3/4 power and then press AT hot spot. You can see the AT take over but half way down the runway the power starts coming back, maybe almost to the location of the physical position of the throttle quadrant. Recovered by pushing power all the way up via device. This is a new behavior. Regards, Fabio van Roon

I am also getting this since HF4. Note the fix (or is it fudge?), but it did not do this before.

I also have the same issues. AT disengages at V1. Then I have all sort of disengages during descend, Never had this problems before hotfix4. I calibrated my X52. All sensitivities are ok. No FSUIPC. Danko Crnkovic

The Never & Always options are now gone with Hofix 4 !!

HOLD/ARM Mode and Always show up as White, and Never Shows up as Yellow. Yes I have Hotfix 4 and they are still there. If they are not showing up for you then your not doing something right or you screwed up your hotfix 4 installation. Suggest you reinstall the NGX. The way I upgraded to Hotfix 4 is below. Step 1) Uninstall Liveries and Uninstall NGXStep 2) Use NGX Installer with Hotfix 1, 2, 3 includedStep 3) Install Hotfix 4Step 4) Install Liveries

Since applying HF4, I experienced issues during take off runs. I usually advance throttle quadrant to 3/4 power and then press AT hot spot. You can see the AT take over but half way down the runway the power starts coming back, maybe almost to the location of the physical position of the throttle quadrant. Recovered by pushing power all the way up via device. This is a new behavior.

Not sure if this applys to your situation but I was having the same issue with the power coming back. Figured out it was FSUIPC. Earlier in the month I was messing around with the Calibration in FSUIPC to get it to use Thrust Reverse on my X52 Pro Throttle. Had issues with that so stopped using it and went back to using a button for thrust reversers. So Now the Trigger is back to Thrust Reversers and the Pinkie Trigger is Throttle Cut which will turn off the reversers without you having to advance the throttles. Anyway what I forgot in FSUIPC was the Throttle was still setup for calibration in FSUIPC. Soon as I went in there and hit the reset button the problem went away. I am guessing simconnect and fsuipc are not playing nice together. So is probably better to use FSUIPC for assigning buttons only and not for Calibration and Axis assignment because that does seem to cause issues. I also remember a couple threads where PMDG recommended against using FSUIPC for axis and calibration. So obviously they are recommending you do not do this for a very good reason. I am not having any problems at all now with just buttons assigned through FSUIPC. So you might want to check that in your settings and see how it works for you. If you need to calibrate, do it through FSX or Control Panel - Game Controllers. I do it every flight before I leave the gate.

I had posted an "A/T disengaging" issue yesterday and thought it might have been related to the weather engine. Now, I'm not so sure. My issue of the A/T disengaging is shortly after I reach cruise altitude... and this didn't have until I installed HF4 also. If anyone on this thread has any ideas about my situation, I'd appreciate ANY assistance. My thread is here: http://forum.avsim.net/topic/350101-autothrottle-disengaging-at-cruise/

Jason, My options like yours are missing too.I also had to reinstall win 7 recently and also FSX, PMDG, hotfix, etc.. and I thought it was a tweak PMDG did that was causing some problems - so now it has been removed. Maybe Ryan or someone will tell us of the fixes in the Hotfix so we will know. Benny Miller