What do you mean by objects made with 3dws ?
Do you mean the brushes that you use and apply csg too, to make models from, usually for rooms and buildings and things ?
Does the problem affect other meshes(.x models) that you are loading from 3dWS ?
Im not sure, perhaps there is a problem in the way the object is being interpreted by GDK in relation to its bounds. But that would be the answer I think, you would need to recalculate the objects bounds, sparky's has a command to show the object's collision bounds, I cant remember it off the top of my head but if you turn that on, and also dbShowObjectBounds, you will get an idea of how the object is behaving, you may need to setup the bounds manually if you cant get it to recacl it normally..
One way to force GDK to recalc bounds is to make a mesh from the object, delete the object, then make a new object from the mesh and delete the mesh, its slow though and inefficient, but it works, code would looks somethnig like : (using object 1 as an example)
dbMakeMeshFromObject(1, 1); // make mesh 1 from object 1
dbDeleteObject(1); // delete object so we can make a new one
dbMakeObject(1, 1, 0); // make new object 1 from mesh 1
dbDeleteMesh(1); // delete the mesh
I know there is a command in DBPro for recalculating an objects bounds, but im not sure if it is included in GDK or not(I havent looked thoroughly, but i havent seen it in the GDK headers)
You would need to experiement with where you added that code in though if you used something like it, try putting it just after the object is loaded/created and before anything else if you can, but if doing that affects the way your level looks, then putting it after all of the positioning has been done would be best.
I havent actually had a problem like this though heyufool, so im just givin u some ideas you could try to fix it...
Good Luck
If it ain't broke.... DONT FIX IT !!!
