-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several errors with "zed" command in UCRT64 - unable to open program #21459
Comments
reported upstream: zed-industries/zed#13575 |
same problemhere: `[2024-08-09T16:11:11-07:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] } OS Name: Microsoft Windows 10 Pro |
there is still nothing to do with that. in some machines zed work, in other not |
@aranapatona wrote:
I have the same problem and was initially puzzled. I'm not a gamer and so I didn't immediately noticed the importance of that missing Vulkan error. Vulkan is a low-level graphic API usually supported at the device driver level. The machine were I tried to test Zed is a very old machine and so its graphic card driver doesn't support Vulkan (my NVidia graphic card on that machine broke and so it's using a device driver for the integrated Intel G33/G31 Express chipset which support DirectX 9.0c). I searched for a Vulkan-to-DirectX 9 translation layer Conclusion: if the device driver for your graphic card/chipset doesn't support Vulkan (or at least DirectX 12 and you know how to compile and install Dozen translation layer) there is no way to run Zed on such machine at the moment. Update: apparently there is a translation layer called Ashes that should support DirectX 9 (to 11), according to this chart on Vulkan web site, on Vulkan Porting Layers page: but from what I understand at a glance it's not transparent, a patch to Zed source is needed to use it. Update 2: this information is NOT correct. See: Are DirectX 9 and 10 actually supported? #282
|
Description / Steps to reproduce the issue
Proceeded to type:
pacman -S mingw-w64-ucrt-x86_64-zed
installed succesfully
Expected behavior
Expected to type "zed" on the UCRT64 shell to run Zed.
Actual behavior
Errors showed up when "zed" was typed at the prompt with the following result (I'm including the prompt where I'm trying to reinstall again to ensure nothing was missed, and it did fine and then followed by typing "zed") Also, I see its mentions an unsupported device? I'm including further down my computer info in case this further helps.
Laptop config:
Verification
Windows Version
MINGW64_NT-10.0-19045
MINGW environments affected
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: