ID doesn't play nice with TeamViewer

213 views
Skip to first unread message

V@no

unread,
Aug 24, 2018, 6:11:04 PM8/24/18
to Input Director

Hello.

I've been trying figure out why sometimes when I remotely control my PC via TeamViewer, my computer stops receiving mouse clicks and keyboard from the remote computer.
It turned out that when cursor reach the edge of screen and moves to slave, there is no way bring it back. TeamViewer on remote computer shows it as if it's on master so any mouse clicks and keyboard presses being passed slave computer...blindly...


One of the problems here is that TeamViewer uses "proportional" cursor coordinates, meaning it knows total resolution between all physical monitors and places cursor on slave monitor proportionally based on where it on master, therefor it never be able reach the edge to get back to the master (my master has 2 monitors, but TeamViewer can only see one monitor at the time)

I don't know if ID be able detect when TeamViewer session is active, but I hope this can be resolved somehow..

Thank you.

Shane

unread,
Sep 1, 2018, 11:18:44 PM9/1/18
to Input Director
Hi,

Remote control software can conflict with Input Director (they're both trying to do something similar under the hood). I'll have a look at it when I have an opportunity.

Regs,

Shane.

Scott Copus

unread,
Mar 30, 2019, 11:55:25 AM3/30/19
to Input Director
I'm piggybacking on V@no's comment about TeamViewer compatibility feature request too.  Thanks!

-Scott

Jan Dittrich

unread,
Dec 5, 2019, 12:26:02 AM12/5/19
to Input Director
Hello,

we are also facing this problem regularly. There are some softwares, which are able to detect where inputs such as mouse movements are coming from. For example, Kaspersky is actively "blocking" mouse movements over their windows, if the mouse is moved by an application like input director instead of a physical device.

Maybe with such a technique it could be possible to implement an option, that the master does not switch to the slave if the input to do so comes from an application (e.g. TeamViewer). This solution would be software agnostic and would also work for other remote-control software.

Shane

unread,
Dec 5, 2019, 11:27:53 PM12/5/19
to Input Director
Hi Scott,

Is the compatibility issue occuring when TeamViewer is running alongside Input Director on the master system, the slave system or both?

Thanks,

Shane.
Reply all
Reply to author
Forward
0 new messages