# OpenGL 3D Sphere

## Recommended Posts

Hello, I'd like to know, how can I draw a 3D sphere using triangles, supposing all I have are those simples triangle fan and triangle quad functions on OpenGL? I don't want to use glutWireSphere or any of the sort. Thanks!

##### Share on other sites
x = cos(a)*cos(b)
y = sin(b)
z = sin(a)*cos(b)

If you plug in values for a (longitude) in the interval [-pi,pi] and values for b (latitude) in the interval [-pi/2,pi/2], you'll get the corresponding points on the sphere. Now a tessellation of the rectangle [-pi,pi]x[-pi/2,pi/2] will be converted to a tessellation of the sphere.

Does that help?

##### Share on other sites
The method just suggested was the typical method of generating a sphere. It has the advantage of being very simple, but it has the disadvantage of not having a uniform distribution of verticies. This means that depending what direction you look at it (for a given triangle count) it looks more or less round. You can trivially render it be drawing the "poles" with triangle fans, and every lattitude band with a triangle strip. this corresponds to a triangulated rectangular grid, with the exception that the top and bottom strips have no "diagonal edge" meaning they'd look like rectangles, except the top and bottom edge correspond to the poles and are degenerate (ie those edges are points).

Depending on your requirements, you may want what is sometimes called an "ico sphere" or a geodesic sphere. One can calculate the vertex locations be starting with an octahedron (or a tetrahedron) whose verticies lie on the surface of the sphere you wish to render and subdividing each triangle into four by adding a vertex at the centre of each edge (and connecting them to form new edges). The location of these new verticies is constrained to lie on the surface of the sphere you are rendering. For a given sphere radius this defines a one parameter family of tesselations with uniform distribution of verticies throughout the surface. This compares to the previous method which describes a two parameter family (number of lines of longitude and lattitude) which is vertex heavy near the poles. By contrast the ico/geodesic sphere has no (mathematical) poles though clearly there is a top and bottom point determined by the original figure (in the case of an octahedron these are the top and bottom points, and for the tetrahedron, it's the top and bottom points of the first subdivision).
Hope this helps,

Dan

##### Share on other sites
Could you explain better about the whole rectangle tesselation thing? I didn't understand. I know what tesselation is (dividing geometric figures in triangles) but not what [-pi,pi]x[-pi/2,pi/2] is. Also, OpenGL coordinates start from (0,0,0) right So I should do a translation of those angle limits (a and b) if I want the sphere to go to the middle of the screen?

##### Share on other sites
Yet another way is to make a "normalized" cube; i.e. draw a cube, normalize its vertices to one, then split each face quad into four quads by adding a point in its center. Normalize each added point and repeat for each quad down to the level of subdivision you require. This works well if you want to fake cube mapping, and the vertex distribution is nice. Of course the normalization makes it slow for drawing immediately, so make sure you only create it once and store the verts somewhere.

##### Share on other sites
What I would do is download a free 3D program like blender or trueSpace light and use them to create a sphere. Export it out into a raw file format that have all your vertices. Import that into your program and render away! If you need to change the size of it, just use the scale operation.

## Create an account

Register a new account

• ### Forum Statistics

• Total Topics
627767
• Total Posts
2978991
• ### Similar Content

• Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
So, here's what the plan is so far as far as loading goes:
Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!

• I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks

• A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

-What I'm using:
C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.
-Questions
Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.

• 11
• 10
• 10
• 23
• 14