You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
like title said. ill just run down my set up then difference in-between stable and lazer its a very minor issue
open tablet driver installed and opened (screenshot 1)
2 monitor setup monitor 1 on left 2 on right, 2 is the main monitor (screenshot 2)
when opening stable with my area mapped to my second monitor it works perfectly fine no issues but when switching to lazer curser will hug the right side of the screen until i switch the area in open tab driver to monitor 1.
it was working perfectly fine originally but what i think broke it was when i accidently hit f11 it switch mapping to monitor 1 some how
what i think happened
i got monitor 2 yesterday and lazer might have stayed mapped to display 1 but since i set display 2 as my main monitor it opened on monitor 2. making it work until i hit f11 causing it to switch tracking back 2 1
Type
Game behaviour
Bug description
like title said. ill just run down my set up then difference in-between stable and lazer its a very minor issue
open tablet driver installed and opened (screenshot 1)
2 monitor setup monitor 1 on left 2 on right, 2 is the main monitor (screenshot 2)
when opening stable with my area mapped to my second monitor it works perfectly fine no issues but when switching to lazer curser will hug the right side of the screen until i switch the area in open tab driver to monitor 1.
it was working perfectly fine originally but what i think broke it was when i accidently hit f11 it switch mapping to monitor 1 some how
what i think happened
i got monitor 2 yesterday and lazer might have stayed mapped to display 1 but since i set display 2 as my main monitor it opened on monitor 2. making it work until i hit f11 causing it to switch tracking back 2 1
Screenshots or videos
Version
2024.1208.0
Logs
compressed-logs.zip
The text was updated successfully, but these errors were encountered: