Lockheed L-1011 Autothrust TM mode EPR problem

[Eli128gb]

Hello everyone, 

 

I have the problem that whenever I want to use the Thrustmanagement mode to climb, it shows the EPR 000 and the engines spool down. I have set everything up correctly including both PMS, have already played around with switching of probe Heat, and many more things. I would be really glad if anyone had a solution or at least knows if this is a bug or I’m missing something systemwise. 
 

kind regards Elias!

[Trevor]

You have to fill in all the required parameters in the first 4 pages or so like BOD distance etc. Happened to me as well until I figured it out

[mph163]

1 hour ago, Trevor said:

You have to fill in all the required parameters in the first 4 pages or so like BOD distance etc. Happened to me as well until I figured it out

I did that but mine still does the same as @Eli128gb says until I engage the autopilot, then it works. 
 

Side note I have my airplane set to KG in the PFB do I still need to put LBS into the PMS? I have been putting KG into it. 

Edited yesterday at 03:34 PM by mph163

[Joshua Green]

Did you need to engage the autopilot itself or just set a pitch mode on the panel? I found that mine would engage correctly as long as I had some pitch mode engaged. But still, it's supposed to be completely independent, isn't it?

[mph163]

4 hours ago, Joshua Green said:

Did you need to engage the autopilot itself or just set a pitch mode on the panel? I found that mine would engage correctly as long as I had some pitch mode engaged. But still, it's supposed to be completely independent, isn't it?

No I had to engage the autopilot itself (move one of the paddle switches) in order for the TM function to work properly!

[Joshua Green]

Ok, definitely sounds like a bug, then.

[mph163]

I just checked and it doesn't matter what units I enter. TM mode gives 000 until I engage the autopilot. I have seen the same behaviour on several people's videos and streams as well. 
I wonder whether the team can confirm whether this issue has been logged.