Ok, then I'll look into translating your color dll to blitz.
About the file formats, "to me" this almost rides on the notion that you want this open source 3d engine to be totally customizable. So, I would think it would be better to later create add-ons to load/save various 3d file formats if so desired. In this case, people here know blitz. Why not just get something we are more likely all somewhat more familiar with, the .b3d format. That will give us d'em bones to animate. The modelling & animation tools I have are gameSpace( currently does .md2 & md3 well supposely) and the common characterFX, Milkshape, Ulitmate Unwrap tools. But, I lack good experience in this area.
About the lights, vertex lighting is a must in my book. As for glLights, I think the engine should have access to lights & materials just as easy if you were programming with them directly via OpenGL. I haven't seen the volumetric lighting demo you've done. If it can be added to the engine with ease then go for it... or if it's to "customized" to simply put into the engine, then you could share it as a demo example to show how to use the engine to make it work for you.
Those are just my thoughts. I would like to hear more from various other people also.
I'm off... I'll look more into the code provided tommorrow. Thanks for getting this started for us, Josh. This should be fun to be part of.
About the file formats, "to me" this almost rides on the notion that you want this open source 3d engine to be totally customizable. So, I would think it would be better to later create add-ons to load/save various 3d file formats if so desired. In this case, people here know blitz. Why not just get something we are more likely all somewhat more familiar with, the .b3d format. That will give us d'em bones to animate. The modelling & animation tools I have are gameSpace( currently does .md2 & md3 well supposely) and the common characterFX, Milkshape, Ulitmate Unwrap tools. But, I lack good experience in this area.
About the lights, vertex lighting is a must in my book. As for glLights, I think the engine should have access to lights & materials just as easy if you were programming with them directly via OpenGL. I haven't seen the volumetric lighting demo you've done. If it can be added to the engine with ease then go for it... or if it's to "customized" to simply put into the engine, then you could share it as a demo example to show how to use the engine to make it work for you.
Those are just my thoughts. I would like to hear more from various other people also.
I'm off... I'll look more into the code provided tommorrow. Thanks for getting this started for us, Josh. This should be fun to be part of.