The issue is the same on physical Windows machines and VMs. There is also no difference in behavior using different zoom factors (adaptive or fixed scaling). On client side there is many-many variations, no difference in behavior depending on resolution. I'm using self hosted rustdesk-server 1.1.7-1 (not relevant, the problem also remains using the official tell us more about your monitors plese, resolution and zoom factor etc. So something might be wrong with the Windows client side 1.2.0, while 1.1.9 is working properly. Windows 10 control -> Windows 11, 10, 7 clientsġ.2.0 -> 1.1.9 OK Linux Mint control -> Windows 11, 10, 7 clientsġ.2.0 -> 1.1.9 OK Windows 11, 10 control -> Linux Mint client Because of my work I've tested it on many-many Windows clients, and 1.2.0 on the client side is unusable. Or you have to click again to release a drag-and drop action. You have to move the mouse a little bit at the same position to put the client mouse pointer to the right place. It's not a lag, because if you wait for a longer period of time without moving the mouse, the mouse pointer won't be at the right place, the context menu will show up at the same wrong place (or it won't pop-up because the client doesn't get the click action at all), so the pointer just stays at some previous wrong position forever. You will see that the context menu will show up at a totally different place than it should be. You can test it well by randomly right clicking on the desktop. The client side mouse pointer does not follow the control side movement and the clicks. I also have this issue using 1.2.0 client on all supported Windows versions. MacOS Ventura Intel > macOS Ventura M1 RustDesk Version(s) on local side and remote sideġ.2.0 -> 1.2.0 Screenshots IMG_1528.MP4 IMG_1527.MP4 Additional Context Operating system(s) on local side and remote side The expected behaviour is that the mouse click will be released according to the local mouse click, or at least, a timeout implemented. The expected behaviour is that the mouse of the remote computer will follow the local computer at all times when the mouse cursor is inside the window of the remote computer. The drag does not get released even when clicking on other stuff in the local computer or the RustDesk application window and must be released with repeated clicking. Sometimes, click and drag will get stuck, and releasing the mouse button does not release it on the remote computer. Play a video to show the connection is continuous. To reproduce, do some dragging of a window in the session around. Notice that in some cases, the remote cursor no longer follows the local cursor, until you move the cursor a bunch, then it catches up. Play a video on the remote computer to show that the video is continuous and smooth. Sometimes, the mouse is jumpy, but the mouse generally follows the client. Connect to the remote machine, preferably over the Internet, and move the mouse in circles. To reproduce, first enable "show remote cursor" to make the cursor more visible. The mouse will get stuck on the "click and hold/drag" mode.The connection is successful, between macOS Ventura and Ventura machines (M1 host, intel client) but there are two problems with the mouse: I was able to create a work around by setting the local computer user profile to match the Windows Black - extra large cursor size so when it does flip between the two cursor settings (remote and local) it will behave as we would like to the user to see.I am using the latest nightlies of RustDesk as of the creation of this post. Is this a known bug or issue and if so can someone let me know what Windows CU update will correct this behavior. So basically i can confirm that the remote session does know that the Xlarge black cursors pointer settings is correct, however moving between displays/ applications the cursor will change to the local computer cursor settings. We are noticing that when logged into a RDP session, mouse cursor pointers that are set in the remote server windows user profile (set to Windows Black - extra large) are changing back and forth to the cursor pointers on the local Windows 10 machine (default small grey pointers) where the RDP was initiated from. We have work computers (Windows 10 Ent LTSC 2019 / Windows 10 build 1809) that have multiple displays connected that primarily RDP into RDS servers (Windows 2019 STD LTSC).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |