AttachColliderMesh() is still the same; it expects collision polygons to exist in the mesh

My mistake, I thought you were using irigidbody.AttachColliderMesh() not what I had in mine.
My example does seem to work for normal genmeshes though, and having an icollider beforehand or not makes no difference, but I don't know what the collision polygons are. Also my example probably doesn't compensate for any moving of objects after the setup.

I don't understand everything you are saying, but I do have an example from my own app that initializes all meshes in a list to be static physics objects. I add any rigid bodies after.

Ignore the icollection part if it's a problem.
One change I need to make to it is to check if each object was set to have no collider, and ignore it if so, but I don't know the place to check that yet.


   iCollection *cl = engine->GetCollection(regio.GetData());   
   iMeshList *ml = engine->GetMeshes();
   for(int i = 0; i < ml->GetCount(); i++)
   {
      if(cl->IsParentOf(ml->Get(i)->QueryObject()) )
      {
         dynSys->AttachColliderMesh (ml->Get(i), ml->Get(i)->GetMovable()->GetTransform(),
            friction, restitution);
      }
   }   
         
}

There are different ways with different benefits. Vertex colors for example, I think they can be set with iMeshObject.SetColor()? Those only work with a shader that reads them, like std_lighting. You could also change the texture it's self, like by drawing on it. You could just modify any shader to use a custom value.

well I was trying to explain that cellstart is already compiled, it is basically CS with cell and python or something (I'm not sure exactly don't have it right now).

 you seem to be saying you installed the win32 libs thing in the middle of the process. I can't tell you exactly what went wrong without seeing error messages etc.

If you've used C before you should be able to download CS and compile it, (it is C++ though). That's where I would start.

CS comes with documentation to answer that, you can also go to the CS homepage and click documentation.
CEL is not required I was showing you wat it said about cellstart, which does not need to be compiled. See the main page for that too.

there are functions in the API Docs that can change the screen size or change to full screen, at least that how I understood it. To change to the exact screen size when peope may have different screens I'm not sure, but if you can figure how to fetch the screen, not window, resolution that may do it.

like do I get a bunch of exe files (or at last one?) o.0?

yes the main cs folder will have multiple .exe files and .dll files (windows) if compiled fully.

Python is supported, and if you want to get straight to using it with Crystal Space and the features of Cell use     CELstart   - is a CEL-based environment for self-contained game packages, allowing easy game creation via scripting, thereby making the development process easier for those less proficient with C++. The package nature of games also make distribution simple.

That is on the crystalspace3d.org homepage

compiling is good too though since you will want that skill eventually.

Well, do you know how to use the c++ programming language, and if not, do you want to learn? There are ways to learn that seperately from CS which would be best. There are also other posibilities, you could try to use the scripting languages that are supported, and you could use CellStart for that, I don't have much more info than that off the top of my head.

To answer about compiling, it requires a compiler software, and that converts the text code into executable files etc.

I found several files http://b2cs.delcorp.org/examples/character/

It did work (I don't know how well) with "run" but not viewmesh when I tried.
It seems like these meshes need the character type shader(s) set in the material, so check that.

Same with most features they are working on I think, but they do mention some things in their mailinglist archive.

http://sourceforge.net/mailarchive/forum.php?thread_name=17ed71ca0803051651x3694e7d1p6d7e051ca3c4126%40mail.gmail.com&forum_name=crystal-develop

basically you should plan for the new animation system they have mentioned they are working on for crystal space, which will be available in blender2crystal

Right now, which format is best supported by the engine, I gues is what I'm going after here...

maybe jorrit or another developer can answer that.

For me, I care a lot about animation, so I developed the CAL3d plugin into my ultimate animation solution, though it still has problems, and it works specifically with the model and material system.
So it also depends on what 3d app you want and how it works, and what shaders you might want...

Bones is the way to go, the ones I mentioned are bone based.

The first thing to do is to get one of the example files from the b2cs site. When you click run, check for the same problems. If those test files work ok, then the problem is your settings in blender.

With lights, energy may not have any effect. set the color to a high value, and the distance to one that matches the scale of the scene.
With textures, is the texture visible in blender in the texture view mode? Is there a material or multiple materials assigned that have different textures set?

If you are using the default b2cs values however it should work right away...