BEPUphysics

The maximumAge is how many intervals pass before it is deleted. If one passes and the maximumAge is 0, then it will be removed- if there isn't something there actively refreshing it. Chances are this is what you're seeing; the entity that needed the triangles there in the first place is still nearby...

There shouldn't be any problems so long as you're not adding/removing dozens of entities per frame. The actual add/remove operation has a little overhead, but if you can get the update time low enough by doing it, it's definitely worth it.

Their new names are "becomeDynamic" and "becomeKinematic." Also watch out for the collision groups; this method won't automatically change the collision group of the entity to the space's default. For example, if you call becomeKinematic on a dynamic object, it will still have th...

As an example, I just ran a 240 inactive box test and it is taking 1.8 ms per frame. Taking this to 1000 inactive entities increased the time to 3.8 ms. There was a slight overhead when I had the 240 boxes floating inside a StaticTriangleGroup, increasing the time spent per frame to 2.3 ms. These te...

On the Xbox, that might be about right, but it might also be some other systems running besides entities. It also depends on how the entities are configured (broad phase still has to run on inactive objects).

When Space.simulationSettings.timeStep is set to 1.0f/30.0f, it means the engine will internally update only once every 1/30 seconds. This can be a little too infrequent for some systems like the solver, which can cause problems with constraints. The vehicle wheels may be helped to some extent by ch...

The centerPosition will not support an offset as it is intended to be the actual center position of the collision shape. Some other convenience functionality that wraps the center position is possible, but it would need to be designed in a clean and straightforward way. I'm wary of continuing the 'g...

The internal multithreading will use the threads only within the (Space).update call. After that call, you don't need to worry about it hogging any more resources. That means if you're calling update from your game's update method, you don't need to worry about using fewer processors. If you are run...

Check the multithreading demo for some example source, you can get it on the documentation page at http://www.bepu-games.com/BEPUphysics/documentation.htm. Basically, you need to give the engine some threads to work with using (Space).threadManager.add(). After that, all you have to do is set (Space...

You can indeed drop the number of iterations used by the solver using the (Space).simulationSettings.collisionResponse.iterations field. 15 is the default. It probably won't help noticeably in this situation, since as you suspect, that amount of physics should run very quickly even on the Xbox.

More information is needed to make any specific recommendations, but in general, just make sure the multithreading is running. What kind of simulation are you running? Is it a 'jiggy' lag (like those caused by garbage collection and compaction), or is it a generally slow framerate? The Xbox will alw...

There was an unprotected reference to the entity's space in the applyAngularImpulse method (called from within the applyImpulse method). The applyImpulse method shouldn't require that an entity belongs to a space and this should be corrected in the next version.

It is in world space.

Collision pairs generate contacts with the goal of supporting a collision. This means they need a good bit of information- position, normal, penetration depth, and some other auxiliary things. All of these things are necessary because the goal is more general than a boolean 'is colliding' test. Even...

The new system has the same functional capabilities as the old system in that you can make a collision group for an entity that does what the old system could do for a specific entity. It could take a bit more work to set up in some cases, but it can do the same amount (and more) when set up. For ex...