Forum Replies Created
September 15, 2020 at 16:33 in reply to: Hardware acceleration not working, Mac to remote Windows #29485
as SteveSpaw says. The HDMI dongle would be the way.
do you have a high resolution monitor attached to the Pi (e.g. 4k) and you run the NoMachine player fullscreen or maximized? Does performance depend on the NoMachine window size (i.e. does it get significantly better if you reduce the player window to a smaller size)?
in order to exclude any networking issue, can you try to lower Display quality to the minimum level (slide bar on the leftmost position) and uncheck ‘Disable multi-pass display encoding’? Then I would also try to disable UDP.
Is the server headless? If so, is there any chance you can attach a monitor there and see if anything changes?September 4, 2020 at 15:17 in reply to: Hardware acceleration not working, Mac to remote Windows #29359
what you say about not using the GPU and even more what you see in the Start menu makes me think the Windows box you connect to is headless. Is it the case? If yes, can you try to attach a monitor and see if these symptoms disappear?
Sorry for the delay, I thought i had already replied to this with some comments on the logs. Anyway, in the logs I see that hardware decoding is effectively used. Is the server headless? If yes, can you try to attach a monitor?
do you have the possibility to connect to the same PC from a different client in the same LAN? In this way we could rule out any problem with the Windows machine you connect to and with network.
thanks for the feedback and for the last head up. We think we know the reason and we will be addressing that too.
Thanks for the update.
The issue with the “ghost mouse” is known, it can happen under some circumstances and it will be fixed probably in the next update. The performance problem is not, so I wonder if this can also be related to the drivers. You may try to disable the ‘Use acceleration for display processing’ option in the Server preferences, Performance tab on the machine where you connect to.
If in the meanwhile you would like to send the logs, I’d be glad to take a look.
Let me clarify: the position where application windows are disaplayed doesn’t depend on the NoMachine software, but it is possible that, if NoMachine resizes the remote physical desktop to a lower resolution than the one you use when being physically in front of it, some of the applications remember the previous position and are moved off screen after the resize (this anyway looks like a bug in the window manager that should prevent that). Assuming this is the case, you can try to choose a larger resolution for the remote dekstop (you can find a Resolution slider in the session menu panel), if available.
Does the paid version use a different way of connecting?
NoMachine products from the Terminal Server family (from Workstation on) allows to create multiple virtual desktops, that are independent from the physical desktop of the server and have no constrain about possible resolutions (any screen size is possible). This also means that multiple users can use their own remote desktop independently.July 31, 2020 at 08:50 in reply to: White Screen when connecting from a Windows client #28800
there is one known issue in version 6.11.2 that can cause a white screen:
But to confirm whether it is the same issue or a different unknown one, we would need to see the logs.
are you using the free version of NoMachine (and so you are connecting to the physical display of the server)?
In that case, are you maybe resizing the remote screen when connecting? Note that this can also occur automatically if you have the ‘Resize remote screen’ view mode enabled or ‘Match the client resolution upon connecting’ checked. I would try to avoid any resize and see if that helps.July 28, 2020 at 19:21 in reply to: White Screen when connecting from a Windows client #28740
would you mind to reproduce again and send us the logs (https://www.nomachine.com/DT10O00163#2)?