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


OpenGL DirectX versus OpenGL

Recommended Posts

Guest Anonymous Poster
The best professional solution now is vga mode 13. OGL & DX are only crappy API with no future...

Share this post

Link to post
Share on other sites
Ok, so far you saw that there is no real answer to this question. Anyway, here is a comparison of the two APIs:

Decide for yourself };-)


Share this post

Link to post
Share on other sites
The only advantage of directX is direct access to video memory (if you want to use voxel or 2d demomaking).

For anything else, opengl is better. (NB: with SDL, you can use OpenGl AND access to video memory).

Share this post

Link to post
Share on other sites
I think the two ways r both good.They have their own advantages.

OpenGL has immediate mode,and platform-independ,so it''s dexterity and easy to learn.And many developpers have began to take into account it.

DirectX has immediate mode and reserved mode. It has not only the 3D module and many other useful module ,such as 2D module DirectDraw, Network module DirectPlay.And it''s ability make it the most popular Game SDK.

So they r both worth being learn and use to write Game and Graphics programs.And if u can use them correctly,the hyrid''s effect will be wonderful.

Share this post

Link to post
Share on other sites
I''ve been using Direct3D for many years and I''m pretty happy with it. Easy to understand and use and very capable. I''ve also used OpenGL, although nowhere near as much, and again, it''s easy to understand and use and is very capable.

OpenGL is easier to learn I would say, paritcularly with the NeHe tutorials. OpenGL is more procedural, and less alien looking, so it would probably be easier for a novice to pick up.

Once you get used to the slightly alien look of DX code, it''s really just as easy to use as OpenGL though.

One major plus point for DirectX is that everything you need to learn it and compile programs with it is located on a single CD (or a single download), the DX SDK. And you may consider the fact that more professional game developers use D3D.

Share this post

Link to post
Share on other sites
Omikron, if you had at least a quarter of a brain you would have read the part in the FAQ that says posts like these that cause flame wars are forbidden...

// Thread ends here
// Sound of moderator clicking delete button beside "DirectX versus OpenGL"

Share this post

Link to post
Share on other sites
"DirectX versus OpenGL"

When will you idiots finally understand the distinction: DirectX is a set of APIs. OpenGL is a single API. You cannot compare the two. So, what you really mean is "Direct3D versus OpenGL." But get it right--say Direct3D when you really mean Direct3D and say DirectX when your really mean DirectX!

Here''s the breakdown of analogs:

OpenGL <--> Direct3D
OpenGL + GLU + platform''s API <--> DirectGraphics or DirectDraw + Direct3D + Direct3DX
SDL <--> DirectX

I swear...I''m getting sick of trying to educate you kids.

Share this post

Link to post
Share on other sites

I thought people had to insult each other before it was a flame war. Well, I''ll be keeping my eye on this thread.

Furby, your breath smells of egg and you have a face like a mules arse.

Now can you close this thread?

Share this post

Link to post
Share on other sites
I solved the OGL vs D3D problem by writing wrapper that supports both. Its api is very easy. I think that OpenGL is much easier and cleaner to use but somehow I like D3D style.

Share this post

Link to post
Share on other sites
1: I wasn''t flaming anyone in particular; I was just expressing frustration over a point of ignorance that never seems to go away.
2: I forgot to close my bold tag.

But I shouldn''t get angry like that, so I apologize to all I may have offended.

Share this post

Link to post
Share on other sites
This topic is now closed to further replies.

  • Announcements

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By test opty
      Hi all,
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
  • Popular Now