• ### Announcements

#### Archived

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

# OpenGL OpenGL Vs. DirectX

## Recommended Posts

I have been looking for a few journals on a comparison pf opengl and directx but i have as yet been unsuccessful. Any sujestions??? Thanks.

##### Share on other sites
Yes.

There was a topic on this maybe a week ago.

Search the forums!

I wanna'' ride on the pope mobile.

##### Share on other sites
Sorry but, geez! if you want ppl''s honest appinions don''t go to a board where ppl like opengl more! :>

##### Share on other sites
Direct3D, which is the only part of DirectX against which it is fair to compare OpenGL, is essentially OpenGL.

D3D uses matrices, vertexes and materials. GL uses matrices, vertexes and materials.

D3D places drawing commands between BeginScene() and EndScene(). GL places them between glBegin() and glEnd().

D3D is built upon DirectDraw, which in turn is built upon the GDI. Yu can''t learn DirectDraw without first knowing a little about the GDI, and you can''t learn D3D without first knowing a little about GL. Conversely, GL exists ''as is''. Using glut, you need only use a few lines of code to prepare OpenGL for use. However, you don''t get to use the accelerated 2D features provided by a DirectDraw-like system.

Signatures? We don''t need no steenking signatures!

##### Share on other sites
Mayrel, isn''t is so that since DX8, Direct3D and DirectDraw have merged into one DirectGraphics API?

Dirk =[Scarab]= Gerrits

##### Share on other sites
quote:
Original post by Mayrel
D3D is built upon DirectDraw, which in turn is built upon the GDI.

Then why is Direct Draw faster than GDI ? Isn't Direct Draw an alternative to GDI. Is that not the entire purpose of DirectDraw (and hardware acceleration).
It is true that you can use GDI together with DD but is makes the program run slower.

quote:
Original post by Mayrel
Yu can't learn DirectDraw without first knowing a little about the GDI,

Why not? I did !!

quote:
Original post by Mayrel
and you can't learn D3D without first knowing a little about GL.

I don't know a thing about D3D or OpenGL but I'm sure you are wrong. I would really love to hear you tell us why you have to know OpenGL to learn D3D !

Edited by - granat on November 1, 2001 3:54:41 PM

##### Share on other sites
Do a bunch of searches on Google.

Look for Chris Hecker''s webpage. I think it is at www.d6.com/checker

Search for recent posts by John Carmack at Slashdot.

Other than that, you won''t find much.

My personal opinion, stop comparing and start coding. *Better* is subjective. Use what you like.

SL

##### Share on other sites
D3D is more applied and extensive,it has many functions to help u with simply graphic-programming.but as we all know,opengl has a more strong capability and can be well replanted to other platform.

all these become the clag of selecting d3d or opengl for 3d programming,but perhaps it''s better to learn both of them.

just my opinion.

jerry2
Programming,make a whole new world.

##### Share on other sites
quote:
Original post by granat
Then why is Direct Draw faster than GDI ? Isn''t Direct Draw an alternative to GDI. Is that not the entire purpose of DirectDraw (and hardware acceleration).

I was talking about learning DirectDraw. The concepts of D3D are built upon the concepts of DD, which are built upon the concepts of GDI.

Personally, I think that should have been clear from the rest of the post, but if you honestly thought I meant exactly what I said, I apologise for being unclear.
quote:

Why not? I did !!

You are certain that you''ve never learnt any GDI? You didn''t use CreateWindow? Didn''t load an image into a DC and blit it to a DirectDrawSurface?
quote:

[quote]Original post by Mayrel
and you can''t learn D3D without first knowing a little about GL.

This is a stupid typo on my part. I intended to say DD (as in, DirectDraw).

Signatures? We don''t need no steenking signatures!

• ### Forum Statistics

• Total Topics
627765
• Total Posts
2978983
• ### 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