[Window Title]
Critical
[Main Instruction]
Unsupported GPU
[Content]
Zed uses DirectX for rendering and requires a compatible GPU.
Currently you are using a software emulated GPU (Microsoft Basic Render Driver) which
will result in awful performance.
For troubleshooting see: https://zed.dev/docs/windows
Set ZED_ALLOW_EMULATED_GPU=1 env var to permanently override.
[Skip] [Troubleshoot and Quit]
That's more of an issue with your system than an issue with Zed, you have to veer pretty far from the beaten path to not have proper DirectX nowadays. Are you running Windows in a VM?
I've literally programmed with VSCode for basically a decade this way without issues. Zed lags, it's disappointing and if I really like Zed I'll have to sort out another setup.
MSTSC is one of the rock-solid tools from Microsoft, and does better than almost everything else available on the market other than some PC over IP technologies specifically highly optimized for this use case. I've been programming with an ancient ThinkPad forever because I'm just remoting into a much more powerful machine.
If you are having problems with Windows RDP then the problem is somewhere else along the pipeline, not RDP itself. No other remote solution I've used is even in the same ballpark as RDP in terms of responsiveness and quality. RDP on a LAN is very usable for actual coding work.
Maybe try gaming-oriented remote desktop tools, like steam link or sunshine/moonlight. Those work great with directx, assuming you have a working gpu (at least integrated gpu) on your remote box. They also have way better latency, though use a lot more bandwidth.
By explaining the advantages over "older" methods. A lot of people use Moonlight/Sunshine for non gaming related stuff, specially considering than the alternatives are all proprietary.
They're productivity tools, not gaming software. You'll be faster and deal with less errors using the correct optimized remote desktop tool for your job, versus what you're using now, which can be slow and error prone.
Sunshine and Moonlight are no more than accelerated and finely tuned VNC servers that happen to be targeted at gaming. You can totally set them up as a regular remote desktop solution.
Right, but I'm saying their sites make it very clear that they're meant for gaming, so GGP may indeed have a hard time convincing corporate IT that they're for work.
My post was answering the question of how they should ask for permission to use it. You pitch it as productivity software that helps you do your job better.
If no monitor is connected then RDP doesn't load gpu drivers. It can also make RDP performance much worse as HW accelerated video encoding is not working
I assume it is not an issue with other applications like Chrome or VSCode (I mean VSCode is Chrome). They usually have some sort of fallback rendering on these environments that work well enough.
It may not be an actual problem with zed either, despite the warning.
Maybe it's misdetecting something? I used to use Remote Desktop for game development sometimes, as weather could make the journey to the office impossible, and the performance was always pretty ok, even with UE5 stuff making heavy use of Nanite running at 1440p.
And if it was actually software emulated, which I can't believe for a moment, though I admit I never checked (I just always assumed the window contents were transmitted via some kind of video encoder) - then I can't imagine that a text editor would be a problem.
The input latency might not be as good as you'd like.
> The input latency might not be as good as you'd like.
Yeah input latency is annoyingly rough, not super bad but _just_ laggy enough to make it annoying to use.
Debating how much I want to change things, I can directly punch into my Linux machine but all my dev IDEs are on a VM for a long list of reasons, and I doubt Zed is going to run on my old ThinkPad if it struggles on software rendering, but we'll see.