Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Given that your camera acts like in Diablo (wherever Isometric or with Perspective):</p> <p>If you have a fixed map size, you can use 1 VBO for the base geometry of your map, Assuming you will use a heightmap based solution. The Quads not visible will be discarded by your graphics card after the vertex shader, not affecting your pixel fillrate. They are not worth the overhead of culling on your side. Details like Rocks, Houses etc will have their own VBO anyways.</p> <p>If you aim for a streaming content engine with a huge seamless world, create chunks, the size of a chunk depends on your game. Divide your terrain into those chunks and test the camera frustum against their bounding boxes before drawing.</p> <p>About drawing chunks:</p> <p>The simplest way, which is <em>enough for most games</em>, is to make each chunk its own geometry, VBO, and so on. But you can optimize <em>later</em> and your terrain implementation should not drive your engine API designs (you will have to implement many different ways to draw things in your engine, for instance particles, post processing effects, etc..). </p> <p>One way you can optimize is with only one VBO for the geometry and the usage of instanced drawing, just like in particle systems you then take some other source for some of your data, like your global transformation, the height of each vertex and so on.</p> <p>But keep in mind, most games dont really need that much optimization in just the terrain. There will come other systems across your path more worthy of optimizations.</p>
    singulars
    1. This table or related slice is empty.
    1. POFrustum culling with VBOs
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USVengarioth
    1. USVengarioth
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POFrustum culling with VBOs
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO`The Quads not visible will be discarded by your graphics card after the vertex shader` Is that only for the quads that are not facing the camera (backface culling) or are the ones outside of the frustum culled as well? Also, I wanted to check about the chunks - each chunk contains some tiles, and each chunk is allocated one VBO. Each chunk also has a bounding box which is used in the frustum culling. Are my assumptions correct?
      singulars
      1. PO
      1. USBodwin
    2. COYes, not only the backfacing quads will be discarded, but WHEN actually differs from implementation to implementation, nevertheless it is one thing you should not bother optimizing for. And yes, your assumptions are correct, but i will elaborate a bit more on that in my answer.
      singulars
      1. PO
      1. USVengarioth
 

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