 |
Forum discussion: https://forums.thedarkmod.com/index.php?/topic/21239-can-only-rotate-on-axes-now/#comment-468750 |
 |
Unfortunately I have to unassign this one since I do not have the mathematical knowledge to fix it. I have established that the call to Circle_BestPoint() in RotateManipulator::testSelect() is returning an invalid intersection regardless of the mouse click position, which results in the _circleSphere never being a candidate for selection even if none of the other manipulator elements were clicked on. However the maths code in Circle_BestPoint() and its callees is beyond my ability to understand or effectively debug. |
|
|
I did a Git Bisect which revealed that this is the commit which introduced the problem. This seems to relate only to render so it is not clear how it affects selection, unless it's just a mismatch between the rendered point positions and what the selection system is testing for. The commit does not touch Circle_BestPoint() at all so it does not appear there is any problem with the maths in this function. === commit 26ab05dffc5380e066251b278d3c196222c56492 (refs/bisect/bad) Author: codereader <greebo@angua.at> Date: Wed Oct 13 10:49:55 2021 +0200 0005733: Compensate the view's projection aspect ratio when rendering the rotate manipulator === |
 |
@OrbWeaver: thanks for spending the time on the bisect. The triangle winding order has most likely been changed in the commit you tracked down. |
- Anonymous
