By the way, how did you not explode the rotator when it's spinning at 100??? I usually keep the input like sum(Throttle * 8) and speed at 5. Did you use any mods?
@Dragorans NACAPROP is a type of wing that SP used for prop engines. You can edit it with Overload on the Wings page. There's not a lot of differences between NACAPROP and Symmetric. NACAPROP also produces less force than Symmetric, but it does not stall whatsoever. So it makes the rotor perform better at low speeds.
I assume you are using rotators to spin wing blades. If that's correct, you need to place them in pairs to prevent spinning. Then try to change the wing type to NACAPROP which has better high AOA performance. Also, add a line in the "WIngs" section in Overload specifying liftScale to something like 5 or 10. Hope this helps!
Theoretically you could find every attribute in resources.assets file. In archaic versions that’s where you can change the default setting for parts. I recalled changing the engine output there.
@SnoWFLakE0s I find variables really useful at retaining values! I think my next step is to make a dial input, but I hope SP will someday add the turnable nob button 🙃
@Formula350 I agree. There is a general lack of documentation around more advanced features (say XML). Still, I find this document helpful. But I do not know if it is extensive.
Actually {FTcode} is probably what you mean. It can be inserted anywhere following =. There is something not mentioned though. {FTcode;000} is a way to formulate the output display of numeric values. {FTcode?"Atext":"Btext"} produces strings.
@PlaneFlightX Good point! I'm also pretty busy these days lol. By the way, credits of the original HUD goes to PlanariaLab. I only made a couple of changes and added ILS support.
@TheSeventh So I’ve already made a working sample but just want to learn more about SP physics. I am particularly confused about the aerodynamic effects of a fast spinning wing as well as the rotator itself.
@edensk I do agree with you for the last part, but I do not quite understand how to use smooth to cancel out the last value. However, I just want to point out that the sum function can record a value based on the activation of another group, which means continuing a previous procedure even when disturbed by a sudden input.
@Dragorans check this example. Hope it helps
By the way, how did you not explode the rotator when it's spinning at 100??? I usually keep the input like sum(Throttle * 8) and speed at 5. Did you use any mods?
@Dragorans NACAPROP is a type of wing that SP used for prop engines. You can edit it with Overload on the Wings page. There's not a lot of differences between NACAPROP and Symmetric. NACAPROP also produces less force than Symmetric, but it does not stall whatsoever. So it makes the rotor perform better at low speeds.
I assume you are using rotators to spin wing blades. If that's correct, you need to place them in pairs to prevent spinning. Then try to change the wing type to
NACAPROP
which has better high AOA performance. Also, add a line in the "WIngs" section in Overload specifyingliftScale
to something like 5 or 10. Hope this helps!Theoretically you could find every attribute in resources.assets file. In archaic versions that’s where you can change the default setting for parts. I recalled changing the engine output there.
@SnoWFLakE0s I find variables really useful at retaining values! I think my next step is to make a dial input, but I hope SP will someday add the turnable nob button 🙃
@Formula350 I agree. There is a general lack of documentation around more advanced features (say XML). Still, I find this document helpful. But I do not know if it is extensive.
Actually
{FTcode}
is probably what you mean. It can be inserted anywhere following=
. There is something not mentioned though.{FTcode;000}
is a way to formulate the output display of numeric values.{FTcode?"Atext":"Btext"}
produces strings.@PlaneFlightX
@PlaneFlightX Good point! I'm also pretty busy these days lol. By the way, credits of the original HUD goes to PlanariaLab. I only made a couple of changes and added ILS support.
I should have thought about counter-rotating rotors earlier lol: https://www.simpleplanes.com/a/0yhN7U/Surprisingly-stable-copter
@TheSeventh So I’ve already made a working sample but just want to learn more about SP physics. I am particularly confused about the aerodynamic effects of a fast spinning wing as well as the rotator itself.
@edensk I do agree with you for the last part, but I do not quite understand how to use smooth to cancel out the last value. However, I just want to point out that the sum function can record a value based on the activation of another group, which means continuing a previous procedure even when disturbed by a sudden input.