Skip to content
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

SHADERed won't launch when SHADERed is installed in program files (Windows) #2

Open
bencresty opened this issue Dec 22, 2021 · 0 comments

Comments

@bencresty
Copy link

bencresty commented Dec 22, 2021

First of all; thanks for the amazing tool! Finally a great standalone tool to program and debug shaders. I was looking for that for a long time. Aside from the debugger crashing at the moment for some reason everything works pretty well and it clearly is thought through well! Great work! Looking forward to also being able to use breakpoints and all that, which is just fantastic!

little thing:

For some reason when 'installing' SHADERed in a subfolder inside `Program Files' and using that path in the global VS Code settings.json configuration as executablePath, SHADERed never gets launched on debug.

It does get launched though when moving the SHADERed installation to within the project folder itself, so get it locally. For instance inside a bin folder inside the project folder.

So this does NOT work:

"shadered.executablePath": "C:\\Program Files\\SHADERed\\SHADERed.exe"

But this DOES work:

"shadered.executablePath": "X:\\projects\\shader-project\\bin\\SHADERed\\SHADERed.exe",

Although a small detail and easy to workaround, there is a big advantage in having SHADERed installed globally; its settings. So it would be nice if this could work in the future.

Anyway, keep up the great work!

SHADERed version: 1.5.6
SHADERed extension version: 0.0.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant