Most likely the cswin32libs package is not correctly installed, or you didn't install the version suited for CS 1.2.1.
Try reinstalling it, either from scratch or perhaps using the Start menu entry.
It could also be that you missed some step when setting MSVC up.

Hello,

  as far as I know, modifying terrain2 mesh at run time is not so easy (since it uses heightmaps), but might be feasible.
Try catching thebolt on IRC (#crystalspace @ chat.freenode.net), he should know better

Hello,

  I think iPolygonMesh was deprecated then removed in favor of iTriangleMesh.
You'll find some new triangulate stuff in include/csgeom/triangulate3d.h.
See apps/tests/tri3dtest/ for code using it.
For some more informations about this, try catching Scott Johnson (alias jwir3)
on IRC or write to CS user mailing list...

I guess there's a space character in CS path which is not correctly handled...
Try moving CS somewhere like C:\dev\CS (any path without space in it).

Just a guess, maybe there's some invalid object, and/or a bug in dynavis.
If you're using CS 1.2, try with a more recent version like 1.4 SVN branch
(see http://www.crystalspace3d.org/trac/CS/wiki/Version14Plan ).
If you're using 1.4 or trunk/1.9 already, please create a ticket on CS Trac,
and it's best if you can provide code+map so that the problem can be reproduced...

You should have a look at the (old, unmaintained) QT plugins from CSExtra repository,
which I think do about the same as the wxWidget plugin which is included in CS (see wxtest),
but for QT:
http://www.crystalspace3d.org/trac/CS/browser/CSExtra/trunk/plugins

Generally speaking, you need to use the appropriate method from the propertyclass used
for the camera and/or actor movement. In the case of walktut, it's iPcLinearMovement,
and you'd need to use GetPosition() or GetFullPosition().
http://www.crystalspace3d.org/cel/docs/online/api/structiPcLinearMovement.html
For the camera, it would be iPcCamera::GetCamera() then iCamera::GetTransform ().GetOrigin ()

Hi,

  does that work better ?

 <sounds>
    <sound name="tada.wav" file="/std/data/tada.wav" />
 </sounds>

Note that doesn't "play" the sound, it only loads it and assign it a name, so you can find and play it from code (no need to load the file beforehand)...
If you use CEL and pcsound property class, you might be able to play it, but then it all depends on how your entity is set up (behaviour, etc.).

Hello,

  to disable automatic rendering and trigger it yourself, you'd have to use iPcCamera::SetAutoDraw(false)
then call iPcCamera::Draw() when you want.

To switch cameras, mmm, maybe look at iPcZoneManager::PointCamera(). That's just a guess tho, never tried that....

Could you check if the problem still happens with CS 1.4 branch ? ( http://www.crystalspace3d.org/trac/CS/wiki/Version14Plan )
Because it's unlikely that any fix is devised/integrated into 1.2 now...
In case it still happens, make sure you build in debug mode, to give the the debugger a chance to provide more  informations,
and consider creating a ticket on CS Track
(you should be able to log in with same account as for this forum)

Hello,

  I think the equivalent would be iRigidBody::AttachColliderMesh().
But if you really have many of them, a few thoughts:

• try to use more simple shapes like box or sphere collider when possible
• consider using Bullet plugin instead of ODE

Also, check $CRYSTAL/apps/tutorial/phystut/phystut.cpp for some physics objects creation examples...

I used the folder msvc8 and i have Visual C++ 2008
What do i do wrong?

Exactly that
MSVC 2008 is MSVC 9, while MSVC 2005 is MSVC 8.
CS 1.2[.1] has no support for MSVC 9.
Either use MSVC 2005/8 with CS 1.2.1, or use CS trunk/1.9 or the 1.4-future-stable-not-yet-released SVN branch.
You can find more informations about 1.4 SVN branch here.

As far as I know, the only way to customize graphical output when "loading"
is to pass an iProgressMeter to the iEngine::Prepare() call.
You can see an example of that in the now deprecated cslight application code,
which you can find in CS/apps/tools/cslight/ (CS version < 1.9).
Or you can browse it on Trac.

I think that topic was discussed in the past already, and the weak point of the wiki is keeping it up-to-date.
Even without API, some of the tutorials on the actual wiki are sometimes quite outdated,
and/or the CS version they cover is not even mentioned, thus leading to confusion.
Maybe some automation could be done, but I'm not sure anyone has time for that.
But the point remains, more examples, and more practictal ones, would be good...

This manual chapter would be it