Printable View
Currently I am using a triangle list to render the terrain.
Almost all the tutorials I am reading teach a method of loading the terrain so you can use quads.
Do I want to use quads??
Next.
People keep telling me to run through each row Like right to left and then the next column left to right.
Why and is this how it has to be done? What for?
All I do for storing the vertices is run y 0 to mapsize and x 0 to mapsize.
When it comes to openGL what is the difference between:
glBegin(GL_QUADS);
glBegin(GL_TRIANGLE_STRIP);
What is the D3D equivelants?
Some of these OpenGL tutorials read and render the vertices in the same function....This is stupid.
TriangleList with indices means 3 points for each triangle right?
TriangleStrip with indices means 4 points for each quad right?
LineList/Strip is the same deal, cept it shows wireframe.
Explain trianglefan?
Reading OpenGL tutorials are we? Well, if I am not wrong I think that quads are have more or less the same speed as triangels. I think the drivers are doing the quad to triangle transelation for you or something like that.Quote:
Originally posted by Halsafar
Currently I am using a triangle list to render the terrain.
Almost all the tutorials I am reading teach a method of loading the terrain so you can use quads.
Do I want to use quads??
If you don't then the first triangle/quad on the next line will use the last or few last vertices from the triangle on the other side, and you will stretch that one from one side of your terain to the other one. You can end the drawing after you have gone from one side to the other, and then start again on the other side again. Like you are doing in open gl with glBegin() and glEnd pair.Quote:
Originally posted by Halsafar
Next.
People keep telling me to run through each row Like right to left and then the next column left to right.
Why and is this how it has to be done? What for?
Quote:
Originally posted by Halsafar
When it comes to openGL what is the difference between:
glBegin(GL_QUADS);
glBegin(GL_TRIANGLE_STRIP);
What is the D3D equivelants?
Some of these OpenGL tutorials read and render the vertices in the same function....This is stupid.
TriangleList with indices means 3 points for each triangle right?
TriangleStrip with indices means 4 points for each quad right?
LineList/Strip is the same deal, cept it shows wireframe.
Explain trianglefan?
If you don't know what the ground primitives looks like, I think you should stop for a moment, and learn some of the basics of DX before you move on.....you also asked about the texture mapping question that is pretty basic compared to what you are trying to pull off. But if you can wait 5min, I will try to make some drawings for you so you can see what they look like.
PS: I will make better images once I get the time to start on my DX tutorials after X-mas.
DX: Linestrip:
http://vbforums.com/attachment.php?s=&postid=1850544
DX: Triangle list:
http://vbforums.com/attachment.php?s=&postid=1850546
DX: Triangle Strip:
http://vbforums.com/attachment.php?s=&postid=1850548
DX: Trianglefan:
http://vbforums.com/attachment.php?s=&postid=1850551
OGL: glQuads (glTriangles is the same just with 3 vertices in stead):
http://vbforums.com/attachment.php?s=&postid=1850555
OGL: (gl_triangle_strip):
http://vbforums.com/attachment.php?s=&postid=1850558
OGL: (gl_quad_strip):
http://vbforums.com/attachment.php?s=&postid=1850561
OGL: (gl_triangle_fan):
http://www.vbforums.com/
OGL: (gl_polygon):
http://vbforums.com/attachment.php?s=&postid=1850563
Did I forget any? Or did I do something wrong...well this is all from the top of my head...and I am tired again. So let me know if something is wrong here..
You should know that out of all the topics I've read. None have showed such beautifully simple diagrams.
I could picture TriangleStrip and TriangleList in my head, I understand how to orient them properly.
Thanks.
I must say my knowledge of how the 3d environment is made is still a little primitive. I understand a lot of more than I did before. But the majority of my knowledge is in game engine design around everything but the extreme details of how the rendering goes.
Like playing with Renderstates and TextureStageStates is somewhat beyond me. I don't understand W Buffers and what Stencil Buffers are. But that will all come in due time.
As for openGl.
It is suprisingly simple so far.
Way easier than direct x...So far..
Although I think I am not goona go to far into it, I enjoy D3D for now.
Thanks for the compliments. I hope the next pictures for the tutorials will be better tho...;)
I liked OpenGL too when I tried it. Wrapping up the Western game I made didn't take much time, and I have never looked at OpenGL before. But something is still holding me back from using it. DX is in my heart...;)
I love OpenGL. It's more flexible than DirectX and it's syntax makes it more readable too. I just created a program that uses both DX8 and OpenGL. Only I used DirectX8 to switch to Fullscreen/Windowed mode (as well as DirectInput and other things). I did it like that because I wanted to be able to switch to fullscreen even when the Forms borderstyle is Sizable. OpenGL's fullscreen mode left the border there and I didn't like that. Would have been ok if I didn't have a hybrid of Fullscreen/Windowed. Only way I could have avoided that was to create a Win32 Window rather than using a Form so I could have more control then over my window. That would leave another problem though. No DirectInput for the mouse then since a form is required.
But yeah, OpenGL rocks.
So again on a side note.
I record my vertices row by row left to right only.
I then store the indices of each triangles properly, I know it is properly.
Unless.
A bmp width of 128 in DC form is that 0-127 or 0-128.
If it has pixels between 0-127 then I am recording everything fine.
Switching between linestrip and list took a minimal ammount of indices relisting, which I just did and recompiled.
Next is to figure out the nice way to get a mountain texture on cliffs and grass everywhere else....Where to start.