Good Morning from my Robotics Lab! This is Shadow_8472, and today, I am more than a tidbit ticked at Windows’ built in remote desktop. Let’s get started!
I’d like to start by saying that Windows Remote Desktop isn’t deserving of a 100% scathing review. It has its purpose. I have concluded it was designed with the tech-savvy Joe who is remoting into his work computer from home or wherever else. As long as you are just surfing the web or using office-type programs, you should be fine.
But as soon as I tried launching Minecraft (I did not test with any other games), the launcher spat out a warning. For context, Minecraft 1.14 was recently released, and I believed they had finally stopped supporting the old launcher and were forcing people to update. The new launcher also crashed the game while trying to launch it, so I spent a day looking into it and getting discouraged over not finding much of anything. I stopped short of updating my video card drivers manually without supervision.
My father finally got the drivers updating, computer glitched, and after several failed attempts, I eventually hooked a monitor back up to it. I was pretty mad when Minecraft launched right away. I pieced together from a few places that 1: Windows Remote Desktop doesn’t use the host’s graphics card like I thought; it loads a basic graphics driver that runs on the CPU. And 2: This graphics driver doesn’t support OpenGL, a library Minecraft needs to run.
Sister suggested moving the whole tower during bedtime worship. I really wanted to fix the solution I was already working on, but it would have been more expensive in terms of time, hassle, and frustration.
Windows Remote Desktop is not a bad piece of software. It was just designed with different goals in mind than I was after.
Final Question: Have you ever had a sure fire project get canceled after it was all done and set up?