I'd recommend Blender - www.blender3d.org. It's what is currently being used to develop the Crystal Core demo.

And appendix of the tutorial has been Wikized - the CS GtkRadiant tutorial has been posted.

Didn't post a thumbnail for it, since I didn't want to use Radiant artwork w/o the group's permission.

I'll stick to the project's icon for tutorials then... coming up is

The first two sections about map building have been submitted to the Wiki site. I've included the full-size version of all the images, so that may help.

Cal3d avatar portion should be forthcoming.

You beat me to the punch on tutorials for XML world formats! I just submitted one. Sans photos, of course. My Blender one was submitted as well however - which should complement the XML one well.

Also working on submitting the Cal3d tutorial (which is much longer)

Does one need to start an article before they post to the tutorial gallery? The only one I can seem to submit to is the shader gallery (which is quite nifty, BTW)

Both, really. Nothing necessarily complex... just building a very elementary shader from scratch and applying it to a material, then applying the material to a simple mesh (i.e. a silly shader that changes the original color of a cube). I think demonstrating how easy shaders can be is a good illustration of CS.

A shader howto would be uber-nifty.

I'm not sure how many Python examples there are, but there are a few scripted demos in CS (i.e. demo and pathtut).

A new architecture was prototyped, but I haven't seen any new implementations. The idea was to have a common interface for UDP,TCP and IP messages, but this turned out to be fairly complex. UDP implementation was the big thing (to keep things low-latency), but it's not easy.

Really I think the key would be to start with a good UDP datagram layer and go from there. Kinda reiterating previous responses, I hear the SDL network layer is fairly good at that (many deathmatch games ported by Loki )

My word that's a big terrain map.

Do you know if there is anything that can be done to help load times on the Wiki page? Is the hardware just getting hammered?

Which images need to be expanded/reframed to be more clear? Some of them, especially the Blender screens, are tough to frame because they're bigger than the page size yet scaling them down kills detail. Let me know which images need better detail/resolution.

Also I'm rewriting portions to cover Blender 2.35 since the Cal3d exporter appears to be operational and now you can have (THANK GOODNESS) relative paths stored for external resources (i.e. texture maps).

Just deleted 20 pages demonstrating how to build a beginner application... sticking to building models & maps for now.

I know it was broken with 2.34 - I'll check with 2.35. It would be a real lifesaver to have the relative pathnames feature introduced with 2.34 included - especially in a tutorial where packaging .blend files statically linked with absolute pathnames can be confusing.

Thanks!

I'm re-writing an older tutorial I'd written using GtkRadiant and Blender to instead use straight Blender. Revisions are being posted at http://www.cs.indiana.edu/~joellis/ - currently it covers cal3d skeletal animation, map design and object file layouts.

Feel free to comment on what's clear/unclear - newer versions will be posted on occasion.