# OpenGL tilemap in 3d not 2d - 3d newb

This topic is 4175 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

##### Share on other sites
It's quite simple to create a map:
Keep it 2D!

At least the structure of it.

How to load models/heightmaps are available on the net.

Basically a Heightmap is a grid (much like your gamemap, but with the numbers representing height instead of a tilenr) which is looped through with:
glBegin(GL_TRIANGLES);for (x < width-1) for (y < height-1)   glVertex3f(x+1, height(x+1,y+1), y+1);  //corner A   glVertex3f(x, height(x,y+1), y+1);      //corner B   glVertex3f(x, height(x,y), y);          //corner C   glVertex3f(x+1, height(x+1,y), y);      //corner DglEnd();float height(int x,int y) {// reads height from heightmap data (i.e standard grid) }

Code is not tested, and is pseudo.

Using the various techniques has their own pro/con's:

Heightmap:
Pro: Easy collision detection, quite fast.
Con: No extravagant details, no cliffs etc.

Models:
Pro: Can be any shape
Con: Harder to collision detect.

Hope all goes well!

Cheers!

/Robert

EDIT:

nehe.gamedev.net <-- LOTS of excellent tutorials for basic/immediate and advance usage!

##### Share on other sites
You must know how a point given in 3D world is mapped to be displayed on the 2D screen. Verbosely, a vertex is a point where faces (usually triangles) of a mesh have a corner. Those vertices of a mesh are specified not in the worlds global co-ordinate system, but in a local co-ordinate system. This is senseful to be able to use the same mesh (i.e. vertices at the respective same vertex positions when seen in local co-ordinates) regardless where in the world the mesh as a whole is located. However, when rendering, the mesh actually appears at a global position, and hence the vertices _are_ to be transformed from the local to the global space. This is done on-the-fly by what OpenGL calls the Model transformation.

Next, you as the observer of the scene be located also somewhere in the global space. If you move you see another cut of the world. So, what you have to display ("what you see") doesn't depend only on the placement of meshes but also of you (most often expressed as a camera). This is what OpenGL calls the View transformation.

Still being in 3D, now its time to map the cut scene onto the screen. This can be done (you already know that) in different modes, mainly in perspective or orthogonal projection.

So coarsly you have to transform a vertex like this:
local (3D) -> global (3D) -> view/camera (3D) -> screen (2D)

In OpenGL you assemble the part local (3D) -> global (3D) -> view (3D) in the so-called MODELVIEW matrix (in D3D these both parts are more distinct), and the part view (3D) -> screen (2D) in the so-called PROJECTION matrix.

Both of these matrices are seperated by the matrix mode. The PROJECTION matrix is normally set up once and used throughout the whole lifetime of the application. The MODELVIEW matrix is normally set up per frame, because the camera stuff is changed all the way.

OpenGL is normally in MODELVIEW matrix mode. Switching is to done by yourself. So somewhere at the (logical) beginnging of the app you switch to the PROJECTION matrix, set it up, switch back to the MODELVIEW matrix, and begin with your game loop. One of the parts of the game loop is setting up the MODELVIEW matrix. First the VIEW portion as a very first part of rendering, then the MODEL portion appropriately for each mesh.

Notice that the order in which the transformations are assembled by their particular matrices (for position, orientation, and perhaps scaling) is a very important thing!

##### Share on other sites
Thank you very much haegarr... I think the explaination of the matricies and their order has really helped me out a bunch. A few things I didn't understand are starting to click together.

One thing I am still missing as this relates to a tile map. I have read about "stretching a texture accross a mesh". I would think this involves calulating texture coordinates to place with all of the verticies. Not that it is really all that difficult to figure out programaticly I am just wondering if there is something I am missing that makes this part a bit easier?

Also, setting up glFrustum... I can get it to work using gluPerspective (ala NeHe) but I would like to know how to get this to work... Any ideas or suggestions that explain in depth? I have searched google results extensively but as I said in my original post, many tutorials suggest that I have some deeper understanding of 3d concepts.

I can follow along in the NeHe tutorials but I feel like I am copy, pasting and not really understanding why some things work the way they do.

• ### Similar Content

• By xhcao
Does sync be needed to read texture content after access texture image in compute shader?
My simple code is as below,
glUseProgram(program.get());
glBindImageTexture(0, texture[0], 0, GL_FALSE, 3, GL_READ_ONLY, GL_R32UI);
glBindImageTexture(1, texture[1], 0, GL_FALSE, 4, GL_WRITE_ONLY, GL_R32UI);
glDispatchCompute(1, 1, 1);
// Does sync be needed here?
glUseProgram(0);
GL_TEXTURE_CUBE_MAP_POSITIVE_X + face, texture[1], 0);
glReadPixels(0, 0, kWidth, kHeight, GL_RED_INTEGER, GL_UNSIGNED_INT, outputValues);

Compute shader is very simple, imageLoad content from texture[0], and imageStore content to texture[1]. Does need to sync after dispatchCompute?

• My question: is it possible to transform multiple angular velocities so that they can be reinserted as one? My research is below:

• I have this code below in both my vertex and fragment shader, however when I request glGetUniformLocation("Lights[0].diffuse") or "Lights[0].attenuation", it returns -1. It will only give me a valid uniform location if I actually use the diffuse/attenuation variables in the VERTEX shader. Because I use position in the vertex shader, it always returns a valid uniform location. I've read that I can share uniforms across both vertex and fragment, but I'm confused what this is even compiling to if this is the case.

#define NUM_LIGHTS 2
struct Light
{
vec3 position;
vec3 diffuse;
float attenuation;
};
uniform Light Lights[NUM_LIGHTS];

• By pr033r
Hello,
I have a Bachelor project on topic "Implenet 3D Boid's algorithm in OpenGL". All OpenGL issues works fine for me, all rendering etc. But when I started implement the boid's algorithm it was getting worse and worse. I read article (http://natureofcode.com/book/chapter-6-autonomous-agents/) inspirate from another code (here: https://github.com/jyanar/Boids/tree/master/src) but it still doesn't work like in tutorials and videos. For example the main problem: when I apply Cohesion (one of three main laws of boids) it makes some "cycling knot". Second, when some flock touch to another it scary change the coordination or respawn in origin (x: 0, y:0. z:0). Just some streng things.
I followed many tutorials, change a try everything but it isn't so smooth, without lags like in another videos. I really need your help.
My code (optimalizing branch): https://github.com/pr033r/BachelorProject/tree/Optimalizing
Exe file (if you want to look) and models folder (for those who will download the sources):
http://leteckaposta.cz/367190436
Thanks for any help...

• By Andrija
I am currently trying to implement shadow mapping into my project , but although i can render my depth map to the screen and it looks okay , when i sample it with shadowCoords there is no shadow.
Here is my light space matrix calculation
mat4x4 lightViewMatrix; vec3 sun_pos = {SUN_OFFSET * the_sun->direction[0], SUN_OFFSET * the_sun->direction[1], SUN_OFFSET * the_sun->direction[2]}; mat4x4_look_at(lightViewMatrix,sun_pos,player->pos,up); mat4x4_mul(lightSpaceMatrix,lightProjMatrix,lightViewMatrix); I will tweak the values for the size and frustum of the shadow map, but for now i just want to draw shadows around the player position
the_sun->direction is a normalized vector so i multiply it by a constant to get the position.
player->pos is the camera position in world space
the light projection matrix is calculated like this:
uniform mat4 light_space_matrix; void main() { gl_Position = light_space_matrix * transfMatrix * vec4(position, 1.0f); } Shadow fragment shader:
out float fragDepth; void main() { fragDepth = gl_FragCoord.z; } I am using deferred rendering so i have all my world positions in the g_positions buffer