• Advertisement

Archived

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

OpenGL OpenGL vs DirectX

This topic is 6550 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Just interesting there is a reason to support OpenGL? As war is follow, i headr many people that''s like OGL or DX. Some people says that OGL slowly dying, and DX is the future of 3D. How do you people think, OGL ( exactly OGL ) will be supported for a long time ( 5-10 years for example ) The hardware providers will support acceleration on their 3D cards for OGL in future ? Or, again Micro$oft with his DX win a "battle" ?

Share this post


Link to post
Share on other sites
Advertisement
It''s going to be OpenGL in the future, and not Direct3D, as far as I''m concerned.
Microsoft has just ripped the OpenGL interface anyway, for their stuff, if I remember the discussions correctly.

Share this post


Link to post
Share on other sites
I think you can''t say anything for sure about that right now. MS more or less controls it both (that is because OpenGL drivers for Windows comes from MS themselves).

Keep in mind though that you can''t compare OpenGL with DirectX since DX is a whole suit of gamedev components and OpenGL is only graphics. A more valid question would be the fight between Direct3D and OpenGL.

============================
Daniel Netz, Sentinel Design
"I'm not stupid, I'm from Sweden" - Unknown

Share this post


Link to post
Share on other sites
If you don''t want to support M$ (for the reason you want) or if you are planning multi-platform strategy, then OpenGL is the API to support.
Linux is coming, BeOS is free, there''s no reason why you shouldn''t use OpenGL to choose a windows only not very well design API (DirectX).
OpenGL has been thought and proved very usefull, Direct3D is a copy and is windows specific, need I say more ?

OpenGL means : "Open Graphioc Library", so I defintely prefer an open architecture rather than a M$ controlled one.
(Or anyone controlled.)
If you look around, every card as OpenGL miniGL and more and more comes with an OpenGL ICD.
nVidia works much with OpenGL, PowerVR are faster with OpenGL...

OpenGL is the most interesting API out there.
Direct3D had become more interesting, since Dreamcast use it, but it''s not enough to use it.


-* Sounds, music and story makes the difference between good and great games *-

Share this post


Link to post
Share on other sites
D3D is Windows only, OpenGL is portable. That in itself is reason enough to -know- OpenGL, even if you don''t use it that much. As leading companies like Corel and iD are saying, you have to consider Linux. Not to mention Macs, BeOS or any other new platform that may gain popularity.

Share this post


Link to post
Share on other sites
No offense. But I''m tired of hearing people say DirectX sucks because it''s MS. That''s a bad reason to say anything sucks. Just cause of the company that makes it.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
I am partial to OpenGL. I started to learn DirectX and it just wasn''t my thing. Learned OpenGL and love it. You usually want a 3d accelerator if you are going to code opengl though.

Share this post


Link to post
Share on other sites
Directx has all components in there, graphics, input, network sound, and programming interface for all of them is very similar, so basically you''ll learn it only once. All that you need, whereas opengl has only graphics (there''s that OpenAL thing, but its nonexistent at this stage). And for some reason, i dont have big hopes on Linux becoming wildly popular all of a sudden. Im not a windows fan (8bit 80 machines like Z80 are the BEST!), but its gonna remain the biggest audience forcouple of years at least, and theres that X-Box announced as well, which is going to use Directx as its API.
So if you have any plans of showing the world your accomplishments in the future, go with DX.

-kertropp

Share this post


Link to post
Share on other sites
don''t choose either... one can''t tell where anything will be in 5 years, so if you want to be prepared for anything, learn both API''s

OGL is easy to learn. Direct3d is significantly more difficult, but both are easy to use once you know them.

*oof*

Share this post


Link to post
Share on other sites
Sorry, using Direct3D is risky, since Microsoft may be broken by antitrust law. Confusion and inability of management may suddenly kill usability of Direct3D.

Moreover, Microsoft does not seem to learn from the past. It continues its monopoly-like illegal strategy: using its monopoly advantage for other markets. I wonder if Microsoft even recognize this strategy is illegal. This keeps the risk higher and higher,,,.

OpenGL is safer.

Kate

Edited by - kate on 3/14/00 9:41:46 AM

Share this post


Link to post
Share on other sites
To add a bit to what has been said here, OpenGL is NOT slowly dying. Besides the fact that it''s cross-platform, it is also the 3D API of choice in the graphics community, so, even if it fades in the game market, it will still be around for a long time to come in the world of graphics, and thus will almost certainly continue to be supported in hardware.

Share this post


Link to post
Share on other sites

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement