Sign in to follow this  

OpenGL [discussion]DirectX 9 or 10 or 11?

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

So I think I finally answered my self about OpenGL or DirectX, and as you see, I've chose DX. Now, I am facing a question just as big. 9, 10 or 11? I have the graphic card 8400GS and I know it is weak and won't work with DX11, but I am upgrading it, hopefully in a month.

Share this post


Link to post
Share on other sites
DX11 has "features levels" that allows you to support any graphics card down to DX9 level ones ([i]GeForce6+?[/i]).
The only downside is that DX11 applications do not run on Windows XP.

On the other hand, DX9 does run on Windows XP.

There is no reason to use DX10.

In a nutshell, if you want to support XP, use DX9, otherwise use DX11.

Share this post


Link to post
Share on other sites
Wait, so why not use DX10? Cuz untill I won't upgrade I still want to run more advanced stuff than a triangle.

And no, I rather use what's really best. Windows XP is too old anyway.

Share this post


Link to post
Share on other sites
[font="Calibri"][size="3"]DirectX 11 supports older hardware (DX9; DX 10), too. Therefore you don’t need DirectX 10 anymore as you can do anything with DirectX 11. [/size]

[/font]

Share this post


Link to post
Share on other sites
[quote name='Geri' timestamp='1311601637' post='4839981']
9
[/quote]

How 'bout an explenation?

Share this post


Link to post
Share on other sites
Ignore Dx10. On Dx11 You have something called "feature levels" that let you run on Dx10 and Dx9 hardware (the Dx9 level is a bit more limitied compared to original Dx9). If you want to write a 2D game or a relatively simple 3D game, I would go for Dx9. Otherwise Dx11.

Share this post


Link to post
Share on other sites
[quote name='Guns' timestamp='1311602856' post='4839989']
Ignore Dx10. On Dx11 You have something called "feature levels" that let you run on Dx10 and Dx9 hardware (the Dx9 level is a bit more limitied compared to original Dx9). If you want to write a 2D game or a relatively simple 3D game, I would go for Dx9. Otherwise Dx11.
[/quote]

I think I'll go DX10 cuz I don't want DX9, it is kinda old like I see it, and I can't run any f*cking sampals from the SDK.

Share this post


Link to post
Share on other sites
[quote name='iYossi' timestamp='1311603024' post='4839993']
[quote name='Guns' timestamp='1311602856' post='4839989']
Ignore Dx10. On Dx11 You have something called "feature levels" that let you run on Dx10 and Dx9 hardware (the Dx9 level is a bit more limitied compared to original Dx9). If you want to write a 2D game or a relatively simple 3D game, I would go for Dx9. Otherwise Dx11.
[/quote]

I think I'll go DX10 cuz I don't want DX9, it is kinda old like I see it, and I can't run any f*cking sampals from the SDK.
[/quote]

lol.. 4 votes for 9, 5 votes for 11... 0 votes for 10.. and you'll go for 10 [img]http://public.gamedev.net/public/style_emoticons/default/laugh.gif[/img]

forum users never stop to amaze me.

btw.. of course i voted for 11.

Share this post


Link to post
Share on other sites
[quote name='kunos' timestamp='1311606885' post='4840017']
lol.. 4 votes for 9, 5 votes for 11... 0 votes for 10.. and you'll go for 10 [img]http://public.gamedev.net/public/style_emoticons/default/laugh.gif[/img]

forum users never stop to amaze me.
[/quote]

In order to maintain faith in humanity I'm hoping that was a typo on his part :P

My vote? All the way up to 11 baby!

Share this post


Link to post
Share on other sites
I can't fucking run a triangle! And I really don't want 9. But, OK. Anyone has any good tuts?

Share this post


Link to post
Share on other sites
Firstly, calm the language down, there is no need for the swearing.

Secondly; what OS are you running? Are you drivers up to date?

Finally, run the examples via the debugger and see what errors it spits out, this might give you a clue as to why it isn't working.

The DX11 [b]API[/b] will work fine on your card assuming the OS and drivers are up to date and the examples are coded to use the feature levels correctly.

Share this post


Link to post
Share on other sites
I once had the same card as you got! It was the Laptop-Version, though.

And yes, I developed using the DX11 API on that thing. :)


My friend, with a HD4890 had some problems with running DX11 stuff at feature level 10, though. But a driver update did the trick.
You should try that, too. Probably you're running some kind of driver from at least 100 years ago which doesn't even know what DX11 is.

Share this post


Link to post
Share on other sites
[quote name='iYossi' timestamp='1311611014' post='4840035']
I can't fucking run a triangle! And I really don't want 9. But, OK. Anyone has any good tuts?
[/quote]

Just like you asked someone for an explanation as to why use "9", please give us an explanation as to why you "really don't want 9". Also, you can find good tuts in several places. Google and Bing are your friends. And if you would like help with why you "can't run a triangle", we'll need more information... does your code even compile and link? Does it crash somewhere? Does it run, but with a blank/black screen?

Share this post


Link to post
Share on other sites
(no flame intended)

why don't you use opengl?
It'd run on windows xp vista & 7 (and on other platforms as well) you'd get full dx10 level features with that graphics card until you get a dx11 level card, and the transition would be seamless. You wouldn't have to worry about whether you're on XP or Vista or 7 you'd get the same visuals and same features... Plus, as I recently experienced, the two API are like twins (or at least DX 9 and OpenGL 2.1), the same features, same workflow, etc. Although I felt like dx was harder to learn due to the lack of good tutorials.

Share this post


Link to post
Share on other sites
OpenGL has it's own share of driver problems, and besides: the OP has already evaluated the two and chosen Direct3D (see the first post) so the question is really irrelevant.

Share this post


Link to post
Share on other sites
I was actually aiming on OpenGL 3.x and unlike DX9/10/11, the was absoulutly NOTHING.

Share this post


Link to post
Share on other sites
The decision is easy: If you want to run on Windows XP or Xbox 360: DX9. Else: DX11.

Share this post


Link to post
Share on other sites
While DirectX 11 is the latest and obvious most "high tech" release of DirectX, as others have pointed out using DX10 or 11 will cripple your game on windows XP, aka it won't work. (DX10/11 is not supported on Windows XP)


Now if you're focus is not to sell to the "masses" and just learning for now go for the latest version that works on your machine.
Do take heed though and yes it is easy enough to write two rendering .dlls and attach your application to the proper one at load time based on the OS (slightly advanced topic) creating a game in DX9 is what I recommend as a starting foundation. It doesn't require half as many complexities as DX11 does in setting up or rendering and still teaches you the foundation.


You also can learn to use Pixel and Vertex Shaders once you have a firm grasp which is basically what DX11 requires for everything to be rendered. So transitioning to DX11 once you grasp DX9 will be fairly easy. Going backwards ... eh possible but the DX9 -> 11 , again in my opinion is easier. Don't have to swallow as much to get your first app up and running etc etc etc.
If you want to support Windows XP and plan on selling your game/app or having friends run your app if they don't have XP and you create it with DX11 well too bad for them. On the other hand this link:
[url="http://en.wikipedia.org/wiki/Usage_share_of_operating_systems#Desktop_and_laptop_computers"]http://en.wikipedia.org/wiki/Usage_share_of_operating_systems#Desktop_and_laptop_computers[/url]

while the %'s have shifted since that was last updated, I'm sure Vista/Win7 have not taken over in a combined % over XP and if you refuse to create the DirectX 9 rendering .dll (read above) you are in essence cutting out at least 1/2 of your potential buyer base which is crazy. You'll have to learn DirectX 9 anyways to support them, so might as well start there. :)

Share this post


Link to post
Share on other sites
[quote name='grazing' timestamp='1311633365' post='4840230']while the %'s have shifted since that was last updated, I'm sure Vista/Win7 have not taken over in a combined % over XP and if you refuse to create the DirectX 9 rendering .dll (read above) you are in essence cutting out at least 1/2 of your potential buyer base which is crazy. You'll have to learn DirectX 9 anyways to support them, so might as well start there. :)
[/quote]

According to the latest Steam hardware survey, users with both Vista/Win7 and DirectX 10/11 GPUs are now on 56%. Total Vista/Win7 is 71%/72%. XP is down to 20%. DX11 looks more like the reasonable choice every day.

Share this post


Link to post
Share on other sites
[quote name='mhagain' timestamp='1311637806' post='4840268']
[quote name='grazing' timestamp='1311633365' post='4840230']while the %'s have shifted since that was last updated, I'm sure Vista/Win7 have not taken over in a combined % over XP and if you refuse to create the DirectX 9 rendering .dll (read above) you are in essence cutting out at least 1/2 of your potential buyer base which is crazy. You'll have to learn DirectX 9 anyways to support them, so might as well start there. :)
[/quote]

According to the latest Steam hardware survey, users with both Vista/Win7 and DirectX 10/11 GPUs are now on 56%. Total Vista/Win7 is 71%/72%. XP is down to 20%. DX11 looks more like the reasonable choice every day.
[/quote]



You have a link to the survey? Wondering if it's a "poll." that was given e.g. the results will not be that accurate by a long shot. Only amongst those who voted.

Share this post


Link to post
Share on other sites
The OS + hardware data is generated by Steam itself, which queries the OS + drivers. They have the results here: [url="http://store.steampowered.com/hwsurvey"]http://store.steampowered.com/hwsurvey[/url]

Share this post


Link to post
Share on other sites
[quote name='MJP' timestamp='1311647024' post='4840342']
The OS + hardware data is generated by Steam itself, which queries the OS + drivers. They have the results here: [url="http://store.steampowered.com/hwsurvey"]http://store.steampowered.com/hwsurvey[/url]
[/quote]


So it's based on those who actually have this 'steam' installed. Gotcha.




Thank you for the link though. :)

Share this post


Link to post
Share on other sites
Another statistics form those who has installed Unity Web Player: http://unity3d.com/webplayer/hardware-stats.html
There XP is 51.7% from all Windows'es.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Similar Content

    • By xhcao
      Does sync be needed to read texture content after access texture image in compute shader?
      My simple code is as below,
      glUseProgram(program.get());
      glBindImageTexture(0, texture[0], 0, GL_FALSE, 3, GL_READ_ONLY, GL_R32UI);
      glBindImageTexture(1, texture[1], 0, GL_FALSE, 4, GL_WRITE_ONLY, GL_R32UI);
      glDispatchCompute(1, 1, 1);
      // Does sync be needed here?
      glUseProgram(0);
      glBindFramebuffer(GL_READ_FRAMEBUFFER, framebuffer);
      glFramebufferTexture2D(GL_READ_FRAMEBUFFER, GL_COLOR_ATTACHMENT0,
                                     GL_TEXTURE_CUBE_MAP_POSITIVE_X + face, texture[1], 0);
      glReadPixels(0, 0, kWidth, kHeight, GL_RED_INTEGER, GL_UNSIGNED_INT, outputValues);
       
      Compute shader is very simple, imageLoad content from texture[0], and imageStore content to texture[1]. Does need to sync after dispatchCompute?
    • By Jonathan2006
      My question: is it possible to transform multiple angular velocities so that they can be reinserted as one? My research is below:
      // This works quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); quat quaternion2 = GEMultiplyQuaternions(quaternion1, GEQuaternionFromAngleRadians(angleRadiansVector2)); quat quaternion3 = GEMultiplyQuaternions(quaternion2, GEQuaternionFromAngleRadians(angleRadiansVector3)); glMultMatrixf(GEMat4FromQuaternion(quaternion3).array); // The first two work fine but not the third. Why? quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); vec3 vector1 = GETransformQuaternionAndVector(quaternion1, angularVelocity1); quat quaternion2 = GEQuaternionFromAngleRadians(angleRadiansVector2); vec3 vector2 = GETransformQuaternionAndVector(quaternion2, angularVelocity2); // This doesn't work //quat quaternion3 = GEQuaternionFromAngleRadians(angleRadiansVector3); //vec3 vector3 = GETransformQuaternionAndVector(quaternion3, angularVelocity3); vec3 angleVelocity = GEAddVectors(vector1, vector2); // Does not work: vec3 angleVelocity = GEAddVectors(vector1, GEAddVectors(vector2, vector3)); static vec3 angleRadiansVector; vec3 angularAcceleration = GESetVector(0.0, 0.0, 0.0); // Sending it through one angular velocity later in my motion engine angleVelocity = GEAddVectors(angleVelocity, GEMultiplyVectorAndScalar(angularAcceleration, timeStep)); angleRadiansVector = GEAddVectors(angleRadiansVector, GEMultiplyVectorAndScalar(angleVelocity, timeStep)); glMultMatrixf(GEMat4FromEulerAngle(angleRadiansVector).array); Also how do I combine multiple angularAcceleration variables? Is there an easier way to transform the angular values?
    • By dpadam450
      I have this code below in both my vertex and fragment shader, however when I request glGetUniformLocation("Lights[0].diffuse") or "Lights[0].attenuation", it returns -1. It will only give me a valid uniform location if I actually use the diffuse/attenuation variables in the VERTEX shader. Because I use position in the vertex shader, it always returns a valid uniform location. I've read that I can share uniforms across both vertex and fragment, but I'm confused what this is even compiling to if this is the case.
       
      #define NUM_LIGHTS 2
      struct Light
      {
          vec3 position;
          vec3 diffuse;
          float attenuation;
      };
      uniform Light Lights[NUM_LIGHTS];
       
       
    • By pr033r
      Hello,
      I have a Bachelor project on topic "Implenet 3D Boid's algorithm in OpenGL". All OpenGL issues works fine for me, all rendering etc. But when I started implement the boid's algorithm it was getting worse and worse. I read article (http://natureofcode.com/book/chapter-6-autonomous-agents/) inspirate from another code (here: https://github.com/jyanar/Boids/tree/master/src) but it still doesn't work like in tutorials and videos. For example the main problem: when I apply Cohesion (one of three main laws of boids) it makes some "cycling knot". Second, when some flock touch to another it scary change the coordination or respawn in origin (x: 0, y:0. z:0). Just some streng things. 
      I followed many tutorials, change a try everything but it isn't so smooth, without lags like in another videos. I really need your help. 
      My code (optimalizing branch): https://github.com/pr033r/BachelorProject/tree/Optimalizing
      Exe file (if you want to look) and models folder (for those who will download the sources):
      http://leteckaposta.cz/367190436
      Thanks for any help...

    • By Andrija
      I am currently trying to implement shadow mapping into my project , but although i can render my depth map to the screen and it looks okay , when i sample it with shadowCoords there is no shadow.
      Here is my light space matrix calculation
      mat4x4 lightViewMatrix; vec3 sun_pos = {SUN_OFFSET * the_sun->direction[0], SUN_OFFSET * the_sun->direction[1], SUN_OFFSET * the_sun->direction[2]}; mat4x4_look_at(lightViewMatrix,sun_pos,player->pos,up); mat4x4_mul(lightSpaceMatrix,lightProjMatrix,lightViewMatrix); I will tweak the values for the size and frustum of the shadow map, but for now i just want to draw shadows around the player position
      the_sun->direction is a normalized vector so i multiply it by a constant to get the position.
      player->pos is the camera position in world space
      the light projection matrix is calculated like this:
      mat4x4_ortho(lightProjMatrix,-SHADOW_FAR,SHADOW_FAR,-SHADOW_FAR,SHADOW_FAR,NEAR,SHADOW_FAR); Shadow vertex shader:
      uniform mat4 light_space_matrix; void main() { gl_Position = light_space_matrix * transfMatrix * vec4(position, 1.0f); } Shadow fragment shader:
      out float fragDepth; void main() { fragDepth = gl_FragCoord.z; } I am using deferred rendering so i have all my world positions in the g_positions buffer
      My shadow calculation in the deferred fragment shader:
      float get_shadow_fac(vec4 light_space_pos) { vec3 shadow_coords = light_space_pos.xyz / light_space_pos.w; shadow_coords = shadow_coords * 0.5 + 0.5; float closest_depth = texture(shadow_map, shadow_coords.xy).r; float current_depth = shadow_coords.z; float shadow_fac = 1.0; if(closest_depth < current_depth) shadow_fac = 0.5; return shadow_fac; } I call the function like this:
      get_shadow_fac(light_space_matrix * vec4(position,1.0)); Where position is the value i got from sampling the g_position buffer
      Here is my depth texture (i know it will produce low quality shadows but i just want to get it working for now):
      sorry because of the compression , the black smudges are trees ... https://i.stack.imgur.com/T43aK.jpg
      EDIT: Depth texture attachment:
      glTexImage2D(GL_TEXTURE_2D, 0,GL_DEPTH_COMPONENT24,fbo->width,fbo->height,0,GL_DEPTH_COMPONENT,GL_FLOAT,NULL); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glFramebufferTexture2D(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_TEXTURE_2D, fbo->depthTexture, 0);
  • Popular Now