Sign in to follow this  

OpenGL OpenGL on MacOS X

Recommended Posts

ChristophR    122
Hi! I have already asked something about this topic last week. Somebody postet a link to an Apple example project. This example worked well, but it was too complicated. I didn't want to see how to work with OpenGL, but I just want to get OpenGL started. I do already know how to use the API, my problem is just that I do not know how to create an OpenGL window with Carbon. In the meantime I have written a test project. It initializes OpenGL (it sets the pixel format and such things. I think this part of the project is correct, since I copied it from a tutorial). But now I have troubles with my event loop. I have written the following code:
bool running = true;
while  (running){
   aglSwapBuffers (context);

   ReceiveNextEvent(0, NULL,kEventDurationNoWait,true, &theEvent);
   SendEventToEventTarget (theEvent, theTarget);
I just wanted to render an empty scene with a red background while the program should still process events from the event loop. But the code above does not work very well. When I start the program I see an empty window at first. After about 10 seconds the window gets a red background. This is exactly what I expected, it just takes too long. Additionally, the program makes my whole system very slow. But I don't know what I made wrong: the loop should render the frames as fast as possible. Does anybody have an idea? Thanks in advance. rgds.

Share this post

Link to post
Share on other sites
RichardS    298
This is a question about Carbon, and not about OpenGL. A more appropriate place to ask this question would be the Carbon-dev mailing list at

Share this post

Link to post
Share on other sites
hammackj    116
Nehe has a Objective C, Xcode example. If you use glut you can do it in c or c++ really easy. I am fairly new to OSX programming and from what i can tell Carbon is dying...correct me if i am wrong.


Share this post

Link to post
Share on other sites
MARS_999    1627
Original post by hammackj
Nehe has a Objective C, Xcode example. If you use glut you can do it in c or c++ really easy. I am fairly new to OSX programming and from what i can tell Carbon is dying...correct me if i am wrong.


Carbon isn't dead but you might as well get used to using Cocoa on Mac for its Apples baby and might have more support or updates than Carbon for Carbon was made to help move OS9 apps to OSX faster than recoding them all. Cocoa really is nice to use and to setup OpenGL is easy with Cocoa. Making a editor in IB with Cocoa is like butter...

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