Sign in to follow this  
3dmodeler

OpenGL opengl or directx

Recommended Posts

OpenGL and Direct3D will allow you to do essentially the same thing. They accomplish it in different ways -- if you are in doubt, pick one and give it a shot, see how you think it feels. Then take a look at the other, and decide which you like better.

The only caveat would be, for OpenGL, don't try to compare the immediate-mode (glBegin / glVertex / glEnd) portion of the API with D3D directly. You'll likely see the immediate mode API first learning OpenGL, and there is no equivalent in D3D, which may seem like a disadvantage. However, GL's immediate mode is one of the slowest methods of rendering available in the API, so if you intend to do things that are nontrivial eventually, you'll want to use a more efficient rendering method.

Share this post


Link to post
Share on other sites
Though for many here this is a non-issue, don't discount the advantage of OpenGL in cross-platform portability. With D3D you and all your users are stuck with Windows forever and ever.

I'm not trying to diss Microsoft here. I simply think it is good to support interoperability and open standards (not open source software--these are separate issues, and open standards are not a communist philosophy, unlike open source is).

I hope you choose OpenGL. Learn and use only those features that are not marked as deprecated in the recent 3.0 standard.

Share this post


Link to post
Share on other sites
funny.. its the same question i've been asking the other day in other forums..
and i got an answer that OpenGL is the best enigne that is.. its faster than DX and works on many platforms more than DX.. so i hightly suggest you to learn OpenGL.. as me that learning OpenGL already on my 3rd week of learning, im already know how to:
make 2d stuff like lines, boxes, circles, dots etc.
load textutres AGP, BMP and JPG file formats
plus i know how to create Boxes, circles and texture them..
also, fogging, blending lights effects and so on.. its really easy to learn that languange!
i've learning DX before it, and i can tell you that OpeNGL is much more easyer than DX!

Share this post


Link to post
Share on other sites
Quote:
Original post by GogetaX
and i got an answer that OpenGL is the best enigne that is..
This is nonsensical.
Quote:
its faster than DX
This is flat out false.
Quote:
and works on many platforms more than DX..
This is probably true.

There's one critical problem, which is that very nearly every OpenGL teaching resource available (especially NeHe) is awful and teaches you to write OpenGL code that you should never, ever write. I guarantee you that the code GogetaX writes is uniformly ancient OpenGL code that should never see the light of day, through no fault of his own. It's rather difficult to learn it properly when all the resources are 1) severely outdated 2) written by clueless people, or 3) both 1 and 2.

Share this post


Link to post
Share on other sites
Quote:

There's one critical problem, which is that very nearly every OpenGL teaching resource available (especially NeHe) is awful and teaches you to write OpenGL code that you should never, ever write. I guarantee you that the code GogetaX writes is uniformly ancient OpenGL code that should never see the light of day, through no fault of his own. It's rather difficult to learn it properly when all the resources are 1) severely outdated 2) written by clueless people, or 3) both 1 and 2.


I totally agree, a lot of OpenGL tutorials are ancient code. However I would say there seem to be a lot more OpenGL tutorials and materials around so they are good to get you going and then you can learn better ways to do what you understand to do another way.

I find OpenGL a lot easier to work with than direct 3D, I learnt OpenGL first using immediate mode and got to grips with that then progressed to using vertex arrays and VBO's so I found switching to direct 3D after this very simple (as direct3D vertex buffers are very similar to OpenGL). It seems OpenGL has a nicer learning curve than direct3D - all be it using some deprecated OpenGL code.

In general though your doing things that both GL and DX can both deal with and especially when using shaders I don't really see benefits over which one you use. The reason I use GL more commonly is because I have a nice little engine and just feel more comfortable using GL. Once you know one of them pretty well the other should be easy to pick up because when learning a graphics API you will learn lots of rendering techniques, maths and so on that have no bearing on which API you use.

Share this post


Link to post
Share on other sites
Well if it was like 10 years ago I would say OpenGL but currently OGL is lagging behind DX.The letdown with opengl 3.0 didn't help anything either.I'm hoping khronos holds his word and releases 3.1 in a few months and removes all the depreceated features and cleans the API.If you are going to be writing games for windows D3D is the way to go now, its much cleaner.If you are doing something cross platform you are stuck with OGL.
Side note : I remember the days when 3d studio max was using opengl by default.Now its using d3d I guess correct me if I'm wrong.

Share this post


Link to post
Share on other sites
Yup. DX9 by default, but DX10 works too.

I prefer DirectX too. Really easy to learn. You can even start a new project with sound and gamepad support with a wizard. They also have tutorials for both dx9 and dx10 in their SDK.

Share this post


Link to post
Share on other sites
Quote:
Original post by Promit
There's one critical problem, which is that very nearly every OpenGL teaching resource available (especially NeHe) is awful and teaches you to write OpenGL code that you should never, ever write. I guarantee you that the code GogetaX writes is uniformly ancient OpenGL code that should never see the light of day, through no fault of his own. It's rather difficult to learn it properly when all the resources are 1) severely outdated 2) written by clueless people, or 3) both 1 and 2.


Are there any good tutorials/resources available that you can recommend? I've
got the book OpenGL Game Programming by Kevin Hawkins and Dave Astle. Is it still a good resource or is it so dated that it's no longer useful?

Share this post


Link to post
Share on other sites
Quote:
Original post by santonel
Quote:
Original post by Promit
There's one critical problem, which is that very nearly every OpenGL teaching resource available (especially NeHe) is awful and teaches you to write OpenGL code that you should never, ever write. I guarantee you that the code GogetaX writes is uniformly ancient OpenGL code that should never see the light of day, through no fault of his own. It's rather difficult to learn it properly when all the resources are 1) severely outdated 2) written by clueless people, or 3) both 1 and 2.


Are there any good tutorials/resources available that you can recommend? I've
got the book OpenGL Game Programming by Kevin Hawkins and Dave Astle. Is it still a good resource or is it so dated that it's no longer useful?


I think it is good, but everything in this book is using immediate mode or display list, so I'd say it's a bit outdated.

Hope that helps

Share this post


Link to post
Share on other sites
Is there an up-to-date-book? I don't know what immediate mode is. I am using video tutorials now but will need a book that is not so dated. As far as DX9 i have a book by wolfgang Engel and I could not conpile a thing so after weeks of failing i decided to try OpenGL, so far so good

3dmodeler

Share this post


Link to post
Share on other sites
since I just finished the opengl game programming book, I need new input too..
the superbible sounds interesting, it's on my list, but what about these two:

OpenGL Library: I'm not sure if its just a reference or a tutorial.. or both?

The Official Guide to Learning OpenGL(R), Version 2: I've always seen people recommend the red book, but is it maybe outdated too ?

edit: heh, the first one includes the second one.. nevertheless, what do you think..

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  

  • Announcements

  • Forum Statistics

    • Total Topics
      628346
    • Total Posts
      2982203
  • 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. 
      Thanks, 
      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!
      Thanks!
    • 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.
      Thanks.
  • Popular Now