Discovered during the conversion of ASET_HUD to MAS.
If a MODEL_SCALE is used to make some components disappear (using startScale = 0, 0, 0 and endScale = -1, -1, -1, it can affect other components that are initialized later. This happens because during initialization, the variable callback is triggered, and the transformation scale is applied before other parts initialize.
Turns out that using a coroutine to delay applying the scale and registering the callback until the first FixedUpdate after configuration does the trick.
Discovered during the conversion of ASET_HUD to MAS.
If a MODEL_SCALE is used to make some components disappear (using
startScale = 0, 0, 0
andendScale = -1, -1, -1
, it can affect other components that are initialized later. This happens because during initialization, the variable callback is triggered, and the transformation scale is applied before other parts initialize.I have not thought of a solution yet.