Sign in to follow this  

OpenGL Half cylinders?

Recommended Posts

GeoLancer    122
Hi everyone! I am new to opengl and was wondering how exactly do i draw half a cylinder in opengl? I was doing it the rudimentary way like this: for( float j = 0; j < 500; j++ ) { glTranslatef( .005, 0, 0 ); glBegin( GL_POLYGON ); for( float i = 0; i < 360; i++ ) { float angle = (i*3.14)/360; glVertex3f( 0, cos(angle)/2.5, sin(angle)/2.5 ); } glEnd( ); } Meaning i was drawing about several hundred half circled polygons reall close to each other to fill up the gaps, thus creating a half cylinder. Ofcourse, this caused too much cpu consumption, i.e. LAG, so now i have no idea. Can anyone help me,please!!! thnkx

Share this post

Link to post
Share on other sites
haegarr    7372
First, please post code snippets in a special container by surrounding [ source ] and [ /source ] (but without the inner spaces). That enhances readability since it e.g. preserves indentation.

You should not render a stack of half circles to apprimate a cut cyclinder. Instead, split up the surface of the half cylinder into several surfaces, and draw them one-by-one. There is a top and a buttom cap, both a half circle. Render them similarly as you've done the stacked half circles before. Then there is the half "mantle" (I don't know the correct word in english, sorry) and the flat closing of the "mantle".

Use something like the following (notice that this is untested code and for explanation only):

int STEPS = 16;
float DELTA = 3.1415/STEPS;
float half_height = 10f;
float radius = 2.0f;

// rendering of top cap; one corner per iteration
for(int step=0; step<=STEPS; ++step) { // notice the <=
float angle = step*DELTA;

// rendering of bottom cap; one corner per iteration
for(int step=0; step<=STEPS; ++step) { // notice the <=
float angle = step*DELTA;

// rendering of "mantle"; one quad per iteration
for(int step=0; step<STEPS; ++step) { // notice the < only
float angle1 = step*DELTA; // at this angle the quad starts
float angle2 = (step+1)*DELTA; // look ahead of next angle: at this angle the quad ends
float rsine1 = radius*sin(angle1);
float rcosine1 = radius*cos(angle1);
float rsine2 = radius*sin(angle2);
float rcosine2 = radius*cos(angle2);

// rendering of closing of "mantle"

See that there are quadrangles rendered along the axis where your solution has the stacked half circles. So the "gaps" are closed totally but with much less effort. You may increase STEPS if you want the surfaces to become more "rounded".

( BTW: There are some general optimizations made as well. Using the pre-increment (++i) is a little bit more efficient than using the post-increment (i++). Furthurmore, repeated computations of the same sine or cosine are supressed, and also multiplication is preferred over division. However, you could ignore this if you want. )

EDIT: some minor bugs in the explanation code corrected, and comments made more verbose.

[Edited by - haegarr on November 12, 2005 6:46:32 AM]

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now