I've had sporadic issues with RDM, where when I have it open it will capture and aggressively hold on to the mouse - so much that when RDM is open I am unable to click on other windows. Close RDM and everything returns to normal. Is this a known issue, or is there a setting I have turned on (or set to too aggressive)?
Hello,
Thank you for reaching out to Devolutions Support.
This is not an issue we commonly encounter, so I would like to gather a bit more information to better understand the behaviour you are seeing.
Could you please confirm whether this mouse capture issue occurs:
This will help us determine whether the behaviour is related to the application itself or to a specific session type or configuration.
If the issue is caused by a misconfiguration, resetting Remote Desktop Manager to its default settings may resolve the problem. You can follow the steps in the documentation below to do so:
https://docs.devolutions.net/rdm/kb/how-to-articles/reset-rdm-to-default-settings/
Please let us know the results and any additional details you can provide, and we’ll be happy to continue assisting you.
Best regards,
Carl Marien
Unfortunately it's sporadic - I don't notice it when I open initially, only after time; I tend to only have RDM, Edge and VirtualBox open at any given time, but closing RDM seems to resolve it (although sometimes it can be stuck tabs in Edge as well).
This is a fresh install of RDM on a fresh install of Windows (but I have noticed the same behavior across multiple workstations).
Hello,
Thanks for the update.
Could you please let us know:
In some cases, mouse drivers or vendor utilities can affect how applications capture mouse input, especially with virtual or remote sessions.
Best regards.
Carl Marien
I'm using a Logitech G502 Hero, with no custom settings (other than it's managed by Logitech's G software).
Hello,
This might be a shot in the dark, but would it be possible for you to try connecting a different mouse to your PC and let us know if the issue persists?
While we haven't been able to reproduce the issue on our end using another mouse with Logitech’s G software, it's possible that this could help isolate the problem.
Best regards,
Carl Marien