Procedural Parts Support

TestFlight has native support for Procedural Parts. Without doing anything special, if you attach a TestFlight config to a procedural part, then TestFlight will but every actual part created in a different size will be treated as a different part.

That means that if you created a 1m by 5m fuel tank and flew it, you would be collecting data on specifically a 1m by 5m tank. If you then created a 1m by 6m tank, that would be a completely new part and start at 0 data. While this "works" it certainly isn't ideal.

Therefore TestFlight has a host of features designed to allow you to more finely control how Procedural Parts are tracked and how technology transfer between parts works. You can use the Advanced Query Syntax supported by both the configuration and techTransfer properties to apply your configs to specific sizes of procedural parts. While this can get a bit complicated on the Config side, it allows for extremely flexible handling of Procedural Parts.

See the wiki page on Advanced Query Syntax to learn how that syntax works. Procedural Parts support adds the following qualifiers to the Query Syntax.

• d for Diameter
• h for Height
• v for Volume
• dMin for Minimum Diameter (IE a cone shaped part)
• dMax for Maximum Diameter (IE a cone shaped part)
• dAvg for the Average Diameter (dMax + dMin) / 2
• dVar for the Variation in Diameter (dMax - dMin)