Recent Posts

me too, that's 1up for phsx

I like the fact that one supplies a density for creating an actor object, rather than a mass.
Densities for different materials are easily available......whereas the mass of an object of a certain size and material is not so readily on hand, and will, anyway, require the user to calculate the mass using the object's density and volume.

hi Allan, no problem, at present I haven't found any decent documentation on that. all I know is the final mass is calculated based on density and shape. however it is possible to set the mass directly which will overide the density, I'll make a function for that when I'v got some time.

but simply: cNxActor->setMass(0.0f - infinite);//actor must be dynamic

//setMass() does not update the inertial properties of the body, to change the inertia tensor
//use setMassSpaceInertiaTensor() or updateMassFromShapes().

so large values aren't really a problem. at the moment only trial and error will see if the bodies act appropriatley with those real world values.

Great update,Gene........Thanks.

Just a question on density values that you are using:
PhysX is based on MKS (meters,Kg,sec) system, which means that density values, as we generally use them (which is g/cm3) must be converted to Kg/m3 by multiplying by 1000.
i.e. Water (1g/cc) becomes 1000 Kg/m3
Iron (7.86g/cc) becomes 7860 Kg/m3
Gold (19.3g/cc) become 19300 Kg/m3
Wood (0.5g/cc) becomes 500 Kg/m3

This leads to some extremely high values being used for forces if real life materials are being simulated......do you agree? Are you using kg/m3 density values?

added an updated .zip attached to first post.

update 1.1 :
                  more/improved actor functions
                  3 more actor creation functions for creating a primitive with local location and orientations.(great for making ragdolls)
                  fixed convex shape mesh from .x file. (wasn't creating the collision shape from the .x file correctly)(just remember 256 triangle limit
                  with convex shapes)
 

Hey ho

HI!

no problem, sorry I couldn't be more help  .

hi genetransfer.
thank you very much for your help.
I'm not using physx, because I have no time to understand it.
I found that form, and you are right there aren't speed benefit from memory function.

thanks again.

hi mf, firstly if you are going to use physx forget about all the BODY* stuff. NxActor is the way to go.

if your not useing physx, and just useing 3Impact standard functions then you can call body functions.

as for create from memory, I haven't seen any speed benefit at all from memory functions at least with an old test i did with skinmeshes (which is somewhere on the forums you 'll have to search for it) and bodies load very fast anyway. I myself haven't used the body memory functions but I dare say would be similar to the skinmesh except without haveing to worry about textures.

if you hunt down create skinmesh from memory on the forums that will be your best resource, it was many moons ago scince I thought about useing them  and I can't remember exactly, there was also a a bit of code exaviour did for loading a mesh from memory which looked useful aswell. so hunting that one down aswell might be helpful.