Honestly I didn't expect they would include it in the main API. I was just figuring they might have some kind of example or such. What with them transitioning from the "It's a spec" mentality to the "It's an SDK mentality".

Quote:Original post by n00body
Honestly I didn't expect they would include it in the main API. I was just figuring they might have some kind of example or such. What with them transitioning from the "It's a spec" mentality to the "It's an SDK mentality".

http://quesoglc.sourceforge.net/

there is a decent one (based on freetype)

Quote:Original post by n00body
Honestly I didn't expect they would include it in the main API. I was just figuring they might have some kind of example or such. What with them transitioning from the "It's a spec" mentality to the "It's an SDK mentality".

I understand your point, but it's not so easy, especially for something so involved like meshes... especially animated ones.
Everybody likes to have meshes in a way it's managed with a bit of secret sauce. Next-gen projects will probably add a bit of "muscle physics" simulation to the skeletral system.

You can write and provide a library which reads .png - everybody uses .png and it's a well defined format. You can design a tool which produces sound, or a file format which encodes arbitrary amount of channels (RAD).
You cannot just write and provide a library which reads "meshes" and plugs them in your engine - what a "mesh" really is and how it's managed is not so well defined.