StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16674022
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-05-21T15:40:50.017
FavoriteCount
0
LastActivityDate
2013-05-21T19:06:43.227
LastEditDate
2013-05-21T19:06:43.227
LastEditorUserId
2362402
OwnerUserId
2362402
ParentId
16355707
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Don't use the old fixed-function pipeline, create VAOs and VBOs(<a href="http://www.opengl.org/wiki/Vertex_Specification" rel="nofollow">http://www.opengl.org/wiki/Vertex_Specification</a>) for your vertex attributes of each sphere. Edit: (added more basics about VBOs and VAOs) When you are rendering without VBOs, the geometry data is send each time you render a frame. Using VBOs allows you to send model data to your graphics card and then to render without the cpu-gpu bottleneck. <pre><code>glGenBuffers(1, &vboHandle); // create vbo glBindBuffer(target, vboHandle); // bind vbo glBufferData(target, size, data, usage); // send vertex data (position, normals, ..) </code></pre> then you have to establish a connection between your VBO data and shader attributes <pre><code>// get location of the in-attribute of the shader program vertexLocation = glGetAttribLocation(programHandle,"vertex"); // activate desired VBO glBindBuffer(GL_ARRAY_BUFFER, vboHandle); // set attribute-pointer glVertexAttribPointer(vertexLocation, 4, GL_FLOAT, GL_FALSE, 0, 0); // finally enable attribute-array glEnableVertexAttribArray(vertexLocation); </code></pre> VAOs are used to organize your VBOs - Usually you end up with the following problem: <pre><code>enable vertex attrib1 enable vertex attrib2 enable vertex attrib3 renderModel disable vertex attrib1 disable vertex attrib2 disable vertex attrib3 </code></pre> With VAOs you reduce the code effort to <pre><code>enable VAO renderModel disable VAO </code></pre> So a combined code fragment may look like: <pre><code>// Create and bind VAO glGenVertexArrays(1, &vaoId); glBindVertexArray(vaoId); // create and bind vbo glGenBuffers(1, &vboId); glBindBuffer(GL_ARRAY_BUFFER, vboId); glBufferData(GL_ARRAY_BUFFER, size, data, GL_STATIC_DRAW); GLint loc = glGetAttribLocation(programHandle, "attrib1"); glEnableVertexAttribArray(loc); glVertexAttribPointer(loc, 3, GL_FLOAT, GL_FALSE, 0, 0); // other vbos, attrib pointers ... // UnbindVAO glBindVertexArray(0); glBindBuffer(GL_ARRAY_BUFFER, 0); </code></pre> That's probably the minimal amount of information you'll need, I recommend to read the chapters 8 and 12 of the opengl superbible 5th edition. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POImproving performance of opengl sphere generator
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USdinony
UserOwnerUserId
1. USdinony
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThat's not false, but that's not an answer.
 singulars
 PostPostId
 PO
 UserUserId
 USCalvin1602

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.