Closed pampas93 closed 9 months ago
Hi there! Thanks for reporting this issue. Is this issue also reproducible with the BoundsControl component? We are intending on phasing out BoundingBox in favor of BoundsControl, so it would be valuable to know if the issue persists on both components.
@Zee2 I could reproduce the same with BoundsControl as well. Same exact issue.
Thank you. I've brought this up with one of our team members who has been working on BoundsControl, we will investigate this.
@Zee2 @thalbern I was looking into the issue and find the IsValidController function is the reason why they don't work together. However, based on the comments here it seems that it was a deliberate choice rather than a bug. Please let me know what are your thoughts on this.
This issue has been marked as stale by an automated process because it has not had any recent activity. It will be automatically closed in 30 days if no further activity occurs. If this is still an issue please add a new comment with more recent details and repro steps.
We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!
Describe the bug
In a scene with two objects, one with the BoundingBox and the other with a Solver (HandConstraint type), only one behaviour works at an instant. When rotating or scaling, solver stops. And the cursors are not reset as well. After rotating, then scaling, the cursor is messed up.
To reproduce
Steps to reproduce the behavior:
Expected behavior
All behaviours work while rotating or scaling the bounding box
Your setup
Target platform