*******Test for Cal3d and CrystalSpace*******
This is version 2 already of a small test program /viewer illustrating programmatic use of a cal3d model (Cally - as provided by Cal3d project) with Crystal Space. The code is a slightly modified version of the "simple1" application provided by Crystal Space.
The cal3d model is in the "cally" folder in the archive below. This is basically what we want the exporter from blender to spit out + a file similar to test.cal3d (the xml description of the model so that CS can easily use it).
There is also a bash script (and useful header.cal3d and footer.cal3d files) that helps you bridge some gaps between exporting from Blender and viewing with this viewer.
You might want to read also this post describing the whole toolchain for Blender+cal3d+CrystalSpace.
To see this working:
- make sure that Crystal Space is present on your system and that the CRYSTAL environment variable is set to it. See Crystal Space version and compilation steps on Eulora's wiki.
- make all (if it complains about cs-config you might simply need to run it again as cs-config is used to get the correct link flags)
- run ./cally3d [filename.cal3d] [animationName] . If you left the default values, you should be looking at a green naked woman walking/struting.
- - feel free to change the code to test various animations and/or load a custom model - this can easily serve to test any cal3d model for match with Crystal Space.
- code has been changed to load any specified .cal3d model and animation name using the optional parameters in the command line above; defaults there are "test.cal3d" and "strut" for the .cal3d file and animation, respectively.
23 Feb 2017
21 Feb 2017
23 Feb 2017
if your model isn't animated/doesn't load, check that you have the right animation specified in the .cal3d file. Better yet, make sure you ARE giving cally3d the filename and animation name you want and not using the defaults if they don't match what you actually have!
if your model moves too slowly/too fast/you can't see its movement check and adjust the values in the .cal3d file. The bash script makes a guess there, but it doesn't know much.