API Question Detecting a docked vessel's actual thruster count

[dbeachy1]

I'm calling pVessel->GetThrusterCount() to detect whether another vessel has at least one thruster defined. It works fine unless the vessel happens to be docked to another vessel -- for example, when a payload vessel with no thrusters is docked to its parent vessel that does have thrusters. In that case, calling GetThrusterCount() on the payload vessel returns the parent vessel's thruster count (??). I assume this is by design since a docked vessel is part of a superstructure? So I'm trying to figure out a way to reliably detect if a given vessel has thrusters defined, even if it's docked. I keep thinking I'm missing something obvious...any ideas?? Thanks.

 

[GLS]

Loop GetThrusterHandleByIndex() until it returns NULL?

 

[jedidia]

In that case, calling GetThrusterCount() on the payload vessel returns the parent vessel's thruster count (??).

Are you certain that you have the right vessel (It's a dumb question, I know, but... it's code. Better check twice for silly mistakes)? Going on the documentation, that would clearly be a bug.

Moreover, docking establishes flat relationships, not hierarchical ones, so there wouldn't even be a way for Orbiter to determine parent and child.
Orbiter 2016 has new handling for docked stacks, but nothing in the documentation suggests that GetThrusterCount() would be affected by this.

 

[dbeachy1]

Thanks for the ideas, guys, I'll look into it more tonight and report back.

EDIT:
So I tracked down the issue: a payload vessel only shows a thruster count when its .cfg file specifies any of these settings (even setting them to 0):

MaxMainThrust = 0
MaxRetroThrust = 0
MaxHoverThrust = 0
MaxAttitudeThrust = 0

If a payload vessel specifies all of those, the Orbiter core creates a total of 21 thrusters for it. So it turns out that GetThrusterCount() is fine, and docking it to a vessel is not the issue. The fix in my case here was to edit these payload vessel .cfg files to remove those lines above.

Thanks the advice, guys, it was indeed a separate bug, and not Orbiter core-related! :tiphat: