John Tsiombikas <[EMAIL PROTECTED]> writes: > All these are nice and usefull, but they don't really fit in lib3ds. > Lib3ds is not and should not try to be a 3d engine. It's just a library > that lets you read data from a 3ds file easily. This sort of feature > creep will only serve to make the library bloated and miss its true > purpose. Keep it simple and avoid such irrelevant features.
Right, but I don't think anybody is really suggesting making lib3ds target specific output formats. Rather, I think what people would like is functions that translate certain "weird" parts of the 3ds format into information more readily usable by typical applications. In my app I use what AFAIK is the most common mesh representation, with per-vertex normals used for smoothing. Translating lib3ds meshes is kind of annoying because of the funny 3ds "smoothing groups" representation; I fix this up myself by doing vertex splitting (though I'm pretty sure I'm not really doing it correctly :-). Other apps doubtless have to go through the same process, and it would be nice if code to do this was available in a handy lib3ds function. -Miles -- We live, as we dream -- alone.... ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ lib3ds-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lib3ds-devel
