Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

It's still the two of them, though only one of them shows up every time; GL_INVALID_OPERATION in either utils/shader.c:447 or utils/texture.c:814

The texture one I fixed, but the shader one is hard because I don't know the context, are you familiar with gdb? If it's asking too much, I understand.

Not very well versed in that, I've used it within code::blocks for my own game to see where it crashes and to set breakpoints, but that's it.

(1 edit)

If you have git installed and you're not bored of dealing with this yet, run the following lines

git clone --recursive github.com:EvilPudding/Shift3d.git

then in the cloned directory,

make gdb

break exit

run

bt

https://pastebin.com/raw/Edgcsp6g

Does the code run if you comment out line 217 of candle/components/light.c

Like so:

        /* renderer_draw(self->renderer); */

Unfortunately no. The backtrace looks like this now:

https://pastebin.com/raw/ViDGFF9Y

So all shader binds are giving GL_INVALID_OPERATION? Damn, this is hard to debug in these conditions, I think I will have to find an AMD computer to fix it... Thanks for all the help.

Yeah, that's basically why I have the GT710 too, to have something from Nvidia to test things with. Have you tried using the Nouveau driver to see if you can debug the issue with that? It doesn't seem to support the required OpenGL version on my card though, so I'm not sure if it's helpful (using MESA_GL_VERSION_OVERRIDE to fake 4.4 support makes the game actually start and run into the same error, but then again that could be because something that's actually needed isn't supported by the driver).

Anyway, sorry for not being able to help any further. I have no idea about anything when it comes to shaders.

I just added in the latest commit more debugging options, can you pull, make clean, make gdb, and try again?