Forum Replies Created
-
Posts
-
Hi,
sorry for the delay. I really thought I had already answered!
As one may expect, in the logs I see that NoMachine on your hardware is really capable to produce 60 frames per second, or vey close to that (the second number is fps):
R 17.7/56.4
R 17.4/57.5
R 17.5/57.1
R 17.8/56.2
R 17.3/57.8In particular, I see that around 57 frames per second are produced steadily at least for some time, until congestion (or a significative increase of network latency) is detected on the network:
42417 42970 11:26:53 522.772 DisplayServer/DisplayServer: Received congestion message with level 9.
At that point, as expected, the server decreases the frame rate.
All in all, I really think the reason is to be find in the network conditions, and not in any hardware or algorythmic issue, that seem to be excluded when looking at the logs.
Hi!
Please check if a core file was dumped (usually in the user’s home directory). If you find it, use the instructions here to get a backtrace: https://www.nomachine.com/AR09L00810.
In any case, logs from the server could be useful. Please locate and compress the log directory as explained here: https://www.nomachine.com/AR09L00810.
You can attach the files here or send to forum[at]nomachine[dot]com.
Hi,
we couldn’t reproduce this in a quick test in our labs.
Does the key combination cycle through the Mac windows now? Or it does nothing at all?
Are you able to say at what point it stopped working? After a client or server OS update? After a NoMachine update?
Hello,
for sure your hardware should be able to stream 60 fps without problems! What is your client side hardware and OS? And would you exclude bandwidth problems? For example, does it get any better if you lower the Display quality in the Display settings menu?
Additionally you could send us the logs, so we can search for any hints. For the server side: https://www.nomachine.com/AR10K00697. For client side: https://www.nomachine.com/DT10O00163#2. You can send them to forum[at]nomachine[dot]com.
Hi,
I see in the logs that the Wayland display manager is enabled on your system.
We are actively working on Wayland support. You can be notified when it will be released by applying in the relevant Feature Request:
https://www.nomachine.com/FR10N03221
In the same link, you can find a possible workaround.
Hi fred1,
we’ve never seen anything similar. Indeed log files look zeroed when the freeze occurs. Maybe you could run a sanity check on your hard disk, just to be sure.
Please provide the following information:
1. Gather content of “C:\Windows\Minidump” directory.
2. Export Event Viewer logs:
– Open Control Panel -> System and Security -> Administrative Tools -> Event Viewer
– To export events, select the type of logs you want to export, click on Action menu and pick Save All Events As.
We’re interested in ‘Windows Logs/System’, ‘Windows Logs/Application’ and ‘Application and Services Logs/Hardware Events’ logs.
There is something strange. I see two X server processes running, and one is in failsafe mode.
I would suggest you to reset everything:
systemctl stop lightdm
killall Xorg
killall -9 Xorg
systemctl start lightdm/usr/NX/bin/nxserver –restart
Or reboot the machine… 🙂
Hi!
You may try to disable mDNS broadcasting and discovery in NoMachine.
To disable broadcasting from servers, click on the NoMachine tray icon and unselect Show the service status -> Server preferences -> Services -> Advertise this computer on the network.
To disable discovery on clients, select Player preferences -> Privacy -> Don’t show other computers on the network.
You can change one of those two options at a time. The important thing is that you apply them an all machines of your network.
Hi Fred,
this issue is not known. Could you try to uncheck the ‘Use acceleration for display processing’ checkbox in Server preferences -> Performance tab? You can open Server preferences from the NoMachine tray icon by clicking on ‘Show the service status’, on your Windows 10 machine, before starting the connection.
Hi,
what does the ‘ps -ef | grep X’ command return on the server?
Is it maybe a headless server (no monitor attached)?
Hi Holger,
what NoMachine product are you using? Can I assume that you are running a Virtual Desktop session?
In that case, you may try to disable the ‘X11 vector graphics mode’ on the server, via the Performance tab in the ‘Server preferences’ UI or by changing the AgentX11VectorGraphics key in ‘/usr/NX/etc/node.cfg’. That mode is specifically optimized for multimedia content.
In any case, I would check if H.264 encoding is being used. You can check that in the session menu of your NoMachine Player, at the botton of ‘Display settings’ menu.
Hi Ve0,
did you try to verify the network bandwidth actually available, and latency as I suggested above?
I see that the editor modified also my marks, but I think you got the point 🙂
Alternatively, libraries can be copied to the proper folder by hand.
I’m going to answer in any case, as this might be useful for someone else.
$ ./configure –disable-cli –enable-shared –disable-avs –disable-swscale –disable-lavf –disable-ffms –disable-gpac –libdir=”C:\Program Files (x86)\NoMachine\bin”
I don’t know if you just copied and pasted here the actual command. In that case, the reason could be the use of quotation marks ”” instead of “”. Or you can try with apostrophes ‘ ‘.