Sign in to follow this  
jbb

OpenGL Dynamically loading and unloading of directx

Recommended Posts

jbb    471
I'm working on a small game project where I want to be able to use d3d11 but to fall back to d3d9 if it's not available / installed.

I can abstract out the drawing interface so that my game with work with either, but if I have to link with the d3d11 DLLs then my program won't even load if they are missing.

So I thought the best thing to do was to use LoadLibrary and GetProcAddress to load the d3d9.dll and locate the "Direct3DCreate9" function, and to do similar for D3D11 and just use whichever loaded. (I'm fully aware they are not very similar and will need a considerable amount of abstraction to present the same interface to my game).

My question though, is are there any problems with loading directx dynamically like this? And if I shut down the directx device can I safely unload the DLLs should I wish to?

I'd ideally like to do the same with opengl as well, although that seems more painful as there are hundreds of entry points to use GetProcAddress on so I might leave that out.

My question though is as above - can I safely load d3d9 and d3d11 dynamically, and can I unload the DLLs when I'm finished with them? A quick check seems to indicate that I can load the sucessfully and use them, but perhaps there is something I'm unaware of.

Share this post


Link to post
Share on other sites
Erik Rufelt    5901
With OpenGL you're required to load most newer functionality dynamically, as only version 1.1 (I think) is in OpenGL32.dll, and for the later ones you need to use wglGetProcAddress with an active context instead. There are multiple free libraries that do this for you, among other things, for example GLEW.

An alternative to LoadLibrary is Delay-Loaded DLLs, but either method should work fine. You can unload a library with FreeLibrary if you're not using it anymore.

One problem with dynamically loading D3D can be that the user has an earlier version of a DirectX DLL installed than the one you use when you build your program, for example D3D11.dll from August 2008 while you build with the one from June 2010. This could potentially lead to things not working exactly the way you expect, which is why it is a better idea to include the DX redistributable installer with your game instead, if possible.

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  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now