It's not virtual displays at the OS level, it's for use within DisplayFusion:
https://betanews.com/2013/09/03/dis...plit-monitors-into-multiple-virtual-displays/
It's basically containers so that your keyboard shortcuts of (for example) "Move and size this window to the top right 25% of this display" act on the virtual display rather than the entire physical display. So I have a saved preset that I take with me from machine to machine that sets the following numpad shortcuts (with control + alt):
7, 9, 3, 1 = Size and move to the 25% of the display/virtual display (7 = top left, 9 = top right, etc)
8, 6, 2, 4 = Size and move to the 50% of the display/virtual display (8 = top, 6 = right, etc)
5 = Maximize
It's completely seamless at the OS level, I also use virtual taskbars so that application taskbar icons only appear on the 1/3 of the screen where the application actually is.
As for RDP, remember that RDP uses a completely separate graphics stack, RDP sessions do not at all reflect the physical monitor setup. It would presumably work fine through something that uses the regular graphics driver (VNC, etc).
[EDIT]Or do you mean the other direction, making a full screen RDP session to another PC full 'screen' on one of the virtual displays? Just tried that and RDP connect set to full screen does not see the virtual displays and instead goes full screen across the entire physical display. I have been using big monitors for so long that I never use full screen mode, instead I choose a size that correlates to the area I want the window to live. Unfortunately mstsc doesn't seem to allow custom resolutions through the GUI, other solutions might. You can, however, modify saved RDP sessions for custom resolutions (just make sure screen mode id:i:1). I much prefer windowed RDP on a big screen, so sticking to common resolutions like 1600x900 etc works fine for my needs. I just tested a 1200x2000 window which fit easily into 1/3 of my screen and snaps well using DisplayFusion shortcuts.[/EDIT]
Viper GTS