Real-Time Physics Simulation Forum 2006-06-22T14:49:20+00:00 https://pybullet.org/Bullet/phpBB3/app.php/feed/topic/375 2006-06-22T14:49:20+00:00 2006-06-22T14:49:20+00:00 https://pybullet.org/Bullet/phpBB3/viewtopic.php?p=1209#p1209 <![CDATA[Minimal object size]]>
In the latest preview 40, there is a setMargin, which allows you to play with per-object margin settings.

You can try to set the margin for static objects closer to zero (0.01) and
for make margin smaller for small dynamic objects.

If you experience missing collisions (the ccd should fix this, but it is work in progress), use smaller timesteps:

in python:

PhysicsConstraints.setNumTimeSubSteps(numSteps)
numSteps = 0 -> no simulation (good to pause just the simulation)
numSteps = 1 -> default
numSteps > 1, subdivide the timestep, higher accuracy, support for smaller margins. So if you halve the collision margin, you can try to double the numSteps

See also:
http://www.continuousphysics.com/mediaw ... in_Blender

Erwin

Statistics: Posted by Erwin Coumans — Thu Jun 22, 2006 2:49 pm

]]> 2006-06-18T18:17:28+00:00 2006-06-18T18:17:28+00:00 https://pybullet.org/Bullet/phpBB3/viewtopic.php?p=1189#p1189 <![CDATA[Minimal object size]]> Statistics: Posted by bmud — Sun Jun 18, 2006 6:17 pm

]]> 2006-06-18T18:20:08+00:00 2006-06-18T18:13:07+00:00 https://pybullet.org/Bullet/phpBB3/viewtopic.php?p=1188#p1188 <![CDATA[Minimal object size]]>
There are restrictions when using Bullet collision detection and physics, and minimum / maximum object sizes are one of them. This might improve in the future, but for now you have to work within the limits.
Other restrictions are using large mass differences: don't put a heavy box on top of a light one, it will go wrong.

There is no FAQ yet, but this should be one of the first items to note.

- for dynamic moing objects: no small objects (minimum 0.15 units), no very large objects (> 10 units)
- don't mix very heavy and very light objects in the same simulation
- 'Apply' the scaling/size to the mesh/model

Statistics: Posted by Erwin Coumans — Sun Jun 18, 2006 6:13 pm

]]> 2006-06-18T18:16:02+00:00 2006-06-18T16:50:14+00:00 https://pybullet.org/Bullet/phpBB3/viewtopic.php?p=1187#p1187 <![CDATA[Minimal object size]]> this post I found via the google search, and somehow I ended up here... for all those confused.[/edit]

I agree. This is a problem that has just recently become very problematic for me. I'm making a marble game. How big is a marble? About TWO centimeters for a large one. Okay, so it's not really marble sized. It's more about the size of a bowling ball. That's within the 20cm limit but the margin is very visible and is making level design difficult. What if I was making a bowling game; or tennis; or worse, golf? If I make everything too big, objects seem to just have too much weird momentum problems like they're underwater. On top of that, making worlds bigger revives a problem that the BCGP team had while working on the underwater racing game. blender's graphics engine has a crummy z-buffer and edges start getting blocky on larger scales.

To get to the point, my game worked without any complaints before last night. I decided to scale everything down to a "real world size" since the blender units are being used as meters. Now the ball runs into objects before its touching them, and it doesn't reach the floor... :( I too would like to scale my margins or suggest that the engine have them scaled as such by default.

http://www.osysi.net/projects/blender/m ... gins.blend

Statistics: Posted by bmud — Sun Jun 18, 2006 4:50 pm

]]>