Dear CS developers and users:
I am having trouble saving my character's meshes to an XML document node. I attempt
it through the csSaver plugin with it's SaveRegion() function. It saves many of the current
sectors meshes, but when it comes to one of my player's meshes, then it hangs. Particularly, it's his base mesh which is of the csNullmeshObjectType. It is only there to
provide a common handle for his other meshes. They are children of this base mesh. They are visible while it is not. Do you understand? This is the error that comes up when csSaver tries to save it
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb79d46c0 (LWP 6091)]
0xab930148 in construction vtable for scfImplementation1<CS::Plugin::SprCal3d::
csSpriteCal3DMeshObject::MeshAccessor, iRenderBufferAccessor>
-in-CS::Plugin::SprCal3d::csSpriteCal3DMeshObject::MeshAccessor () from
/usr/lib/crystalspace-1.4/sprcal3d.so
isn't that weird considering that the mesh being saved is not a Cal3D mesh? I found the
exact line on which the error occurs via a debugger; it is in csSaver::SaveSectorMeshes()
line 853, that is, scfQueryInterface<iFactory> (meshobjectfactory->GetMeshObjectType()).
It does fine getting the mesh object type, but right as it queries that iFactory interface,
then it suddenly starts talking about that Mesh Accessor. I looked at the nullmesh header
and source file and there isn't even a nested Mesh Accessor class within a Nullmesh mesh object like there is in a csSpriteCal3dMeshObject. Do you know what is causing this?
Hoping for help,
Stewy P.
I am having trouble saving my character's meshes to an XML document node. I attempt
it through the csSaver plugin with it's SaveRegion() function. It saves many of the current
sectors meshes, but when it comes to one of my player's meshes, then it hangs. Particularly, it's his base mesh which is of the csNullmeshObjectType. It is only there to
provide a common handle for his other meshes. They are children of this base mesh. They are visible while it is not. Do you understand? This is the error that comes up when csSaver tries to save it
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb79d46c0 (LWP 6091)]
0xab930148 in construction vtable for scfImplementation1<CS::Plugin::SprCal3d::
csSpriteCal3DMeshObject::MeshAccessor, iRenderBufferAccessor>
-in-CS::Plugin::SprCal3d::csSpriteCal3DMeshObject::MeshAccessor () from
/usr/lib/crystalspace-1.4/sprcal3d.so
isn't that weird considering that the mesh being saved is not a Cal3D mesh? I found the
exact line on which the error occurs via a debugger; it is in csSaver::SaveSectorMeshes()
line 853, that is, scfQueryInterface<iFactory> (meshobjectfactory->GetMeshObjectType()).
It does fine getting the mesh object type, but right as it queries that iFactory interface,
then it suddenly starts talking about that Mesh Accessor. I looked at the nullmesh header
and source file and there isn't even a nested Mesh Accessor class within a Nullmesh mesh object like there is in a csSpriteCal3dMeshObject. Do you know what is causing this?
Hoping for help,
Stewy P.
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
