I’m currently working on the Cosmo Messer F2 and the Ts. The F2s are just an upgraded, printable version of the original F model (henceforth referred to as the F1). Aside from having exposed hydrogen tanks on the ventral side and an offset connector to compensate, it’s a superior build to the F1s. The T model is based on the F2, but it’s designed for carriers. The Hipper currently carries up to 12(14) Messer F2s while carriers like the Seydlitz can handle up to 27 Messer Ts.

I decided I’m going to make two versions of the Cosmo Messer T. Both are going to have the exact same designation, but the second version is going to be an Autopillock variant with no scripts or QoL features in the cockpit that aren’t essential for operations: it’s essentially a drone dressed up as a manned unit. This is to get around a couple of problems I’ve been having designing the blasted things.

Autopillock is a very advanced automation script, so the ‘APck Messer T’ is going to take a fair bit longer than the normal version to finish. If you look closely, you’ll see merge blocks on the wings in the picture above. Those are ordnance hardpoints. Now there are four potential missile setups currently available (that I know anything about), the gyroscope/custom turret controller method, the (new) AI blocks method, the Whip WHAM method, and the APck method. The APck variant of the Messer T is going to use the APck method, which is something I’ll need extensive testing for. The normal manned variant is going to use either the AI blocks method, or the Whip’s WHAM script, whichever I like more after testing. That same method will also be used on the F2s.

Once the missile system is in place, the F2s will be complete and I’ll know the manned T model will always be compatible with whatever weird ordnance I come up with for the F series. Long story short, standardization in practice.

More to come.