You can still use Radiant, but I'd recommend Blender. I'm not sure how much the Radiant->CrystalSpace converter is even maintained any more.

I don't want to feed a flame war, but I think a lot of people who are new to application development have these misconceptions.

From my perspective, the documentation and tutorials were the main reason I started using CrystalSpace. Community documentation and the manuals are relatively straightforward, and I had a simple polygon rendered in a custom-made CS app within a couple of days. Bear in mind this comes from a guy who makes a living doing J2EE programming... but with the CS templates, header organization and object-oriented design I was able to get up and running in short order.

From the perspective of my hardware, CrystalSpace does a great job of rendering high-poly models very efficiently. While the engine definitely favors few high-poly models over many low-poly models, once you have visability culling, textures efficiently generated and sectors adequately defined the engine is great.

I definitely didn't have to read the whole API documentation to understand how the introductory tutorials worked - it was fairly common sense. This event-driven model has been used since the days of LaMothe's Mode-X engines, and carries on to today.

If you're having problems understanding the documentation or Crystal Space, I highly recommend taking a step back and instead learning some fundamentals of C++, data structures and object-oriented programming. Until you've written your own hashmap implementation or blitted a few pixmaps to a buffer, you really can't appreciate how easy CrystalSpace makes things.

Okay... Eric needs a new computer... BADLY.

Methinks you are talking about cel shading... I *thought* there was a render plugin for that... but it may have been a while ago...

At http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=37 you can read through a tutorial that implements cel shading in OpenGL...

Another thing to check:

• Do you have an older (or remnants of an older) version of CrystalSpace, cal3d or CEL installed somewhere?

Nope, just one renderer. But that wouldn't influence your sound engine choice.

[Things to check before you post:]

Things to check before you post:

• Did you set the CRYSTAL and CEL environment variables correctly? Can you `cd` into them? CRYSTAL and CEL need to be set when running external apps.
• What version of Crystal Space / CEL are you using? CVS or stable? Bear in mind CVS usually has most problems licked and most bugs ironed out, but it does go through rough patches at times. Use the -D parameter to CVS to back up a day at a time if you're hitting some compile-time errors or are looking for more stable versions with the most recent bug fixes.
• In Windows, did you install MingW first and then MSYS? Are you sure? MSYS has to know about MingW at install time.
• Are you using GCC 4.0? It's crazy. Try backing up a version.
• Last, but not least, have you read the documentation (at least up to the tutorials) and read thru some of the community articles? They're located at http://www.crystalspace3d.org/tikiwiki/tiki-index.php?page=Documentation and http://community.crystalspace3d.org/ , respectively. Give 'em a read. You'll be glad you did.

Along the same lines - I've been running `make install` with different prefixes for a while now on Linux. One debug, one optimized and one bleeding edge CVS. That way the IDE just changes the CRYSTAL and CEL env. vars. and I can switch CS + CEL bases on the fly. Seems to work well thus far.

Also a good article about producing independent game titles:
http://www.gamasutra.com/features/20050721/pfeifer_01.shtml

For me, the two best reads were:

Sloperama's game biz advice:
http://www.sloperama.com/advice.html

Also from Raven Software:
http://www2.ravensoft.com/getajob.htm

I don't believe snapshots exist since it's still in heavy development. To my knowledge, the best way to get it is via CVS, as detailed at http://www.crystalspace3d.org/tikiwiki/tiki-index.php?page=Crystal+Core+Running

Option #3, definitely. Go fullbright with everything, ditch lighting information. I use the software mode mostly for debugging, so this would be perfect.

Agreed - I don't use it in any final builds but I use it extensively when developing. When doing code tweaks for things that are non-model related (i.e. camera angles and the like) I'll use the software renderer. Easy to use for multi-monitor support, sometimes exposes model glitches that are hard to see with hardware rendering, etc.

That said, multi-monitor hardware rendering is becoming more practical as driver support becomes more robust (thank you nvidia) and 3d rendering is becoming standard on even low-end laptops. Once Vista comes out everyone and their mom will have a GeForce 7800, which will make the software renderer even more moot.

Still, I think the software renderer has its place. Being able to run your CS app on five year old hardware is nice.

Now I'm arguing with myself. Nice.

It does look like Blender's exporter changed between versions. The tutorial uses a later version... so you might want to use the separate python exporter... or downshift to 2.35. I'll probably update the tutorial accordingly.

Do an ls - I'm pretty sure what you need to run is ./configure.sh