noone

[noone]

Thank you 😊

[noone]

For me still does not work anything except forums.

[noone]

Hello,

I forgot to mention that I have two displays.

[noone]

Amazing work guys.

Anyway there is still work to be done to improve it.

[noone]

I did notice a huge improvement with the new version, but I was not trying to understand what was changed, as normal human nature, we complain when there is the problem but we do not praise when we get something great like this product.

Today when I saw this post I noticed that in my session i have the H.264 used and session is the same quality with the local screen.

What I can state that software uses now more bandwidth, but with this improvement of session quality it is the small price to pay.

Thank you guys!

[noone]

Thank you for considering my proposal

[noone]

I perfectly understand your point.

About this I am sorry, but i must comment this: 

option was added after evaluating many feedbacks

I am sure this evaluation was done at list 6 years ago when people did not have enough available RAM and screen size like now. Please try to run same evaluation now days.

Thanks
You can close this topic

[noone]

That is clear.
Lets think about the idea that “Resize screen” is not default option, but the option “Match resolution” that is doing wrong behaviour in the window mode. As I said it is OK in the full-screen mode that no person is using.

So or they need to save settings or they need to make new connection and to execute few more clicks as they do not want scroll bars.

Other remote products do not behave like yours.

But if you don’t want to think outside of the box, I gave up.

Thank you

[noone]

The option you’re mentioning is useful if you want to work with fullscreen window.

I am exactly talking about this, but i never sow someone here at the university to start the player in the full screen.

That is why i did propose that that option works like this
– If player is started in the full screen (use full screen resolution to set)
– if player is started in window mode disable that function/ or use window resolution to send.

[noone]

I see that i did not mention, i am using evaluation version of Workstation and virtual desktops. resolution of the real desktop was already sent to the session, but it uses my full size screen to set the resolution.

I propose that you option “Change the server resolution to match the client when i connect” takes NoMachine player window resolution and assigns it to the server, not client’s fullscreen resolution.

Screenshot explains my issue after connection (first resolution on the top is the my current window size resolution)

Attachments:

1. 

   workstation.png
   

2. 

   workstation_1.png
   

[noone]

I have seen problem is related to the default option “Match the client resolution upon connecting” that is always wrong.

For example on client side my NoMachine window size is 1378×764, and my Display size is 1920×1050. In that case with default option enabled NoMachine changes size of my remote desktop to 1920×1050 and not to my window size 1378×754.

I do think it would be better that that option should use player window size rather then the Display size.

thanks

[Author]

Posts