Project optimization on extended models (to hide the unused base layers) concerns smart2 inharitance. But still it's offered for smart1. This leads to hidden layers we need (because extended classes are "merged" to the parent).
So this option should not be provided when schema is created with smart1 OR it should optimize the project in a smart1 way (like e.g. set the default value for the t_type field to the extended class).
Project optimization on extended models (to hide the unused base layers) concerns smart2 inharitance. But still it's offered for smart1. This leads to hidden layers we need (because extended classes are "merged" to the parent).
So this option should not be provided when schema is created with smart1 OR it should optimize the project in a smart1 way (like e.g. set the default value for the t_type field to the extended class).