If you load an existing craft design via open -> merge, and then clone an engine of that craft file via "ALT + left click" TF's middle click tooltip doesn't seem to be initialising properly. It shows "Active Part: [blank]".
If you then change that engine config, the burntime and reliability data in the tooltip don't update to reflect the changed engine config.
Reproduction recipe.
In the VAB start a new craft. Grab a proc tank for the root part, and attach an Aerobee engine. Name the craft and save it.
Start another new craft. Grab a proc tank for the root part.
Access the previous vessel via Open -> (select the craft you saved above) -> Merge. Left click to drop it in the VAB.
Now clone the Aerobee with "ALT + left click", and attach it to the root part. Middle click the engine. The TF tooltip should show ""Active Part: [blank]". TF also wont update the the tooltip if you change to a different engine config.
If you clone the tank + engine you have the same issue.
Grabbing and dropping a subassembly containing an engine then cloning the engine also triggers the issue.
Hi
If you load an existing craft design via open -> merge, and then clone an engine of that craft file via "ALT + left click" TF's middle click tooltip doesn't seem to be initialising properly. It shows "Active Part: [blank]".
If you then change that engine config, the burntime and reliability data in the tooltip don't update to reflect the changed engine config.
Reproduction recipe.
In the VAB start a new craft. Grab a proc tank for the root part, and attach an Aerobee engine. Name the craft and save it.
Start another new craft. Grab a proc tank for the root part.
Access the previous vessel via Open -> (select the craft you saved above) -> Merge. Left click to drop it in the VAB.
Now clone the Aerobee with "ALT + left click", and attach it to the root part. Middle click the engine. The TF tooltip should show ""Active Part: [blank]". TF also wont update the the tooltip if you change to a different engine config.
If you clone the tank + engine you have the same issue.
Grabbing and dropping a subassembly containing an engine then cloning the engine also triggers the issue.
RP-1 Express install on KSP 1.12.3 on Win 11.
Thanks for your work on TestFlight.