It's not really a stupid question, but it's horribly written(since you want to program maybe you should try to write properly or at least try(like I'm doing ^^)).

And loading "3d objects" is all about knowing or be able to handle the file format. and i know i shouldn't answer this question since i don't really have much of a clue but no, there is no function within allegro that allows you to import 3ds files. Find out how to make such an function or use an already written one.

One more thing, if you're into 3d, pure allegro is not what you want.
Try out AllegroGL.

?

But obj provides no animation, correct? Which means you'd need a separate obj file for each frame of the animation, which would waste a lot of space and resources.

Way off-topic, but gnolam's post have just made my day !

Maybe if you try a little harder, you'll hit the shift key every time you press the "I" key.

The reason that there are no Allegro-specific importers is because Allegro does not have internal data representations for meshes. It is too low-level for that. Any importer needs to be customised to the in-memory format.

I have my own internal format, and code to render this to both Allegro software 3d and OpenGL, but it isn't flexible enough (yet) to be considered a universal solution. For example, at the moment I use arrays of V3D_f to store vertices, which were designed for Allegro's old (and nearly deprecated) 3d routines, and contain c,u&v values for each vertex. This is not ideal for most models, which have the u,v values stored for each vertex in a face, not once for each vertex in the mesh.

My plan is to expand my current MESH types from the following

typedef struct MESH_TYPE {
   int flags;
   int n_verts;  VERTEX_TYPE * verts;
   int n_edges;  EDGE_TYPE * edges;
   int n_tris;  FACE_TYPE * tris;
  
} MESH_TYPE;

and replace them with a universal type

typedef struct MESH_TYPE {
   int flags;
   MESH_VTABLE * vtable;   
   int n_verts;  void * verts;
   int n_edges;  void * edges;
   int n_faces;  void * faces;
  
} MESH_TYPE;

which can be used as the in-memory format for nearly all uses. If this catches on, it could make it possible to develop universal importers, that do not tie you to external engines like Ogre, irrlicht, etc.

I don't get it...

ah...