-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Unexpected renderer error occurred after specifying pixel shader path. #9338
Comments
Weird, that error is:
Which I don't think makes any sense. Does the retro terminal effect work for you? Use |
After trying However, when I changed the path from Then I restarted Windows Terminal; changed path to other shader files in the same folder; tried to "glitch" again. But nothing new happened. |
Hey so, I know you've gone through the trouble of hiding your Windows username in your screenshots, but I'm worried now if that might be part of the problem. Does your username have any Chinese characters in it? I'm worried that the shader might fail to load if the path has non-ascii characters in it. If you don't want to share your username, could you try some other path with Chinese characters in it? |
No, my username is made up of English letters and number digits. It's even a valid variable name in C/C++. |
Huh. Well there goes that theory. Here's another totally wild theory - does the drive matter? Can the Terminal consistently load shaders from the |
Everything is working perfectly today. I've tried both drives, path with Chinese characters, inside and outside But I have no idea on what caused this change. Basically I was browsing the Internet and making PowerPoints these days. There was neither system update, nor Windows Terminal Update.😂 |
Well. That's annoying that the repro is gone before we could figure it out. But I'm glad that it's fixed! I still have no idea what might have caused this. I suppose I'll keep my eyes open for future reports. Thanks! |
Environment
Steps to reproduce
I had a fresh new Windows Terminal install from Microsoft Store;
downloaded example shaders from here;
added the following line to "Windows PowerShell" profile in
settings.json
and saved changes to file;restarted Windows Terminal and a warning popped up:
which translates to:
And I think this warning message comes from this line.
I also tried changing the path to
D:/temp/Invert.hlsl
; changing the path to an empty folder; adding obvious syntax errors to the hlsl file.But nothing changed, every time the exact same warning message popped up.
Expected behavior
Nothing pops up and the screen color is inverted.
Actual behavior
Described above.
The text was updated successfully, but these errors were encountered: