Trouble with objects imported from Blender

[chandlerprall]

Trouble with objects imported from Blender

[tapio]

Try setting smaller gravity, to see if the going through is because of too high velocity, though I it's kind of a long shot.

Also, __dirty* flags are needed only if you set position/rotation after adding to the scene, so unnecessary here.

But after reading the Wiki section "Why can't I scale objects?" I scaled the object in Blender and exported it so I could remove the scale.set line -- (It does make working with the objects in Blender a bit of a pain, if there is a different approach that you know of, that would be great.)

In latest version of Physijs, scale should be honored when adding the object to the scene (but not afterwards). You can also use the Blender exporter's Scale option which will leave the .blend intact but scale the exported object. Third option is to manually fiddle with the "scale": 1.00000 line in the exported model .js file.

[bberryhill]

Thanks much tapio for the insight on __dirty* flags and scaling. I'll definitely but that info to use.

I tried changing the y gravity from -60 to -5 and the z from 10 to 0. The ball is still passing through the Blender object and hitting the ground.

With the other ball hitting something that isn't visible when it should fall directly to the ground, it seems that the physics object for the Blender object is in a different position than the blue visible Blender object.

Does that seem like a possibility? Any ideas how I should get the non-visible physics to line up with the visible Blender object?

[tapio]

It seems to me that your object is not centered. For physics objects, it's usually a good idea to have the center of mass of the object be at (0, 0, 0), to make rotation behave as expected (actually any object that is going to be rotated should probably be centered around at least some of the axes). There is an align option in the Blender exporter to do that for you automatically. Try that.

[bberryhill]

Thanks much tapio. Using the align option in the Blender exporter looks to have worked. I've uploaded the fix to my previous link.

Thanks for your time. Much appreciated.

[chandlerprall]

Thanks @tapio

Wiki has been updated to reflect the recent changes.