Forum Replies Created
-
Posts
-
Do you have both a Nvidia card and the Intel integrated graphics? Can you try to use a different card for NoMachine in the Nvidia control panel? And which one is in use now?
Just to be clear: nothing is changed regarding hardware decoding in version 6.10. The only change is that hardware decoding is now enabled by default also for large screen resolutions (in https://www.nomachine.com/FR04R03970 you can read about the reasons).
Unfortunately it looks like that some card/drivers combinations are still affected by this problem. For some users updating Intel graphics drivers fixed the issue, but not for all (make sure you reboot the machine after updating, by the way). As far as we know the problem is in the drivers and there it should be fixed.
Unfortunately they’re not complete. There should be a ‘session’ file in the R-* directory that is the actual session log.
Hi,
please gather server side logs as explained in https://www.nomachine.com/AR10K00697. You can attach them here or send to forum[at]nomachine[dot]com. Also show us the output of the ‘xinput’ command.
Please try to update your Intel graphics drivers and check again if hardware decoding works with the new drivers.
Could you send client side logs for inspection? See instructions in https://www.nomachine.com/DT10O00163#2.3. You can attach here or send to forum[at]nomachine[dot]com.
Hi,
the fix is already present in version 6.10.12, but not yet enabled by default, due to a possible (low) impact on performance. To enable it, add this line to the ‘/Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg’ configuration file:
DisplayServerExtraOptions "-yuvgrab 0"Hi,
is the server a headless machine? What is the desktop environment in use?
Logs might be useful (see https://www.nomachine.com/AR10K00697).
Hi,
it could be due to this change:
https://www.nomachine.com/FR04R03970
Client side logs (instructions in https://www.nomachine.com/DT10O00163#2.3) and info about your graphics card and installed drivers would be very useful. Thanks.
New NoMachine version 6.10.12 has been released (fixing https://www.nomachine.com/TR04R09608). Please update and check if the issue is still present.
Hi,
you may try these options in the session menu panel (https://www.nomachine.com/DT10O00156&dn=menu%20panel#5.7):
– choose to ‘Request a specific frame rate’ and select 60 fps
– click to ‘Disable frame buffering on decoding’
Hi Walter,
sorry for delay. At the moment we know that only Nvidia driver versions 4xx are affected and only with some video card models, versions 3xx are not. But it’s still not clear what is triggering the issue. Investigation is ongoing. At the present stage, it looks like NoMachine can cause this behaviour only indirectly and there is no evidence of a problem in our software.
Is ‘Fit to window’ disabled in the Display panel of the session menu?
And can you send a screenshot?
Hi,
those errors mean that it is not possible to allocate shared memory on your system, probably because it is exhausted. To confirm, please run the following commands in a terminal on the Mac at work and send us the output (you can attach here or send to forum[at]nomachine[dot]com):
sudo sysctl -a | grep shmsudo ipcs -maQuickest way to get rid of leftover shared memory segments is to restart the machine.
Hi,
NoMachine automatically adapts to network conditions, so I wouldn’t change many of the default options. In particular I’d leave H.264 as it could leverage hardware encoding and decoding. In the Display settings panel I’d change display quality to max, choose to request 60 frame per second and select ‘Disable frame buffering on decoding’ along with ‘Disable client side image post-processing’. You may also want to disable UDP by clicking to Edit the connection and selecting Advanced settings.