Forum Replies Created
-
Posts
-
Hi,
please send us NoMachine log files and X.org configuration:
sudo tar zcf NoMachine.log.tar.gz /usr/NX/var/log
sudo tar zcf Xorg.log.tar.gz /var/log/Xorg.*
sudo tar zcf xorg.conf.tar.gz /etc/X11/xorg.*
And your graphics card model:
sudo lshw -C display
You can send the files to forum[at]nomachine[dot]com.
That should already happen, unless you hit a bug or some corner case. What I had supposed is that those windows were originally rendered with “vector graphics” and then compressed as an image upon reconnection (as it can be necessary due to the stateless nature of X11 protocol). And that would be the reason why you see a difference. Can you send a screenshot of the NoMachine window showing the issue and of your Display settings?
Hi!
1. The AVC pack will help for sure.
2. NoMachine will adapt automatically to network conditions to achieve best performance possible. Just use the Display quality slider (that you can see in the session menu – Display settings tab) to find the best trade-off between quality and speed that works for you. You can leave other settings to the defaults. Consider that of course also screen resolution will affect used bandwidth.
Hi,
keyboard layout is reset at reconnection accordingly to the client side layout. However NoMachine offers the possibility to run custom scripts that will be triggered on specific events, so you can add your xmodmap command to the UserScriptAfterSessionReconnect script in /usr/NX/node.cfg. You can find more info in https://www.nomachine.com/DT04O00139#11.6 and some examples in https://www.nomachine.com/AR02L00787.
Regarding pixelation and colors issue at reconnection, what you see is probably the effect of jpeg compression. If I understand correctly, you’re running custom sessions in floating window mode that use the ‘X11 vector graphics mode’. Being X11 protocol stateless, it may happen that at reconnection windows are redrawn using compressed image instead of vector graphics. Increasing display quality could be enough, or you can try to set a lossless compression method. For example, edit /usr/NX/etc/node.cfg by adding this line:
ProxyExtraOptions pack=16m-png
As for your second question, H.264 will be supported soon also on iOS devices:
https://www.nomachine.com/FR12M02992
One thing you could try is checking “Disable client side image post-processing” (https://www.nomachine.com/it/DT10O00157#5.7). You may also attach session statistics here for inspection (https://www.nomachine.com/it/DT10O00157#9).
It doesn’t depend on NoMachine. The same problem can be found when connecting from any remote access tool. You can see other users with the same issue here:
https://serverfault.com/questions/815775/google-compute-engine-vm-display-driver
https://serverfault.com/questions/817910/installing-a-virtual-graphics-adapter-on-a-windows-server
https://productforums.google.com/forum/#!msg/chrome/IPZFTPihzWA/ZEzq0ZWeBwAJThe fact is that without a display adapter, no rendering can even happen on the server. The exception is RDP, but only because it creates a virtual session – it doesn’t connect to the physical display.
However, it seems that now Google Cloud makes available instances with a GPU (at least in beta, as far as I can see). You may want to check that here: https://cloud.google.com/gpu/.
Thank you for all the info!
Naturally file transfer bandwidth has to be limited in a way that it doesn’t slow down the streaming of the session, but definitely what you describe doesn’t look as the correct behaviour. We will test your setup deeply in our labs.
You’re welcome!
Maybe NoMachine could display the frames information in the stream window, in one of the corners, as an option (printing it in real time).
That’s a great idea and it is present in the Feature Request we opened:
https://www.nomachine.com/FR09P03680
The file transfers between these computers reached 100mb/s through Windows, but when using NoMachine, the file transfer ranged from 300kb/s to 3mb/s
Do you confirm that you are referring to NoMachine’s file transfer service (that wouldn’t use all the available bandwidth)? Or you mean instead the streaming of the NoMachine session?
So, it could be a client-side option between showing “black margins” (simulating the 4:3 resolution on the server-side) or leaving the image stretched.
1:1 mode should be the default! Please check in the Display panel in the session menu that ‘Fit to window’ is not selected. You can also use the quick icons at the bottom of the menu to switch between display modes.
Hi Belez,
printing in the logs what is the programmatic framerate selected by the server, according to network conditions and such, seems to be something definitely missing. We’ll add it to the logs of the client, as well as when, for any reason, the programmatic framerate changes during the session. The achieved framerate, then, can be different. We’ll add it as well, but the best way to measure it is certainly by an external tool, like Fraps. As I stated, we ignore why Fraps fails to detect it. You should ask the Fraps developers. Anyway having the framerate measured by the client will be a good starting point.
I mean, i can use fraps and similar software on Steam and Splashtop streams to measure client-side FPS (and it is different from server-side), but i can’t do the same with NoMachine client-side.
Well, it’s difficult to say because we should know the exact way Fraps “gets” that a new frame is output… You should try to contact the Fraps developer and try to shed some light. Of course there may be some optimizations we have worked on that Fraps doesn’t expect… We may also explain in detailed way all those optimizations, but you will agree that it’s in our interest to keep some spice secret. 😉
Dear dd0044, this specific game seems to have a problem causing this specific issue.
It can still be a problem with NoMachine, of course, but it is absolutely advisable to first try the patch and then verify if it’s actually so.
We strongly invite you to do your best to install the game’s patch, possibly with the help of the game’s publisher, otherwise it will be difficult for us to investigate the problem without a well-specific starting point.
It’s a bug. There is a specific executable, nxdock, that is not signed. We investigated this and it seems that the bug was introduced in version 6.0.62, when we lastly upgraded the Mac build environment. We’ll fix it in the next release. Just to make things clear, the Mac and Windows packages are fully signed, as signed are all the libraries and all the executables (except those that, by mistake, got out of the procedure). We’ll fix this shortly and update the post-production unit tests.
Hi Bruce,
we’re not able to reproduce this behaviour in our labs at the moment. We are preparing a debug package to investigate on what’s going on on your Mac, if you’re willing to test it.
Unfortunately NoMachine insists on using QuickSync rather than VAAPI and the former is notoriously difficult to get working without applying a lot of hacks whereas the latter covers multiple GPU types and should “just work”.
Just to say that we started this in 2014. At that time VAAPI was not as mature and it didn’t even support the encoding side.
But now, finally, VAAPI starts to yield some results, and it is widely supported. Also considering the huge mess distributions make with Intel drivers, Intel Media SDK and the tweaking necessary to make QuickSync work, we are finally readying the VAAPI implementation.