[LWJGL Texture render order?] *solved*

OpenGL Development
#1

Hey JGO, I’ve gotten a little more familiar with LWJGL since my last 3D render attempt, but I’m still trying to get the hang of it.

I’ve managed to setup:
Basic FPS like movement (Key movement & Mouse rotation)
A 20x20 Quad Grid, composed of 64x64 textured tiles. (All flat)
A few boxes stacked on top of each other in the corner.

What the issue is:
I’m a LWJGL Noob so I don’t exactly know.
To explain this from my point of view, it look’s as if there’s something that I’m doing wrong relating to the order of Object rendering. (See below)

Here’s a picture of the issue, this only occurs if I’m below the object:
(Could be explained better, I’m hoping the pictures will help. You can notice the textures look weird)

If I’m above the objects it doesn’t happen:

I figured this problem was relating to the order of which I was rendering my objects, so I went in and rendered them backwards.
Now the issue is the same, just in the opposite direction.

If I’m below the object the issue doesn’t occur:
(With rendering orders reversed)

But if I’m above the object the issue occurs:
(With rendering orders reversed)


Notes:
This happens on all sided of the object.
At the moment I’m currently making several calls to glBegin(GL_QUADS), and I’m applying texture coordinates, everything works fine.
I do make alot of calls to OpenGL during Initialization of OpenGL, (glEnables, hints etc) I’ve tried removing all of them minus the bare minimum needed for the view port, still the same issue.
If anyone would like to see any code, please let me know what.
If this belongs in the ‘Newbie and Debugging questions’, please let me know.

Question:
Should I be rendering multiple quads within 1 single glBegin(GL_QUADS) call? (Not doing it like that at the moment)

Looking forward to some feedback JGO anything would be helpful thanks.

#2

Enable the depth-buffer.

#3

Wow Riven, thanks man works perfectly.
(Thought it was glEnable(GL_DEPTH)) :persecutioncomplex: :persecutioncomplex: :persecutioncomplex:


glEnable(GL_DEPTH_TEST);

25 Lines of glEnables/hints and that one wasn’t in there. :point:

#4

Don’t forget to configure it properly using glDepthFunc

#5

glDepthFunc at the moment is:


glDepthFunc(GL_LEQUAL);

I’ll go look into that, thanks again.

#6

In regards to your question, yes. The fewer times you can call glBegin and glEnd the better (for performance).

#7

There’s several OpenGL debugging functions out there, don’t forget to put them in your main loop, so things like that won’t occur.

#8

There are? Non that would help for this, I think.