MicrosoftI feel like this could be user error on my part but I'm not sure. I have a 4K monitor and on v2.93 I'd connect to remote systems with a 1920x1080 resolution and it was actually upscaled a bit in the undocked or docked view, so it didn't seem tiny. All I did was upgrade to v3.01 and using the same settings, it still connects at the 1920x1080 that it used to, but now it's "appropriately" scaled 1:1 and just appears really tiny on my 4K monitor. If I switch back to v2.93 it's okay again (in my case it's about 2878x1614 in actual size, scaling up my 1920x1080 client).
I don't recall doing anything in particular on the old version to have it scale up for me but I set that all up so long ago, I'm not sure.
The client settings I have for v2.93 for this client are "no scaling" for both docked and undocked under "Display Settings", and a 1920x1080 custom size in "Remote Desktop Settings".
On v3.01 it's the same but has the added "DPI scaling" option which defaults to "As Host". When I tried changing that to something else it just changes the scaling on the remote system, which isn't what I want (I want that left at 100%). I don't know if v3.x simply no longer scales the actual display up like it used to?
I could fiddle with it and scale up with that new option and connect at a higher resolution, but then things can be a little weird if I'm connecting locally and then remotely where things aren't consistent.
I realized that the difference in the 1920x1080 of the actual client and the way it's scaled up for display on my 4K monitor (up to about 2878x1614 or whatever, which was an approximation) is 150%. That's the scaling factor I have on my 4K display, so I think RDCMan 2.93 is scaling up the connection by the scaling factor I have set.
In v3.01 it's not doing any kind of scaling of the actual connection, and if I were to change the scaling factor in the properties of a connection, that's only changing the display scaling of the *remote* system which means I'm still getting a 1920x1080 sized window but with everything blown up larger in the same size box. :)
I hope I've explained the situation well enough to replicate.
MicrosoftThis is the desired and "correct" behavior. The RDCMan window should maintain the geometry of the host system where you're running, while the remote system to render at various "zoom" levels - 100%, 125%, 150%, 175%, etc. This can be configured per remote connection, or per the entire group.
Oh, okay. It was just a difference in how 2.93 worked compared to 3.x so it was unexpected. I'll probably stick with 2.93 for now since that works okay for my use case, but I wanted to make sure you were aware that something has changed between versions that may impact adoption rates. 🙂
EDIT: That is to say, if I wanted my 1920x1080 remote desktop to take up more than just a quarter of my 4K monitor it can't really be done. With 2.93 it's sized up by 150% based on my 4K monitor's scaling rate. If I wanted something similar with 3.x I could bump up the remote desktop resolution to 2880 x 1620 and then set the scaling of that remote session to 150%. The net effect would be a window size the same as what I have now, with the remote system having to do a higher resolution and then scaling it, I guess? The trouble there could be when I go over to that remote system and logon locally, any open windows I had would probably do a reshuffle to the regular HD resolution and 100% scaling... it would probably look the same, but it seems like that's more complicated than just letting my local system do the 150% upscaling of the remote desktop window for me, like 2.93 does.
Either that or I use this as an excuse to get an even larger 4K monitor, or get glasses to view the smaller quarter sized RDP window. 😄
I just tested that out. Yeah, I can emulate the look and feel by changing the resolution of my remote desktop to 2880x1620 and then either letting it use my host scaling (or setting it to 150% which is what my host scaling is).
Doing that means my remote session looks the same as it did before where it's actually using 2880x1620 of window space on my machine, and setting a 150% scaling factor keeps all those remote windows and stuff sized right.
Note that not all apps obey scaling, like the app for my UPS (Cyberpower). At 4K, that thing ignores scaling and is super hard to read. :) So although this would work for most well behaved apps that know how to scale, some won't. And it just seems wrong somehow to force the remote system to work at a higher resolution and then scale it back to HD resolution equivalent anyway. And does that mean screen updates over RDP send more data? I'd guess, but maybe the compression factor evens it all out.
