@Kendog84 It might be that the FT inputs for my variables are also really long so that might be causing it instead
Although it might also be my PC specs
@ReinMcDeer
You're probably right, it's a compromise
Are variables/part variables in general known to make a noticeable difference, (lets say on older mobile devices) though?
I know that at least in some cases, it's better to use variable setter and keep the FT input short than to have long FT on every part that uses the input (having long FT as a custom variable and shorter FT for parts input saves a tiny fraction of loading time, someone on a discord tested that for me (I think on python))
Door (left door in this example) waits for the gear to fully go up or down before it starts moving, and vice versa, regardless of how fast they move. Does not use delay function, pretty simple.
Build link: https://www.simpleplanes.com/a/Eaae6X/Simple-Landing-Gear-Door-FT-delayed-with-IF-argument
@Kendog84 It might be that the FT inputs for my variables are also really long so that might be causing it instead
Although it might also be my PC specs
@ReinMcDeer
You're probably right, it's a compromise
Are variables/part variables in general known to make a noticeable difference, (lets say on older mobile devices) though?
I know that at least in some cases, it's better to use variable setter and keep the FT input short than to have long FT on every part that uses the input (having long FT as a custom variable and shorter FT for parts input saves a tiny fraction of loading time, someone on a discord tested that for me (I think on python))
@weeeeeeeeeeeeeeee
Thanks:)
This is good, but for optimization it would probably be better to use less variables
Or at least for me, variables increase loading times
nice