The bug can be reproduced in KSP 1.2.2, with ModuleManager 2.7.6, TestFlight 1.8.0.1, and this config file. The fastest way to reproduce this bug is to create a new sandbox game, put the Kerbal 1 on the launchpad, exit to KSC, then resume the flight. Immediately after starting the flight, TestFlight will track both the command module and the second stage engine; after resuming from KSC, it will only notice the engine. There are no errors/warnings in the log, even with debug output enabled.
This bug is not associated with prelaunch status, and applies also to orbiting spacecraft. For example, if I launch the Kerbal 1 into orbit, the eventual TestFlight screen looks like this:
If I go to KSC and reload the flight through the tracking station, I get this:
This bug also applies if you quit KSP and later reload the save game.
I have not yet had a chance to try to isolate which TF modules are causing the problem; I'll post an update if I learn more.
The bug can be reproduced in KSP 1.2.2, with ModuleManager 2.7.6, TestFlight 1.8.0.1, and this config file. The fastest way to reproduce this bug is to create a new sandbox game, put the Kerbal 1 on the launchpad, exit to KSC, then resume the flight. Immediately after starting the flight, TestFlight will track both the command module and the second stage engine; after resuming from KSC, it will only notice the engine. There are no errors/warnings in the log, even with debug output enabled.
This bug is not associated with prelaunch status, and applies also to orbiting spacecraft. For example, if I launch the Kerbal 1 into orbit, the eventual TestFlight screen looks like this: If I go to KSC and reload the flight through the tracking station, I get this:
This bug also applies if you quit KSP and later reload the save game.
I have not yet had a chance to try to isolate which TF modules are causing the problem; I'll post an update if I learn more.