DadSchoorse/vkBasalt

Path is correct but always "failed to load shader file" with reshade shaders

ralgar opened this issue · 3 comments

ralgar commented

Using latest vkBasalt 0.3.2.6, no matter what I always get this same error:

vkBasalt info:  config file: /home/ralgar/.config/vkBasalt/vkBasalt.conf
vkBasalt info:  depthCapture = off
vkBasalt info:  reshadeIncludePath = /home/ralgar/.config/vkBasalt/carmack-eternal/Shaders
vkBasalt info:  reshadeTexturePath = /home/ralgar/.config/vkBasalt/carmack-eternal/Textures
vkBasalt info:  effects = curves
vkBasalt info:  curves = /home/ralgar/.config/vkBasalt/carmack-eternal/Shaders/Curves.fx
Selected GPU 0: NVIDIA GeForce GTX 1060 6GB, type: DiscreteGpu
vkBasalt err:   failed to load shader file:
vkBasalt err:   Does the filepath exist and does it not include spaces?
zsh: segmentation fault (core dumped)  ENABLE_VKBASALT=1 vkcube

My vkBasalt.conf:

depthCapture = off

reshadeIncludePath = "/home/ralgar/.config/vkBasalt/carmack-eternal/Shaders"
reshadeTexturePath = "/home/ralgar/.config/vkBasalt/carmack-eternal/Textures"

effects = curves

curves = "/home/ralgar/.config/vkBasalt/carmack-eternal/Shaders/Curves.fx"

The path is 100% correct:

❯ stat /home/ralgar/.config/vkBasalt/carmack-eternal/Shaders/Curves.fx
  File: /home/ralgar/.config/vkBasalt/carmack-eternal/Shaders/Curves.fx
  Size: 6271      	Blocks: 16         IO Block: 4096   regular file
Device: 0,52	Inode: 14652641    Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/   ralgar)   Gid: ( 1000/   ralgar)
Access: 2022-09-17 20:54:24.539873404 -0700
Modify: 2022-09-17 20:54:24.539873404 -0700
Change: 2022-09-17 20:54:24.539873404 -0700
 Birth: 2022-09-17 20:54:24.539873404 -0700

Why can't vkBasalt find the shader? Clearly the path exists and has no spaces.

I've tried quotes, no quotes, relative path, absolute path, 777 perms applied recursively.

Tried literally everything I can think of. I'm completely stumped.

Boulotaur2024 commented

Same here
Weird...

ralgar commented

@Boulotaur2024 Yeah, I gave up trying to get it working. Any luck on your end?

ralgar commented

This appears to be working fine now with the latest git build. Closing the issue.