Databases
StackOverflow2013
Postsdbo
POBullet Physics Strategy for (infinite) scrolling track like terrain
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBullet Physics Strategy for (infinite) scrolling track like terrain
    primarykey
    data
    text
    <p>I’m trying to find what options we have in Bullet to achieve a scrolling track like terrain where the terrain segments (or tiles) are reused once they scroll out of view.</p> <p>In 2D engines such as Box2D and Chipmunk I would lay out static collision bodies with segment shapes or polygon shapes, repositioning them once they are out of view. Here’s a link describing this being done in the ActionScript version of Box2D: <a href="http://www.emanueleferonato.com/2011/10/04/create-a-terrain-like-the-one-in-tiny-wings-with-flash-and-box2d-%E2%80%93-adding-more-bumps/" rel="nofollow">http://www.emanueleferonato.com/2011/10/04/create-a-terrain-like-the-one-in-tiny-wings-with-flash-and-box2d-%E2%80%93-adding-more-bumps/</a></p> <p>Looking through some of the documentation, it seems like in Bullet we have multiple options for the shape, like btHeightfieldTerrainShapes or btStaticPlaneShapes or btBoxShapes. In addition I also looked at the AppConcaveDemo in the demos that come with BulletPhysics, and I saw that it’s using a btBvhTriangleMeshShape and the vertices are being recalculated. Would maybe this be the better option?</p> <p>Looking at these different options, I’m wondering if there are any thoughts on how to best achieve something like this keeping in mind that the terrain scrolls horizontally, similar to the game TinyWings and should be narrow as a HotWheels car track.</p> <p>I’m not looking for a detailed technical implementation, but rather a discussion of the merits of one technique over the other, being performance the primary consideration.</p> <p>Note: Not sure it’s worth mentioning, but this terrain would interact with both rigid and soft bodies.</p> <p>Thank you,</p> <p>Claudia</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USClaudia
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POBullet Physics Strategy for (infinite) scrolling track like terrain
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIs the terrain generated programmatically, or loaded once at the beginning of the game/level? in the firt case you could use Kinematic bodies (http://www.bulletphysics.com/ftp/pub/test/physics/Bullet_User_Manual.pdf page 26), in the second case the image at page 18 should help to clarify
      singulars
      1. POBullet Physics Strategy for (infinite) scrolling track like terrain
      1. USrraallvv
    2. COIt would be generated programmatically. And it seems what you replied about the kinematic bodies, is a hint towards using primitives (such as a btBoxShape).
      singulars
      1. POBullet Physics Strategy for (infinite) scrolling track like terrain
      1. USClaudia
    3. COyou can use btBoxShape for straight roads, and btScaledBvhTriangleMeshShape for curves like is depicted [here](http://postimage.org/image/72b9kg7gd/)
      singulars
      1. POBullet Physics Strategy for (infinite) scrolling track like terrain
      1. USrraallvv
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload