next »

[Fifth]

Messing with a timing value for the falling boulder trap..



I'm not touching you!

[Fulby]

The screen shot function in my game was broken and took the image of a star system from the XZ plane instead of overhead. It's meant to look like this:


Instead it looks like this:


I like it though - it could make good minimalist cover art for a space game or movie.

[oahda]

Such as this game? You've already got the logo and all on there!

[Fulby]

It was adding the logo that broke it . But no it wouldn't fit the feel of the game and I've draft cover art already.

[oahda]

Could add some unsettling, noisy background sounds to this and I'd have creepypasta material. Starting the program I get a black screen, but if I start resizing it, I randomly get distorted still frames of creepy monkey heads:

EDIT:
Now that I've fixed it, here's how to do it: forget to clear your FBO's depth buffer every frame.

[Dakutau]

Seems that the KO-animation does not take notice when the playerobject hit the ground.

[Pineapple]

I swear it's literally impossible to consistently get the Y axis right when writing gl rendering code 

[oahda]

I used to have issues like that in the past, but ever since I started playing by OpenGL's rules (y is up/down rather than z, starts bottom left, positive is up) there have been zero issues (some 3D formats would still give me upside down UV's, but Khronos's own glTF format fixed that too). Highly recommended.

Can understand if it feels annoying to do it "upside down" if it's a 2D game and you're not used to it, but it's honestly a good idea. No ugly hacks and workarounds everywhere like layout(origin_upper_left) in shaders.

[Pineapple]

I used to have issues like that in the past, but ever since I started playing by OpenGL's rules (y is up/down rather than z, starts bottom left, positive is up) there have been zero issues (some 3D formats would still give me upside down UV's, but Khronos's own glTF format fixed that too). Highly recommended.

Can understand if it feels annoying to do it "upside down" if it's a 2D game and you're not used to it, but it's honestly a good idea. No ugly hacks and workarounds everywhere like layout(origin_upper_left) in shaders.

Actually it turns out, no, positive Y is down in opengl. (...If you're rendering to a framebuffer.) Also, it was NOT fun to realize after a half hour that the reason I couldn't just fix it by flipping it vertically was because of back-face culling and forgetting to use a VBO other than the one that gets drawn right-way around when not rendering to a framebuffer.

[JWki]

I used to have issues like that in the past, but ever since I started playing by OpenGL's rules (y is up/down rather than z, starts bottom left, positive is up) there have been zero issues (some 3D formats would still give me upside down UV's, but Khronos's own glTF format fixed that too). Highly recommended.

Can understand if it feels annoying to do it "upside down" if it's a 2D game and you're not used to it, but it's honestly a good idea. No ugly hacks and workarounds everywhere like layout(origin_upper_left) in shaders.

Or you just convert coordinates right before rendering. You have to do some sort of conversion from game units to pixels anyways right?

[oahda]

Yeah, not sure how 2D/ortho affects things yet… I've only done it the messy way in 2D/ortho and by GL's rules in 3D/perpective so far, so we'll have to see. But I've had no issues with regular textures loaded with stb_image nor with textures created at runtime by rendering into framebuffers when mapped onto objects; neither has been upside down, and I haven't had to flip any data anywhere after loading it, so I'm happy so far.

[powly]

I used to have issues like that in the past, but ever since I started playing by OpenGL's rules (y is up/down rather than z, starts bottom left, positive is up) there have been zero issues (some 3D formats would still give me upside down UV's, but Khronos's own glTF format fixed that too). Highly recommended.

Can understand if it feels annoying to do it "upside down" if it's a 2D game and you're not used to it, but it's honestly a good idea. No ugly hacks and workarounds everywhere like layout(origin_upper_left) in shaders.

Actually it turns out, no, positive Y is down in opengl. (...If you're rendering to a framebuffer.) Also, it was NOT fun to realize after a half hour that the reason I couldn't just fix it by flipping it vertically was because of back-face culling and forgetting to use a VBO other than the one that gets drawn right-way around when not rendering to a framebuffer.

Positive y is most definitely up, rendering to a frame buffer is exactly the same as rendering to the screen (which is a frame buffer, just one you don’t create explicitly). You’re most likely accessing the resulting texture in an inverted manner.

[bitbulldotcom]

Messing with custom shaders to draw overlapping geometric shapes. This is one shader. Not remotely the effect I wa looking for but I thought it looked kind of cool nonetheless - may use something similar elsewhere in the game!

[JobLeonard]

The effect might warrant an epilepsy warning though

[bombjack]

Here is what happens when you mess up the axis

[oahda]

Shader messup which was rather beautiful:



What I was actually trying to make and in the end managed to:



(voronoi cracks)

[JobLeonard]

If I squint I can already see the intended Voronoi cracks in the background. How did it happen? It looks a lot like when I use too small integers for my range and get funky modulo effects due to integer overflow bugs.

[oahda]

I don't remember exactly when along the process this happened, but I used a triangular wave to make the voronoi lines jagged, so I think it has something to do with that since it made diamond shapes. Combined with gl_FragCoord maybe.

[Radiant]

Shader messup which was rather beautiful:

This should be a hidden menu option in your game

[oahda]

It was actually for someone else's game!