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.
Hi Alex,
Thanks for the new version of RDCMan We've upgraded from version 2.92 to the latest release, and I've noticed that even when idle, the new version seems to be using three times the memory. When connected to a session, the memory usage increases even more significantly.
I'm not a developer, so I can't provide a more detailed technical analysis, but I assume it might be related to the changes in the underlying architecture or additional features introduced in this version. Could you shed some light on what might be causing the increased memory usage?
Thanks again for your efforts
MicrosoftLet me know if you run into issues because of this. This is due to some foundational changes in MSTSC, I expect to see improvements here with future Windows updates.
