Thanks so much for the testing, seeing how someone else thinks and approaches problem solving is really helpful. I think I'll add a mechanic where boxes can't be pushed against some walls to prevent someone having to restart all the time because they don't know if they've messed it up.
You found many more buggs, thanks. You were not supposed to be able to push the block while on a different side. You also put a box inside another box of the other side and they counter each other, which means there's no collision, but the box is still visible on one side, when it should just disappear. You couldn't find a solution probably because you didn't know what was a bug and what was supposed to happen, but you were on the right track. If you think about it, you could find a way of getting that corner cube which you took by means of bug.
Ok, I sprinkled vector normalizations in every quaternion operation, IT SHOULD NOT HAPPEN AGAIN. If it does, I'm quitting enginedev for good and will probably start learning woodworking or something like that.
Played through all of it except the last two levels which are not supposed to be working yet. Do you accept donations, I feel like you're wasting way too much time and I need to know if it's fixed on your end.
Like I said in the youtube page, sorry for the bugs, it only happens on windows, I thought I fixed it a thousand times, but I normally don't dev on windows. I understand if you don't want to redo the video since everyone gets one shot, but maybe try to see if it's still broken on your end? (by the way, you can run with a commandline argument of the number of the level to jump to)
Is it fixed? Can you find any more bugs? By the way, I have the rendering resolution set to about 80% because my computer isn't as good as yours, but I haven't added settings yet, sorry.
GL_INVALID_OPERATION in glUseProgram(program 5 not linked)
Apparently, it didn't get linked somehow... I've added a debug print to check if the program gets linked correctly. Again, tell me to stop giving you things to do if I'm pushing.
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.
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.
I removed those two extensions, but I'm not sure where I'm using the directive in the middle of a shader, I am now printing the generated shaders. Thanks for the help!
That one is probably fixed now, but I haven't tried in AMD at all, so I don't know if there will be more problems or not with the shader language, thanks for trying it out for me!
