Search Issue Tracker
Fixed
Fixed in 2.5.3, 3.0.0
Votes
1
Found in [Package]
2.5.2
3.0.0-pre.1
Issue ID
XRIT-125
Regression
No
[XRIT] XRUIInputModule does not consider multiple monitors for calculating the mouse position
Steps to reproduce:
1. Open the attached user's project "MultiDisplayUI.zip"
2. Open the scene "MultiDisplayUI"
3. Move one Game View to a second monitor and configure Display 1/2
4. Enter Play Mode
5. Click the Button on the second monitor
Expected Result: Buttons are clicked on their respective Monitor Display
Actual Result: Only the button on the primary monitor (Display 1) is clicked
Reproducible with: XRIT 2.4.0, 2.5.2, 3.0.0-pre.1(2021.3.34f1, 2022.3.18f1, 2023.2.7f1, 2023.3.0b4)
Could not test below XRIT 2.4.0 due to package errors after downgrading
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
The user has provided a fixed package version located in the Packages folder in the root project folder with these changes:
XRUIInputModule.cs (Line#623 m_MouseState.displayIndex = Mouse.current.displayIndex.ReadValue(); )
MouseModel.cs (Line#329 public int displayIndex)
-See forum post:https://forum.unity.com/threads/xruiinputmodule-does-not-consider-multiple-monitors-for-calculating-the-mouse-position.1535155/
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Joint Physics result in unexpected behaviors when used for articulated vehicles like buses or trucks
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts which worked with TMP Font Asset Creator
Resolution Note (fix version 3.0.0):
Fixed an issue in XRUIInputModule where display index was not being set for mouse or touch in the PointerEventData object causing it to always default to the first display. (Fixed in XRI 2.5.3 and forward-ported to 3.0.0)
Resolution Note (fix version 2.5.3):
Fixed an issue in XRUIInputModule where display index was not being set for mouse or touch in the PointerEventData object causing it to always default to the first display.