Forum Replies Created
-
Posts
-
Hi,
for a start, you can try to disable hardware decoding, by checking the box in the session menu:
https://www.nomachine.com/DT07M00087#5.7
and hardware encoding, by uncommenting and changing the relevant key in the <installation directory>/etc/node.cfg file:
EnableHardwareEncoding 0
Hi gabriele,
can you specify the driver version? If possible, send us the logs as explained in my post above.
And does disabling ‘client side hardware decoding’ fix the problem also in your case?
The problem is, that all opened windows on display “1” (programs, terminals, etc…) opens in display “0” (I see it in task manager), except NoMachine client and server windows, they are opens normally. So, what am I doing wrong? And how fix it?
I assume that both desktops are owned by the same system user. In that case, how the display to connect to is chosen depends on the application. What you can do is starting the second desktop as a different user. Not sure if you can configure those applications to behave differently.
Hi,
we are aware of the issue which is due to incorrect info reported by the X RandR extension on some headless machines. Besides the workarounds you already mentioned, you can use also this one: https://www.nomachine.com/AR03P00973.
If you’d like to receive a patched version to test, please write to forum[at]nomachine[dot]com.
Hi,
are you aware of any video drivers update on your system? What’s your graphics card model and driver version?
Please also send client side logs, gathered while reproducing the green screen problem. You can extract them as explained in https://www.nomachine.com/DT10O00163#2 and send to forum[at]nomachine[dot]com.
Hi Mehmet,
you can try to disable hardware encoding instead of disabling H.264 altogether. To do that, uncomment and disable the EnableHardwareEncoding key in the ‘C:\Program Files (x86)\NoMachine\etc\node.cfg’ file, then restart NoMachine server:
EnableHardwareEncoding 0
Please also send logs for further investigation, as explained in https://www.nomachine.com/AR10K00697.
Hi,
thanks for letting us know that the product is working well.
About the noticed “motion sickness”, let me point out that, from a technical standpoint, any “lack of synchronization” is unlikely due to the way NoMachine handles the mouse movements. Mouse movements, in fact, are handled locally and displayed immediately, as they happen, on the client side. In other words, what you see moving on screen, is the local cursor and not the remote one. On the other hand, it’s true, that to see the response of the graphical environment (for example an icon becoming highlighted after a mouse click) the mouse event must reach the remote server, the graphical output encoded, sent and displayed by the client, so that the response can be actually “delayed”, depending on the network latency or the speed of the involved machines. Unfortunately there is very little we can do to avoid this. To better check the latency that exists between the mouse movement and the speed of the server to reflect the change, you can enable showing the remote cursor as it is processed by the server. You can find this option in the Input preferences panel. Such option is turned off in the default settings.
Hi,
this is not possible at the moment. Part of the reasons are technical: the only consistent way to implement blanking across all platforms is by turning off video output completely, thus it is not possible to show a prompt on the physical screen, especially one that would not be seen also on the connecting client. Note that you can regain control over the machine at any time by connecting from any other computer or device at your disposal, including mobile devices, thanks to NoMachine client for iOS and Android.
With the last update, H.264 encoder is now available by default in all NoMachine products, free ones included, so it is not possible to exclude that some new problem could be found when hardware encoding or decoding is in use with specific graphics cards or drivers, since, as you can imagine, it is not possible to test every possible combination of hardware, drivers and configurations in our labs.
Can you confirm you had tried to check the ‘Disable client side hardware decoding’ box?
And could you send us the session logs so we can investigate further? You can gather server side logs as explained in https://www.nomachine.com/AR10K00697 and client side logs as in https://www.nomachine.com/DT10O00163#2. You can send the files to forum[at]nomachine[dot]com.
Also a screenshot showing the issue could be useful.
Hi.
Strange. There is no such “error” in the NoMachine code and I honestly don’t understand how it could have been generated and make the session fail.
Could you take a screenshot of that error?
Please also provide more info on the operating system and the NoMachine product installed.
Hi,
I assume you have a Retina display on your Macbook and so it could depend on the scaling settings of the display. Could you attach a screenshot of your Display system preferences?
Hi,
isn’t just disabling ‘Fit to window’ doing what you want? If that’s not the case, could you explain further what behaviour you would like to achieve?
Yes, indeed.
In general, when streaming a Windows desktop, RDP has access to the internal OS graphics primitives. But this doesn’t occur when streaming the NoMachine session, whose content is a Linux screen that is rendered remotely.
RDP is not able to stream this type of content as efficiently, so it’s not a NoMachine problem. This is a performance issue that must be solved in RDP.
Yes, getting the dongle should be the easiest solution to have GPU acceleration, but probably you are good to go with the llvmpipe solution, so I’d suggest to wait for your user 😉
Hi,
I think this Feature Request describes what you need:
https://www.nomachine.com/FR12K02799
Check the box to be notified when implemented 😉