Find file format somewhere. Read it and parse into your mesh structure. Where is the problem here? You need to ask a more specific question.

I agree with Secretary of State X-G.

Anyway, for a file format to implement I suggest the Wavefront OBJ format - it's an ASCII format, and about as simple as a 3d model format can be (at least if you ignore the NURBS stuff). And as a bonus, most decent modelers can export to .obj so you won't have to write your own converters.

I understand what you say, but now, can you suggest me some tutorials of allegro opengl or something about 3d programming with allegro?

Somebody can suggest me a program to convert 3d models into file to parse into mesh structure.

thanks a lot at all!

Game Tutorials scroll down the page, you will find tutorials on how to load some 3d models format in your prog

Load both and display them at the appropriate time, of course.

Ask more specific questions, damn it.

Ah, the irony...

So? Start typing!

MD2 is actually a pretty easy format to load and display. The downside is that it's pretty aged and still uses frames and not a skeletal animation system. I hacked up a small MD2 loader last weekend for my game, to see how hard it actually is to load/display them. (see attached file) It uses C++, Allegro and AllegroGL, and it's not 5 pages long It could be even shorter by using a single fread to load the data. Anyway, maybe it gets you started.

Some things to note:
- the animation is hard-coded to the single "stand" animation of the model. There's a list with the different animations and how many frames they use somewhere

- the animation is a bit bumpy, that's because only the key frames are displayed, there is no interpolation done

- it's my first try at MD2 and 3d models in general, so it's not perfect

Do you have vsync on? I get like 1400fps without vsync. To get smooth movement you have to interpolate between the current frame and the next frame. That means computing the vertices of the triangles on your own, depending on the display duration between the single keyframes.

I didn't implement it because it was just a test and my game will only need few (if any at all) animations, it's a space shooter

But it shouldn't be that hard to implement it. I think all you have to do is to get the difference between each current vertex and the next vertex, divide this distance by the number of steps (smoothness) and add this number to the current vertex position.

steps = 10
distance = new_x - old_x
amount = distance / steps
vertex_x = old_x + amount

for x, y and z. Maybe it's easier to use vectors though.

No, some do also feature NURBS and other mathematical surfaces that can either be passed to the GL or transformed into poly's at run-time.
There are also a few games (very few, actually) that use some kind of voxel models, especially for terrain.