Sign in to follow this  
ishikawa-san

OpenGL C#, DirectX, and Vectors

Recommended Posts

ishikawa-san    122
Ok, so here's a deal. I'm writting a Game Engine. So there's an IRenderer interface. So I make Directx, opengl, whatever renderer. So another thing, Vector3D class. It's clear that I cannot use diffrent vectors classes, for every renderer. So how can I deal with it? I mean, how can I use my custom vectors in directx? It's about drawUserPrimitive stuff right? I know, I found some examples on the net, but either it uses unsafe code, which does not satisfies me, or it just simply does not explain anything. Common, help me out. DirectX for C# is just soo poor documented. Thanks in advance!

Share this post


Link to post
Share on other sites
zdlr    266
I think DX for C# is poorly documented because XNA and, latterly, WPF may overtake its use.

Anyway, if I've understood your question correctly, I believe your IRenderer interface will deal in your own Vector3D class (or, perhaps your IVector3D interface).

Each specific implementation of your IRenderer (D3DRenderer, OGLRenderer, etc.) will have to convert from the generic vector to their own specific implementation.

If you created an IVector3D, you could provide an adapter for each renderer:


class D3DVector : IVector3D
{
private Direct3DSpecificVector _vector;

public double X
{
get { return _vector.X; }
}

// etc...
}

Share this post


Link to post
Share on other sites
ishikawa-san    122
So this is what I was afraid of. I need to implement/convert, my Vector3D class, to OGL or DirectX one. But I looked to Irrlicht code, also Ogre3D, none of this engines does it. So there must be some other way I bieleve.

Thanks very much for the anwser anyway!

Share this post


Link to post
Share on other sites
zdlr    266
Thinking about it, that's largely because renderers don't need to know anything about vectors... Vertex data, yes, but I don't think the client needs to pass the renderer any vectors directly?

Share this post


Link to post
Share on other sites
FippyDarkpaw    154
First, I wouldn't bother with C#/DX, just use XNA. You are stuck on Windows already (?) so make your life easier and use XNA which is the most well-documented SDK I have ever used.

Second, if you really want to make an OpenGL renderer in C# you probably need an OpenGL/C# wrapper like this:

http://csgl.sourceforge.net/

BTW, in C++ at least, OpenGL calls accept DirectX Vectors and Matrices. For example,

- any OpenGL call that expects float[2] can be passed DX Vector2
- any OpenGL call that expects float[3] can be passed DX Vector3
- etc...

So you might be able to use only the DirectX math library for both your DX and OpenGL renderer.

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