• Advertisement

Archived

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

OpenGL DirectX versus OpenGL

This topic is 6051 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

Advertisement
guess what...

me likes the way dx is designed - att least since ver 6 }=)

Bjørn.

Share this post


Link to post
Share on other sites
Used to love DX more than OGL then I was persuaded into drawing a simple spinning cube in Open Gl . I have stuck with it since then.

Share this post


Link to post
Share on other sites
If you''re reading this, you''re wasting time.

If you''re going to respond to this, you''re wasting even more time.

G''luck,
-Alamar

Flame wars are just silly...

Share this post


Link to post
Share on other sites
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
how much are you betting, AP?
you think DirectX and OpenGl will go extinct?
unlikly anytime in the near future (at least 10 years)

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:
http://www.xmission.com/~legalize/d3d-vs-opengl.html

Decide for yourself };-)

Bjørn.

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
PSioNiC, sorry, I didn''t know that, but by saying that, _you_ are starting a flame war, not me

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.

Share this post


Link to post
Share on other sites
OK I''ll start, merlin9x9, you are an asshole. No need to tear someone to shreds over a simple misunderstanding.

Share this post


Link to post
Share on other sites
quote:

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
I cant believe i actually read this thread, i must be dumb!!

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
I feel compelled to post something...

Nah, not really

-Mezz

Share this post


Link to post
Share on other sites
Direct3D RULES.
All you fools using OpenGL are losers.
lol jj
but seriously, you are...

Possibility

Share this post


Link to post
Share on other sites

This topic is 6051 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.

Guest
This topic is now closed to further replies.

  • 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