June 10, 2020 at 08:58 #28069
I have reported this issue a few times now (science October 2019):
I was subsequently provided with a fix that I beta-tested. I was able to confirm it helped the situation (although didn’t completely solve it) and it was supposed to put into the next version (6.9.2). However, when 6.9.2 came out I complained that the issue was still there. Turned out that the fix wasn’t put into 6.9.2 (due to an oversight) and I was told to wait for the next version. Well, with 6.10.12 out now it’s still having exactly the same issue. Did the fix not make it into the current version yet again?June 15, 2020 at 15:51 #28127bucuContributor
the fix made it into the current version however it was tuned for better user experience. We would like to send you a debug package with that tuning reverted to see if it helps with your case. If you are interested please let us know and we will contact you via email.June 16, 2020 at 10:08 #28130
Yes please – I’m desperate for this to be fixed.June 18, 2020 at 16:42 #28185
Can you please confirm if you have my email address, otherwise I will post it here (unless you provide an address so I can email you instead).June 18, 2020 at 16:44 #28190
Mick, we will send it to the email address associated with your forum account. Can you confirm what version you are using? 6.10 or 6.11?June 19, 2020 at 05:11 #28199
6.11.2June 24, 2020 at 13:23 #28255
Please can I have this fix! This issue is just killing me.June 26, 2020 at 14:13 #28308
Check your inbox!July 2, 2020 at 09:11 #28381
We’ve viewed the video you sent via email and observed the behaviour which occurs when a sharp move of the finger on the magic mouse within the window causes the content of the window to reload slowly instead of scrolling up or down. (Note for new readers of this topic: when moving the finger on the mouse slowly within the window or in the actual scroll area at the side of the window NoMachine is responsive and content is rendered correctly).
At this point, we need to see debug logs because we need to see what’s being registered by NoMachine when you’re encountering the issue. So, please enable debug on both the Mac client and Linux Workstation host. Reproduce the problem and then send them to the usual email address. For instructions on how to enable debug, please follow this link:July 8, 2020 at 09:04 #28452
Would you try -defercore in DisplayServerExtraOptions (node.cfg)?
Does the issue occur in virtual desktop as well as in rootless mode?July 9, 2020 at 14:29 #28455
I just tried that – took me a while to figure everything out. Was this a server side or client side instruction? Where is node.cfg located? Anyway, assuming it was a client side thing, I tried it on my Mac after finally finding the file in:
I edited the file as below:
#DisplayServerExtraOptions “-nocomposite -noshpix”
but nothing changed. I then had our CAD guy edit the server side file on the linux (actually Centos) machine in the same way and then I did see a difference. It did display the same constantly redrawing bug when I swipe fast on the Magic Mouse as in the video, only this time many of the redraws were implemented as screen over-writes (see attached picture). So I’d have to say things got worse because of the added poor visual effects. I also tried it with the node.cfg file back to normal on the Mac while the edits were still in effect on the server and experienced the same overwriting visual effects. So in summary, changes were only noticed when the server side file was edited. I forgot to check it with a virtual desktop and when I remembered the CAD guy had already left. That being said, if I have to view the remote desktop instead of the individual windows then I immediately jump to VNC where I’ve never had any problems. The *only* reason I use NoMachine is because of the capability of displaying individual remote windows back onto my Mac.
Attachments:July 9, 2020 at 14:51 #28462
All the interventions so far have been for the remote Workstation installation, the Linux server. So there is no need to alter anything on the Mac client.
Please try the virtual desktop anyway: we need to know how it works with no modifications to node.cfg (so you don’t need to ask the CAD guy). To be clear, I’m not asking you to abandon single application mode to embrace virtual desktop: I’d just like to know if the problem only affects single application mode or is more general.
If I got it right, the CAD you are using is Cadence Virtuoso. I’ve get access to a Virtuoso installation: if you tell me where to find in Virtuoso that window exhibiting the scroll issue, I’ll try to reproduce the problem on my own.July 9, 2020 at 14:53 #28464
You mention a “CAD guy”, I assume that’s the administrator in control of the NoMachine server, so I assume that you are not in control of the remote server. If that’s the case and if that Linux server is running a subscription from NoMachine, it’s better if the administrator opens a ticket with the NoMachine support team. He would then be able to follow our instructions.July 13, 2020 at 08:47 #28497
I did try the virtual desktop and do not see the problem at all.July 14, 2020 at 13:44 #28513
I did try the virtual desktop and do not see the problem at all.
This is interesting.
It would help a lot if we could reproduce in labs. Would you tell me how to reproduce it using Cadence Virtuoso?
- This topic has 21 replies, 4 voices, and was last updated 3 months ago by .
Viewing 15 posts - 1 through 15 (of 22 total)
Viewing 15 posts - 1 through 15 (of 22 total)