Looks like after installing unity 6 600.0.22 I’ve encountered a couple of regression issues with the stylus input. Stylus input in the editor has, for the most part, worked well in the Unity Editor. It seems broken now as described below.
Also, There were issues in prior unity versions where the BeginScrollRect from EditorGUILayout would randomly return NAN. but that one is bit inconsistent to reproduce so I never documented it.
I’m curious if Unity has any intent on fixing these issues and if there is a time line on resolving them? Item 1 and 2 render the Editor unusable when using a stylus (at least on Mac). switching to a mouse is clunky as I’m often tasking between other Graphical Applications when using unity. Thanks!!
I filed the stylize issue and there is an incident report here ( IN-86354 ). Unity has yet to look at the issue yet so there is no issue tracker filing yet.
The issue’s state is still Open and not Confirmed by Unity. As such, there is no bug filed against the issue yet but this is what I submitted.
Also - did you find a workaround? I ended up installing a mouse and just using both input devices. If the Scene View becomes unresponsive, I just jam on the ‘2D’ view mode button (using the mouse and not the stylus) until responsiveness is regained.
Description:
After Unity regains window focus, the Scene View becomes unresponsive to mouse and pointer input in unity 6.0.X
this is not an issue with abbusive use of EditorApplication.delayCall whch can manfifst the same symtoms
This is a blocking issue that inhibits Mac users from using Unity 6.
The issue can be seen in this video:
Note: In the video, the steps are reproduced several times and we recover from the indeterminate scene view state by pressing the ‘2D’ mode button and repeatedly jamming on various mouse inputs while wiggling the mouse round. Note the mouse clicks are rendered to depict an attempt to engage with the Scene View. During the mouse clicks, the Scene view camera should be changing orientation in accordance to the mouse drag input.
Steps:
From Mac OS device, download unity 6.0.X
create a new project
from the scene view, move the camera around with the mouse or pointer device or create a selection rectangle by dragging the mouse/pointer around
force the Unity Editor to lose focus by mouse/pointer clicking to another window
regain focus for the Unity Editor by mouse/pointer clicking the Unity Editor Window
try dragging around with the mouse/pointer in the scene view.
Observed:
Notice after step 6 the scene view does not respond to mouse/pointer events.
Scrollweheel zoom still works
Pressign a combination of random mouse clicks and toggling ‘2D’ view mode seems to break the Scene view out of the unresponsive state.
Repeating the steps will result in the unresponsive scene view state manifesting
Notes
These results be consistently replicated from the repo steps
Running Mac OSX Sonoma with 5K resolution
This is not the same issue with EditorApplilcation.delayCall as we are using a fresh project and we make no calls to modify EditorApplication.delayCall.