gbelmont22

[gbelmont22]

Ah ha!  Just to follow up my previous posts (again).  After (even more) fooling around with the client I discovered if I set the Display settings to ‘Scale to window’ and then click ‘change settings’ I can enter a custom resolution for the client.  Bingo!

Initially I tried 2880 x 1800 (which is the native resolution of the Retina display), but that produced an overly-small scaled output.  Assuming that I needed to use half of that to compensate for the Retina display, I proceeded to try 1440 x 900, which was too far in the other direction.

In the end, the Goldilocks values seem to be 1728 x 1080 (which is 60% of the native resolution – no idea why – feel free to educate me here!).

I also tried a second client (connecting from the RPi to the Mac), which seemed to work equally well.

So I think, mission accomplished! – although I would continue to welcome any comments or suggestions.

[gbelmont22]

Ok, as usual, 2 minutes after my last post I was able to locate the node.cfg in

/Applications/NoMachine.app/Contents/Frameworks/etc/

I tried adding the DisplayServerExtraOptions key as suggested and the effect was a step in the right direction. The client now renders the top-left corner of the desktop.  The best way I can describe it would be to think of the client as ‘cropping’ the top-left of desktop and scaling it up to fill the entire client window/display area.  This means the right side and bottom of the desktop are completely missing on the client.  However, the mouse tracking is still correct so clicking a menu requires placing the mouse at the ‘true’ position instead of the overly-large ‘rendered’ position.  I tried fooling around with various display options on the client but no joy.  I also tried connecting from two different clients (my Mac Mini and my RPi) both rendered the desktop identically ‘cropped’, which tells me again this is related to how the server is ‘transmitting’ the data.

Still, that was a pretty impressive first try.  I’m open to further suggestions! 🙂

 

[gbelmont22]

Thanks for the reply.  I am currently running Catalina 10.15.7 which is a little behind the times.  I did try some newer versions of macOS installed to a thumb drive, but none of them helped with my underlying GPU problems and so I never progressed any further – so I can’t say if NoMachine behaves any differently on any newer version of macOS.

Now to expose my ignorance, could you kindly direct me to the node.cfg file on Mac?  It’s probably staring me in the face…

[gbelmont22]

Thanks for the suggestion.  Unfortunately, my MacBook Pro is giving me some serious (unrelated) problems, and I am unable to try this to see helps.  If (by some miracle) I get myself back on Terra Firma, I will give this a go.  Thanks again!

[Author]

Posts