![mac parallels windows 10 rdp keyboard mapping issue mac parallels windows 10 rdp keyboard mapping issue](https://i.ytimg.com/vi/saXq3bdj2Eg/maxresdefault.jpg)
- #MAC PARALLELS WINDOWS 10 RDP KEYBOARD MAPPING ISSUE PATCH#
- #MAC PARALLELS WINDOWS 10 RDP KEYBOARD MAPPING ISSUE PRO#
- #MAC PARALLELS WINDOWS 10 RDP KEYBOARD MAPPING ISSUE PLUS#
Parallels > VMware Fusion, but that could change by the time Fusion with DirectX is out of beta. Remote desktop from Mac to desktop workstation: Map rendered in 5.7s, FPS 889.067 max / 157.337 0.31M tri/sec. !(g2uuyvxnxn851 "Native Windows 10 desktop workstation - Map rendered in 7.9 seconds. VMWare Fusion Tech Preview 20H2 - Map rendered in 12.0 seconds. Parallels Desktop - Map rendered in 10.5 seconds.
#MAC PARALLELS WINDOWS 10 RDP KEYBOARD MAPPING ISSUE PRO#
All results were within the margin of error for every repeated run.Įach test from the MacBook Pro was done using the same external display to ensure it only ever used the dGPU and not the iGPU.
![mac parallels windows 10 rdp keyboard mapping issue mac parallels windows 10 rdp keyboard mapping issue](https://camerondwyer.files.wordpress.com/2018/05/remote-desktop-mouse-cursor-disappear-not-visibile-input-02-windows-black-scheme-cameron-dwyer.jpg)
The results there were surprising, so I performed both it and the native desktop test 2 more times. I repeated each test twice with a reboot in between until I got to the Remote Desktop test. I recorded the performance metrics at the end. For each test I started with a fresh open of ArcGIS Pro, deleted the display cache which triggered another reopen, activated the performance metrics and pressed the + key to get a reliable zoom from one level to another. The same project was copied to local storage on all VMs and the desktop, nothing opened over the network. I would measure the amount of rendering time to the 10th of a second and record the ArcGIS Pro rendering performance metrics. Measure the amount of time it takes to completely render a street network map project of the State of Missouri with a little Kansas thrown in for flavor (recent project I completed).
#MAC PARALLELS WINDOWS 10 RDP KEYBOARD MAPPING ISSUE PATCH#
Windows 10 Enterprise 2004 (for all VMs and desktop) updated with the latest patches available at time of testingĪrcGIS Pro 2.5.2 with latest patch at time of testing VMWare Fusion 20H2 Tech Preview with DirectX11 support
#MAC PARALLELS WINDOWS 10 RDP KEYBOARD MAPPING ISSUE PLUS#
Thunderbolt 3 dock connecting 2 x external 4k displays over displayport, 10GbE networking and USB peripherals.Ĭustom built (by me) workstation desktop with an AMD Ryzen 3950x 16-core CPU (water cooled), NVIDIA RTX 2080ti GPU (water cooled), 64GB DDR4 3600mhz RAM, 2TB Samsung Evo Plus SSD, 10Gb networking.
![mac parallels windows 10 rdp keyboard mapping issue mac parallels windows 10 rdp keyboard mapping issue](https://4sysops.com/wp-content/uploads/2012/03/A-Windows-command-prompt-from-a-Mac-OS-X-computer.png)
I wanted to know how much performance I was gaining or losing with each method.and came away somewhat surprised.Ģ019 MacBook Pro 16" with i9-9850hk 8-core CPU, 5500M 8GB GPU, 32GB of RAM, 1TB SSD, running Catalina Beta 10.15.6. Because of this I either have to virtualize Win10, just use my Windows workstation or RDP into said workstation. Sadly, working in public safety IT and GIS almost none of my applications are natively supported, and among those that are, few if any have GPU rendering acceleration (looking at you, QGIS! lol). I have a 16" MacBook Pro and am a huge fan of MacOS from an ease of use and security standpoint. This was in no way scientific nor did I control all possible was just a fun project. I am a systems engineer first and a GIS analyst second, so I love hardware and tuning. This was primarily done as a fun nerdy project. With that knowledge and a morning off I decided to do some testing to see where the best experience could be had with my current hardware setup. I posted a thread a few months ago about ArcGIS Pro rendering performance and got some great feedback that was really helpful in understanding rendering performance in AGP.