Sign in to follow this  
iYossi

OpenGL [discussion]DirectX 9 or 10 or 11?


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
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
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
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
[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

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
      628401
    • Total Posts
      2982456
  • 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