Search Issue Tracker
Won't Fix
Votes
2
Found in [Package]
0.1.1
Issue ID
UBRMPPM-1
Regression
No
UI Component detection areas are offset in Multiplayer Play Mode players
How to reproduce:
1. Open the “Multiplayer_Play_Cursor_Bug” project
2. Open the “Lobby” scene
3. Open the Multiplayer Play Mode window (Window > Multiplayer Play Mode)
4. Enable “Player 2” (tick the box)
5. Wait for the “Player 2” state to become “Active”
6. Enter Play Mode
7. In “Player 2” Game view, hover the cursor over the “Host” or the “Join” buttons
Expected result: when hovering the cursor directly over buttons, they become highlighted
Actual result: buttons become highlighted when the cursor is hovered slightly above the buttons
Reproduced with: 0.1.0 (2023.1.0b1, 2023.1.0b17), 0.1.1 (2023.1.0b1, 2023.1.0b17)
Not reproduced with: 0.1.0 (2023.2.0a1, 2023.2.0a15), 0.1.1 (2023.2.0a1, 2023.2.0a15)
Could not reproduce with: 0.1.1 (2020.3.48f1, 2021.3.25f1, 2022.2.20f1) (Package is not supported)
Reproduced on: Windows 10 (by reporter), Windows 11
Note: Not reproducible in Player
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This might've been fixed with the latest version of the MPPM package which is currently in its pre-release 1.0.0-pre.2 and the 2023.3.x editor version. If this still persists, open a new bug. Also note, the project had compilation issues, so not able to reproduce it.