Local cursor for remote connections to Mac

Forums / NoMachine for Mac / Local cursor for remote connections to Mac

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #33328

    I swear this was OK the other day (was doing work in Logic Pro X and it would have driven me mental).. So I believe something has changed, and I can’t seem to change it back..

    When connecting to my MacBook Pro through NoMachine I configure it to scale the remote resolution and display full screen, using SwitchResX I configure the MacBook to be 3440 x 1440 (it works fine it just gets framed on the native 2880 x 1800 display of the MacBook), and I connect from a Windows machine which has a wide screen monitor which is native 3440 x 1440.

    Effectively I get full native resolution of my Windows monitor for the full screen remote session in NoMachine.

    As stated this was working just perfectly, however now the local pointer is a massive hand which floats over the remote pointer.

    I found a few forum articles about the local/remote pointer but nothing that helps with this, I don’t mind the two pointers (better if I could just turn the local one off), but it would be nice if the local one was just an arrow like the remote one and the same size, if it must be a hand – also the same size as the arrow, not huge.

    The massive hand only appears when you’re actually working with the remote desktop, if you use the page curl to get into NoMachine settings it goes away, it’s only there when interacting on the remote desktop and you see the local and remote mouse pointers (almost) in sync.

    I have attached some screenshots to illustrate – ignore the hand’s shadow, I was moving it so you could see the hand and the arrow and somehow the phone camera created a ghost hand, the others put the size of the hand into perspective next to normal screen text and on top of the remote arrow.

    Any insight into this would be greatly appreciated.

    Both local and remote versions were updated to see if that fixed anything so currently running NoMachine (Windows 7.4.1, Mac 6.14.1), OS are Windows 10 Pro (latest feature release), Mac OS X 10.12.6, the Mac is not running headless (it’s a MacBook Pro) as with some pointer related issues already mentioned in the forum.


    I have no idea why this changed again.. At least I know I’m not going crazy..

    This remote cursor is now only a single remote normal size arrow! (happy days! for now..)

    Screenshots attached, one not moving, other circling the mouse and thus the repeats and ghost pointer, and comparison Finder shot.

    I did have some issues with my Windows machine and network interface – but I would think that totally un-related to NoMachine (it did include several restarts of Windows – the MacBook has not been restarted since my original post).

    If anyone can shed some light on this in case it reverts to having the “huge hand pointer” as well as the remote arrow – it would be nice to know why it happens and how to stop it! 🙂


    Hi Nyquist,

    we can’t reproduce this issue in our labs and we didn’t receive similar reports. Should it happen again, please let us know, possibly with the steps to reproduce.


    It happened again – only this time it was a huge cursor not hand over the small/normal cursor.

    If anyone else happens across this it turns out it may be very simple.. I was running OBS Studio on the MacBook Pro before I remote connected with NoMachine.

    After connecting and getting the huge cursor, if I quit OBS everything goes back to normal – just one small/normal cursor!

    If I re-launch OBS (while remotely connected with NoMachine and the full screen 3440×1440 as described above), I get a secondary cursor but they are both the same small/normal size.

    Another couple of screen shots attached – 1st single cursor (OBS not open), 2nd two cursors (OBS re-launched after NoMachine connection – I was moving the mouse as they don’t track exactly the same but very close).

    So it’s workable if OBS must be running for any reason – you just need to quit and re-launch after the NoMachine session is established.

    I hope this is useful if anyone else every comes across this – easy once you know the solution – very frustrating when you don’t!

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.