[1.193.103] Rotor limits and clang
Outdated
Build a battery, rotor, and attach a structure from the rotating part. Set the rotor's velocity, minimum angle and maximum angles to positive values.
Slide the maximum angle back and forth and observe the rotor's behavior.
Result: The rotor will make sudden backwards adjustments. The rotor being near 0 degrees, rotating slowly, or rotating a structure with subgrids, can contribute to the violence of these adjustments.
Expected result: The rotor will stop or continue rotating at the desired speed when outside the limit.
I have the same bug
Hello, Engineer!
Thank you for your feedback! Your topic has been added between considered issues.
Please keep voting for the issue as it will help us to identify the most serious bugs.
We really appreciate your patience.
Kind Regards
Keen Software House: QA Department
Hello, Engineer!
Thank you for your feedback! Your topic has been added between considered issues.
Please keep voting for the issue as it will help us to identify the most serious bugs.
We really appreciate your patience.
Kind Regards
Keen Software House: QA Department
This shouldn't be outdated because it is still a problem and cause for massive clang. The problem is basically, if you change your rotor limits so that the current angle of the rotor falls outside those limits, the rotor will automatically move to set itself within those limits with an unholy amount of torque. Because of that huge torque, if the rotor is carrying some mass on it, it will pick up too big of a momentum to get itself to stop at the new limit and it will overshoot. So all you have to do is make your current angle fall outside the limit by a few degrees and you'll get a massive swing of the rotor with some serious clang. Setting rotor limits that makes your current angle violate those limits should either not be allowed (should display a warning and not do anything on its own) or if the rotor attempts to set itself within the new limits it should do it with a torque/speed cap so as to avoid clang. I'd personally prefer the former...
This shouldn't be outdated because it is still a problem and cause for massive clang. The problem is basically, if you change your rotor limits so that the current angle of the rotor falls outside those limits, the rotor will automatically move to set itself within those limits with an unholy amount of torque. Because of that huge torque, if the rotor is carrying some mass on it, it will pick up too big of a momentum to get itself to stop at the new limit and it will overshoot. So all you have to do is make your current angle fall outside the limit by a few degrees and you'll get a massive swing of the rotor with some serious clang. Setting rotor limits that makes your current angle violate those limits should either not be allowed (should display a warning and not do anything on its own) or if the rotor attempts to set itself within the new limits it should do it with a torque/speed cap so as to avoid clang. I'd personally prefer the former...
Hello, Engineers!
This has now been reproduced in this thread here :) https://support.keenswh.com/spaceengineers/pc/topic/rotors-min-and-max-limit
Kind Regards
Laura, QA Department
Hello, Engineers!
This has now been reproduced in this thread here :) https://support.keenswh.com/spaceengineers/pc/topic/rotors-min-and-max-limit
Kind Regards
Laura, QA Department
Replies have been locked on this page!