Sign in to follow this  
BlackWind

OpenGL some questions about direct3d9

Recommended Posts

BlackWind    212
hi, im moving from opengl to directx, and i have some questions... i have been doing many examples for d3d, and i found vertex buffers and index buffers are good for saving space and boos the performace. In opengl there is something called "vertex arrays" which is pretty much the same thing. But that technique is old. Also, it has something called Vertex Buffers Object (vbo) which is actually a "better" version of vertex arrays. "Recently" they release the FB0 (or something like that, which apparently is even better). Now, my question is, which are the "new" techniques and utilities in D3D9 (with enough documentation and examples on the internet) that i should use? and what does that replaces? for example, 1.-what is better than vertex buffers and index buffers? 2.- whats the best option for matrix operations? 3.- and for effects? (lighting, shadows, etc..) 4.- and for working with meshes? (.x for example) 5.- and for spatial partition? by those questions, i dont mean that for example someone answer: "for spatial partition you should use octrees", but instead of that, something like: "well, before you had D3DOctree::Create(D3DMesh *meshdata), but now you have D3DXNEWOCTREE:Create(D3DXMesh *meshData) which is faster and easier to use and comes in "x library" thanks for your advices. cheers!

Share this post


Link to post
Share on other sites
dmatter    4828
Quote:
Original post by BlackWind
Now, my question is, which are the "new" techniques and utilities in D3D9 (with enough documentation and examples on the internet) that i should use? and what does that replaces?
One nice aspect of D3D versus OGL is that, more or less, what you see is what you get - you don't have to mess around with extensions that do the same job only better; this is even more the case now with D3D10 and onwards. The tools you're provided with are the ones you actually use.

Quote:
1.-what is better than vertex buffers and index buffers?
Vertex and index buffers in D3D are the equivalent of Vertex Buffer Objects (VBO's) in OGL.
Frame Buffer Objects (FBO's) are something completely different but designed with the same object model, hence the similarity in name.

Quote:
2.- whats the best option for matrix operations?
As a rule of thumb: Do them in shaders wherever it makes sense, otherwise do them on the CPU using a maths library like the one found in the D3DX (D3DXMatrix and associates).

Quote:
3.- and for effects? (lighting, shadows, etc..)
Prefer to use the programmable pipeline. So either use the existing D3DX Effects Framework or write your own to manage shaders manually.

Quote:
4.- and for working with meshes? (.x for example)
Again, either use the existing classes in the D3DX (like ID3DXMesh) or write your own.

Quote:
5.- and for spatial partition?
More specialist higher level structures such as these don't exist as part of the D3D(X) API, you'd do it all yourself or find some other library to do it for you.

Share this post


Link to post
Share on other sites
metalman666    156

Check this sites, these has got good amount of directX tutorials.

http://directxtutorial.com/

http://www.chadvernon.com/blog/tutorials/

http://www.drunkenhyena.com/cgi-bin/directx.pl

All the sites are very helpful with loads of examples.

Hope this helps...

Share this post


Link to post
Share on other sites
Buckeye    10747
Don't forget that OGL uses a right-hand coordinate system and CCW triangles (default culling of CW) and DirectX uses a left-hand system and (commonly) culls CCW. You can't simply import OGL vertex data. There's a bit of manipulation required if you do that.

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