Forum Replies Created
Basically, I’ve tried changing settings, etc. on both the client and server-side to try to get the highest performance over LAN, and I can get high performance for a little while, but the frame rate always degrades over time to around 20-25 fps. Not unusable, but also not as good as NoMachine is capable of.
Did you try to disable HW acceleration on HW as I suggested? Because disabling it should in theory get you slower performance, but in practice enabling it can give a ton of problems
If you have it enabled, on the client, it should say: Display 1920×1080, codec H.264 NVENC/VAAPI, audio Opus 22kHZ stereo
If you have it disabled on the client it should say: Display 1920×1080, codec H.264/VAAPI, audio Opus 22kHZ stereo
Another source of slowdown may be Ubuntu’s compositor. I’m not familiar with Gnome’s compositor to suggests tweaks for it. On XFCE you’d go to Window Manager Tweaks -> Compositor -> Enable display compositor (turn it off).
Try using OBS (Open Broadcaster System) and start recording the screen, and see if such slowdown appears after a while (since how OBS and NoMachine capture the display appear to be very similar).
A possible solution for you could be to place multiple NXS files on your desktop that you can double-click to open the session directly.
Ok that’s not a bad idea. Not ideal, but ok
I can understand your point-of-view and I am sorry that you aren’t comfortable with the new design of the UI.
OK, I’m not saying the new method is bad. I can see why people would like this behavior. But it’s not for me.
Then my feedback would be this: Please add a checkbox “Auto close select window on connect” which will automatically close that window, and will be reopened when the connection stops (if not already opened).
This would get people like me a behavior that is close to NoMachine 6’s behavior, and would be good enough.
This may be a silly answer but I noticed some of the rigs you mention (particularly your two Linux boxes) are severely prone to overheating.
Check your sensors to see you’re not just being throttled. For your AMD rig on Ubuntu you’ll need a mainline kernel of 5.11+ otherwise CPU sensor data will show up as 0°C.
If you suspect it’s an adaptive flow control, try literally disabling it (Ctrl+Alt+0 -> Display -> Change Settings -> Modify -> Disable Network-adaptive display quality). There’s also other options you can try tweaking.
Another thing you can try is Toggling HW acceleration server-side
Note: I don’t work for NoMachine, I’m just another user.
That last part about unknown codec rang a bell while I was looking this week through NoMachine knowledge base.
in /usr/NX/etc/node.cfg as described in https://www.nomachine.com/FR04N03097
Done! Check your inbox.
I plugged a monitor into the NV card. I can’t yet make it work on Linux, although that looks more like an incompatibility with the TV I used to hook to the card as I get:
xrandr: Configure crtc 6 failed
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 21 (RRSetCrtcConfig)
Value in failed request: 0x0
Serial number of failed request: 82
Current serial number in output stream: 82
However this let me go a little further with NoMachine, and now everything is still a white/blank screen, only 1 monitor is detected (out of 2, the other one is connected to AMD card) and interestingly NoMachine doesn’t know the resolution and says that the video codec in use is “unknown” (attached pic).
My guess is that it’s clear NoMachine should be using the AMD card (which has a monitor hooked in), but it is selecting the NV one.