Currently the texture shift functionality of mascomponent ignores range settings, always using 0,1 as the range, which, for example, makes it difficult to implement a fc.SolarPanelOutput() gauge without scaling the variable in a lua script or something.
Might be true for other functions of mascomponent, too.
Currently the texture shift functionality of mascomponent ignores range settings, always using 0,1 as the range, which, for example, makes it difficult to implement a fc.SolarPanelOutput() gauge without scaling the variable in a lua script or something.
Might be true for other functions of mascomponent, too.