I've even tried it with my hardware throttle unplugged. Same result. Trust me, it's the plane, not user/controller error.

That's what I say too ;-)

Daniel,Your response was vague as to what you're talking about. The throttle in the sim and the hardware throttle you have attached to your computer are completely different entities and the sim will pay attention to both, if you allow it to, which can cause issues. So, what you're saying is, even if you have your hardware throttles at 100%, when you hit TO/GA, you're getting rated thrust and then a reduction? All I'm trying to do is make sure something else isn't the cause. I teach computer classes as my day job and if you really want me to, I'll start tracking the stats. For now, I'd venture to guess 90% of those who assert they did something correctly and it's the computer's fault are the ones who are at fault. The rest of them found some quirk. I'm not saying you're wrong, I'm saying you need to need to explore the possibilities. Since I didn't know anyone disconnected their hardware throttles, I had to start at the lowest common denominator: human error. Once all of that eventually came out, we could start ruling things out, but that wouldn't have come out unless someone started asking the questions. All I'm trying to do is help find the issue. I'm not trying to imply you're all dumb, so you don't need to take it that way. I just have a cynical view of anyone who uses a computer, and even more of a cynical view of someone who, not providing specific information about what lead to the issue, asserts it's not them. That's just me being jaded from my jobs, I guess.

Daniel,Your response was vague as to what you're talking about. The throttle in the sim and the hardware throttle you have attached to your computer are completely different entities and the sim will pay attention to both, if you allow it to, which can cause issues. So, what you're saying is, even if you have your hardware throttles at 100%, when you hit TO/GA, you're getting rated thrust and then a reduction? All I'm trying to do is make sure something else isn't the cause. I teach computer classes as my day job and if you really want me to, I'll start tracking the stats. For now, I'd venture to guess 90% of those who assert they did something correctly and it's the computer's fault are the ones who are at fault. The rest of them found some quirk. I'm not saying you're wrong, I'm saying you need to need to explore the possibilities. Since I didn't know anyone disconnected their hardware throttles, I had to start at the lowest common denominator: human error. Once all of that eventually came out, we could start ruling things out, but that wouldn't have come out unless someone started asking the questions. All I'm trying to do is help find the issue. I'm not trying to imply you're all dumb, so you don't need to take it that way. I just have a cynical view of anyone who uses a computer, and even more of a cynical view of someone who, not providing specific information about what lead to the issue, asserts it's not them. That's just me being jaded from my jobs, I guess.

Regardless of where my hardware throttles are, and whether they are plugged in or unplugged, it will still perform the same. I'm amost certain this is what other users are experiencing, but I can only speak for myself. This is not human/computer error but something with the go-around logic is not operating properly.

Daniel,Your response was vague as to what you're talking about. The throttle in the sim and the hardware throttle you have attached to your computer are completely different entities and the sim will pay attention to both, if you allow it to, which can cause issues. So, what you're saying is, even if you have your hardware throttles at 100%, when you hit TO/GA, you're getting rated thrust and then a reduction? All I'm trying to do is make sure something else isn't the cause. I teach computer classes as my day job and if you really want me to, I'll start tracking the stats. For now, I'd venture to guess 90% of those who assert they did something correctly and it's the computer's fault are the ones who are at fault. The rest of them found some quirk. I'm not saying you're wrong, I'm saying you need to need to explore the possibilities. Since I didn't know anyone disconnected their hardware throttles, I had to start at the lowest common denominator: human error. Once all of that eventually came out, we could start ruling things out, but that wouldn't have come out unless someone started asking the questions. All I'm trying to do is help find the issue. I'm not trying to imply you're all dumb, so you don't need to take it that way. I just have a cynical view of anyone who uses a computer, and even more of a cynical view of someone who, not providing specific information about what lead to the issue, asserts it's not them. That's just me being jaded from my jobs, I guess.

No hard feelings buddy! I know you want to help and your strategy is correct. But this is not a new problem. This issue is well known since the very beginning. It's up to the PMDG team to solve it. They got it right with the original 737NG so I'm fully confident they will get it right with the NGX too, eventually.

When performing a automatic go-around the auto throttle has control over the power setting. When you hit the TO/GA you will see a N1 rise to go-around thrust and immediately backing off again resulting in a climbrate of <1000fpm, even if your throttles are at max before commencing the the go-around. So yes, I'm telling you this has nothing to do with the hardware. This is a software issue.

According to the FCOM this is exactly what it's supposed to do. You'll get enough N1 to achieve 1000 fpm (at Flap 15). Less flap means a higher V/S target. The FCOM refers to reduced GA thrust. On my NGX N1 goes to GA initially then backs off as rate of climb reaches the target. The A/T won't set full GA thrust unless you push TOGA a second time (if N1 has reached reduced GA thrust). Kevin Hall

According to the FCOM this is exactly what it's supposed to do. You'll get enough N1 to achieve 1000 fpm (at Flap 15). Less flap means a higher V/S target. The FCOM refers to reduced GA thrust. On my NGX N1 goes to GA initially then backs off as rate of climb reaches the target. The A/T won't set full GA thrust unless you push TOGA a second time (if N1 has reached reduced GA thrust). Kevin Hall

Kevin, According to the FCOM you will get reduced go-around power and a climb rate of between 1000-2000 fpm after the first press of either the To/GA switches. In the NGX, like you said, you initially get full GA thrust (which is not correct) before it backs off again and you get a climb rate which is lower then 1000 fpm. Do you agree with me that this is not like the FCOM?

even captainsim get there GA logic right. Captainsim!

Kevin, According to the FCOM you will get reduced go-around power and a climb rate of between 1000-2000 fpm after the first press of either the To/GA switches. In the NGX, like you said, you initially get full GA thrust (which is not correct) before it backs off again and you get a climb rate which is lower then 1000 fpm. Do you agree with me that this is not like the FCOM?

I got 1000 fpm climb rate at flap 15, which is why I didn't see a problem. My take on the 1000-2000 fpm is that the commanded V/S will vary with the flap setting. I haven't tried with less flap to see if the V/S command increases. Kevin Hall

even captainsim get there GA logic right. Captainsim!

Have CaptSim done an NG? And are you sure they got it right in all respects on the types they have done? Kevin Hall

^ I really dnt know but srsly this is something annoying . Maybe I should just start buying Abacus... Lol F*** that!

^ I really dnt know but srsly this is something annoying . Maybe I should just start buying Abacus... Lol F*** that!

And whats your point? I still see that you dont take any advice by other members about the forum rules, maybe you should take time to read them.