max_thrust returns incorrect value for engine thrust
Otaku-Labs opened this issue ยท 3 comments
I was trying to write a script for a suicide burn/hover-slam and after slamming into the ground over and over I started double checking the values and noticed that in my stream of T as shown below, when I call T() it returns a value of 294327.53 (rounded), or 2,943.28-kN and the thrust readout in KSP indicates 2,649.00-kN. A difference of nearly 300-kN
T = conn.add_stream(getattr, vessel, 'max_thrust')
I'd like to try to reproduce this if I can. What engines are you using and how many? I'd like to see if I get the same thrust value.
Is this a situation where 'available_thrust' is more appropriate than 'max_thrust'?
What engines are you using and how many?
I should have noted it in the report... I have forgot by this point. I might be able to reload the save if I still have it, but, I'm out of town currently. I haven't messed with KRPC in a while because I wasn't sure if it was still supported.
Is this a situation where 'available_thrust' is more appropriate than 'max_thrust'?
The result were the same whether using max or available.
@praxeo Going back, I'm not able to tell which save I was using (they're a bit disorganized). I want to say it was the:
S3 KS-25 "Vector" Liquid Fuel Engine
I can't be sure though. I would suggest trying it with any engine and see if you have conflicting read-outs. If you can't find any, I'll just close this and re-open if I rediscover it.