Forum Replies Created
-
AuthorPosts
-
fra81ModeratorHi,
you can tweak the image quality by using the Quality slider in the ‘Display settings’ tab of the toolbar. You can access the toolbar by pressing Ctrl+Alt+0 or by clicking the page peel in the upper right corner of the player window.
You may also try the “Disable network-adaptive display quality” and “Disable multi-pass display encoding” checkboxes in the same tab.
fra81ModeratorHi.
You can use lightweight mode to have pixel-perfect fonts, but only if you are running virtual sessions.It can be enabled in the Server preferences -> Performance tab, accessible by clicking on the “Show the server status” button of the tray icon on the server (or by editing the “AgentLightweightMode” key in the ‘/usr/NX/etc/node.cfg’ file).
As explained by titan in the post above, work is in progress to provide a lossless RGB mode in all types of session.
fra81ModeratorNo functionality will be lost if you disable UDP. It may only affect performance.
These articles can be of interest for you:
fra81ModeratorHave you enabled “Resize remote screen” in the Display settings tab?
This setting will make your remote screen have the same resolution as your player’s window.
Please note that not any resolution will be allowed by your video driver if you are connecting to a physical desktop.
On the contrary, any resolution is allowed if you are running a virtual desktop.
fra81ModeratorDid you enable the lightweight mode as explained here?
fra81ModeratorIt looks like a known problem.
Can you please try the attached library:
1) Open NoMachine Service program, click on “Sever running” and then on “Exit” to shutdown the NoMachine server.
2) Rename the original libnxdimi.dll file in your “C:\Program Files\NoMachine\bin” directory and substitute with the attached one.
3) Open NoMachine Service program again and restart the server.
Attachments:
February 17, 2014 at 14:46 in reply to: Connecting to 4.1 physical desktop resets display frequency #2364
fra81ModeratorWe are already working at the problem with refresh frequency.
Thanks for reporting 😉
fra81ModeratorDoes the /usr/NX/bin/nxplayer.bin executable exist?
Can you try these commands:
# ls -la /usr/NX
# ls -la /usr/NX/bin
# ls -la /usr/NX/lib
fra81ModeratorThe old behaviour can be restored by editing the server.cfg file.
Edit /usr/NX/etc/server.cfg by adding this line:
ConnectPolicy automigrate=0
fra81ModeratorYes, it looks like the graphics card stops working when detaching the monitor.
You can take a look at this article for a way to workaround this problem.
January 10, 2014 at 14:58 in reply to: Connecting 4 client to 4 server on the same machine messes up the GUI #1661
fra81ModeratorThis “mirror” effect is due to the fact that you are connecting from the client to the server running on the same machine. If with version 3.5 you didn’t get this effect it was because you were running a virtual desktop. This functionality is available in the Workstation 4 which is one of the products of the enterprise range. You can get it here in evaluation: https://www.nomachine.com/download/linux&id=13
January 7, 2014 at 19:21 in reply to: Does NoMachine for Windows support displaying individual windows to client? #1601
fra81ModeratorThis functionality is not supported in NoMachine for Windows in version 4.0.369.
On Linux it works in the same way server 3.x worked, from any client OS.
fra81ModeratorWe are not able to reproduce this behaviour.
Can you send us the client and server logs? Submit to issues[at]nomachine.com referencing the topic title in your subject.
Logs can be extracted using the instructions here:
fra81ModeratorUpdate2:
good news, it seems. The latest version of the USB module that is ready but was held in testing doesn’t show this behavior. If you are so kind to contact the support, we’ll send you the sources you can compile (just run “make”) and put in the correct place to test.
fra81ModeratorUpdate:
we tried on multiple Fedora 19 and Ubuntu 13.10 machines and we reproduced the problem on one of them. The description you gave matches 100%. The source of the problem is in the USB kernel module. Unloading it fixes the CPU problem.
Edit /usr/NX/etc/node.cfg and set EnableUSBSharing key to “none”. Restart the server with /usr/NX/bin/nxserver –restart. Please confirm that the workaround works.
-
AuthorPosts
