Archived

This topic is now archived and is closed to further replies.

Facehat

OpenGL DirectDraw + OpenGL

Recommended Posts

Guest Anonymous Poster   
Guest Anonymous Poster
Sounds like two APIs...
Two different sets of code fighting for exclusive rights over your video memory and renderer.
Just go Direct3D... OpenGl and DX are merging anyway.. and DX seems to be portable to the new API that will be formed.

-DL

Share this post


Link to post
Share on other sites
NuFAN    122
Hi,
you can use both API's together, it's a bit complicated, but you can do. Many coders prefer this to change the display mode and then set it as the device context.

It depends on what you're gonna do with your programs. If you want to create portable code, use OpenGL. If you only create programs for Windows, then you should better stay at DirectX, because there are many components and if you understand one, it's not hard to understand the rest.

CU

------------------
Skullpture Entertainment
#40842461

Share this post


Link to post
Share on other sites
druid-    122
A few points:

1)
There's a very simple reason why you can't use a ddraw surface to render opengl on and still access through ddraw functions:

Microsoft hasn't written a driver model to support it.

This is the essential reason, though there can be some issues with hardware compatibility, but MS hasn't even given venders a chance to try it out.

2)
OpenGL and DX are not merging, SGI will continue to support OpenGL and a recent announcement makes it clear that they have stepped out of cooperation with MS on the low-level API.

3)
It is common practice to use ddraw to temporarily set fullscreen (for one app), since MS did not include this functionality in the Win32 API. However, I don't believe this is what TheGoop was asking about.

4)
There are many other reasons to choose OpenGL over DX than just portability. I use OpenGL, but I'm not a fierce advocate of it, try them both and make your own decision.

------------------
Scott Franke [druid-]
sfranke@usc.edu
druid-'s GL Journal
http://www.gamedev.net/opengl

Share this post


Link to post
Share on other sites
Guest Anonymous Poster   
Guest Anonymous Poster
In general mixing DDraw with OpenGL can be a bad idea, while you can get it to work, some OpenGL drivers use DDraw internally.

l8r
Ryan

Share this post


Link to post
Share on other sites
Facehat    696
Yet another question: Why can't you use OpenGL with DirectDraw? I was thinking of simply grabbing a device context from a DirectDraw surface and rendering to that, but it sounds like that can't be done. Any reason why?

--TheGoop

Share this post


Link to post
Share on other sites

  • 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++.
      Question:
      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