search

Ylianst / MeshCommander

MeshCommander is a Intel(R) Active Management Technology (Intel(R) AMT) remote management tool. It's feature rich and includes a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and much more. MeshCommander is built on web technologies and runs on many plaforms. In addition to being available as a stand-alone tool, MeshCommander was built to be very space efficient to that it can be uploaded into Intel AMT flash space to have it served diretly from the Intel AMT web serve.
Apache License 2.0
370 stars 80 forks source link

Bad calculation of mouse position in dual screen configuration #32

Open NotCommonUser opened 4 years ago

NotCommonUser commented 4 years ago

Hi! I am using MeshCommander 0.8.8 (installable version running on Windows 10). It is connected to NUC7i5DNHE (BIOS DNKBLi5v.86A.0069.2020.0610.1823, ME v11.8.77). NUC connected to 2 monitors, host running MeshCommander working on single screen. 2020-09-14 When connecting ME lets me select the screen i would like to see, choosing one with F1.

Now the issue is that X position of mouse cursor is wrongly calculated. It looks like the local host position X is translated to virtual position on ME as X*2. I think processing is confused whether it is really working on dual screen (2 times horizontal resolution) or on single screen (local host running MeshCommander).

To add, this happens when host OS is Ubuntu, or Windows 10. Does not happen on BIOS (there i guess there is only one screen activated).

Kind regards, Chris

arinci commented 3 years ago

Hello, I'm having the same issues as explained above. Intel ME version is 11.8.86.3909, chipset is Q170. Problem is bigger in case three displays are connected in "extended desktop" mode. Please note that the issue is not present when "mirror/clone" mode is used in Windows10, in this case each display shows the same image as the other(s). Same situation using RealVNC Viewer, so it seems that the problem is on server side, into Intel ME firmware. With RealVNC the problem disappear switching the pointer to "Relative Pointer Motion", but mouse pointer movement is a bit "jerky" :-).

Do you think that the problem can be fixed on MeshCommander? Or do you think that the problem is related to a bad Intel ME/BIOS implementation of the VNC protocol, server side?

Best regards, Simon