Jump to content
  • Advertisement
Sign in to follow this  
Viperrr

OpenGL DirectX and PhysX

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

Does any here have experience using AGEIA PhysX with DirectX? And specifically its character controller? I am looking for a tutorial on how to use the PhysX character controller with DirectX, to create a standard First Person Shooter control. The samples that come with the documentation of PhysX are for openGL, and are not explained very well. I have never used PhysX before, can someone help me get started please?

Share this post


Link to post
Share on other sites
Advertisement
I could use this nfo also. The tuts for the character controller are not very good for me. Can anyone post some simplistic code for this?

thanks in advance,

Share this post


Link to post
Share on other sites
Never got around to using the character API, but I had PhysX integrated into my old D3D9 engine. If you any specific question not related to the character API I can try to answer them for you, if you like.

Share this post


Link to post
Share on other sites
Ok well, how about I start simple: creating a plane, and displaying it onscreen (for debugging)

This is part of what I have now:
[source lang=cpp]
...
pGroundPlane = CreateGroundPlane();
...

NxActor* CreateGroundPlane()
{
// Create a plane with default descriptor
NxPlaneShapeDesc planeDesc;
NxActorDesc actorDesc;
actorDesc.shapes.pushBack(&planeDesc);
return pScene->createActor(actorDesc);
}



How would I render this plane onscreen? Using directX..

Share this post


Link to post
Share on other sites
I see alot of people are viewing this topic.

If you, like me and 7thAvatar, would like to see a tutorial on charactercontrol with PhysX + DirectX, drop a line here!

If there is enough interest for it, maybe someone will be kind enough to make us one :)

Share this post


Link to post
Share on other sites
Perhaps important to point out (and I sense this is the point of confusion): the mesh or shape you supply to PhysX has absolutely nothing to do with the mesh that you render. They are completely different meshes who's data is stored in different places. In general, the mesh you supply to PhysX is a really simplified version of your actual mesh but in practice they share no data and can thus be considered "completely different".

So in your code you've created an NxPlaneShape but you have nothing to render because you still need to create an actual mesh to render. i.e. some set of vertices, indices, uv coordinates, textures, shaders and whatnot for DirectX to handle.

To put another way, if you don't already know how to create objects and draw them in DirectX (i.e. have an already working application that does this) then do not try to use these 2 APIs together. Start by building a basic "game" just using DirectX: have some objects that move around under your own control which are drawn to the screen.

Otherwise, if I'm off the mark I'm not entirely sure what the problem is. So here's another stab.

Think of PhysX as the "where stuff is" manager. DirectX is just the "draw stuff" manager.

Usually you'd draw something like this (in API agnostic pseudo-code)


MyAPIPushMatrix( myThingsOrientationMatrix );

DrawThing();

MyAPIPopMatrix();




Now if you're not using PhysX then:


myThingsOrientationMatrix == myThing.getMatrix();




however, you're using PhysX to figure out where stuff is so


myThingsOrientationMatrix = myThing->myNxActor.getMatrix();

//replace getMatrix() with the actual API call. too lazy to look it up right now




-me

Share this post


Link to post
Share on other sites
Palidine,

I know how to draw things with DirectX. Infact, I have the graphics part of my engine down; I can load and display meshes, using pixelshaders.

So my engine is at the point where I have a building (which consists of some meshes) and I can walk through it with WASD + mouse look. You know, the controls pretty much all FPS use. (I use DirectInput to do it)

But like you said, Direct3D has nothing to do with collision detection, it just draws. Now I need a way to keep the player from walking through walls, so I looked around and found PhysX :)

I also understand that PhysX meshes are completely seperate from Direct3D meshes. I understand what you mean by "where stuff is" manager. I knew that.

However, looking at the samples for openGL, I noticed they actually draw the PhysX meshes to the screen, for debug purposes. That way I could line up the PhysX meshes with the Direct3D meshes.

The reason I wanted to draw the plane now, is this:
If it shows up on screen, it mean Im doing something right! ;)

Are you saying this is not possible?

Share this post


Link to post
Share on other sites
Quote:
Original post by Viperrr
Palidine,

I know how to draw things with DirectX. Infact, I have the graphics part of my engine down; I can load and display meshes, using pixelshaders.

So my engine is at the point where I have a building (which consists of some meshes) and I can walk through it with WASD + mouse look. You know, the controls pretty much all FPS use. (I use DirectInput to do it)

But like you said, Direct3D has nothing to do with collision detection, it just draws. Now I need a way to keep the player from walking through walls, so I looked around and found PhysX :)

I also understand that PhysX meshes are completely seperate from Direct3D meshes. I understand what you mean by "where stuff is" manager. I knew that.

However, looking at the samples for openGL, I noticed they actually draw the PhysX meshes to the screen, for debug purposes. That way I could line up the PhysX meshes with the Direct3D meshes.

The reason I wanted to draw the plane now, is this:
If it shows up on screen, it mean Im doing something right! ;)

Are you saying this is not possible?


No they don't. In the demo code they build simple geom shapes with OpenGL calls. If you start with DrawActor() and go deep enough their are a whole bunch of utility functions that draw shapes in OpenGL.

The demos uses the PhysX internal list of objects as the render list so it looks like they are rendering the actual PhysX object. My entities have a pointer to their physics body and I keep my own list of rendering objects. Then I poll the entities physics object world matrix as the position to place the D3D mesh. Same as Palidine pseudo code.

Share this post


Link to post
Share on other sites
The PhysX physics simulation is SEPARATE from the DirectX Rendering API. To use them together, you want to supply some data from your scene (original matrix positions, bounding volume size, a simplified set of mesh data etc.) along with the physical attributes of the things in your scene to the physX simulation via NxActors. The simulation then runs and updates the actors world matrices - thats essentially all it does. Next you take the world matrix of the NxActor (NxActor->getMatrix()) and apply it before rendering your DirectX representation of the object. Remember the two things are separate!

Share this post


Link to post
Share on other sites
The PhysX SDK comes with an interactive debugger ... it's a long time since I've used it but I remember it being very helpful. You can also get PhysX to spit out buffers full of vertices for rendering debug shapes in-game. Rendering these will give you a visual representation of the actual PhysX actors (including character controller) within your scene. It's all in the docs :)

Share this post


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

  • Advertisement
  • Advertisement
  • Popular Tags

  • Similar Content

    • By plz717
      Hello, everyone! I hope my problem isn't too 'beginnerish'. I'm doing research on motion synthesis now, trying to implement the Deep Mimic paper (DeepMimic) by BINPENG XUE, in this paper, I need to first retarget character A's motion to another character B to make the reference motion clips for character B, since we don't have character B‘s reference motion. The most important thing is that in the paper, the author copied character A's joint's rotation with respective to joint's local coordinate system (not the parent) to character B. In my personal understanding, the joint's rotation with respective to joint's local coordinate system is something like that in the attached photo, where for the Elbow joint, i need to get the Elbow's rotation in the elbow's local coordinate system (i'm very grateful for you to share your ideas if i have misunderstanding about it 🙂)
      I have searched many materials on the internet about how to extract the local joint's information from FBX, the most relative one i found is the pivot rotation( and geometric transformation, object offset transformation). I'm a beginner in computer graphics, and i'm confused about whether the pivot rotation( or geometric transformation, object offset transformation) is exactly the joint's local rotation i'm seeking? I hope someone that have any ideas can help me, I'd be very grateful for any pointers in the right direction. Thanks in advance! 

    • By nOoNEE
      hello guys , i have some questions  what does glLinkProgram  and  glBindAttribLocation do?  i searched but there wasnt any good resource 
    • By owenjr
      Hi, I'm a Multimedia Engineering student. I am about to finish my dergree and I'm already thinking about what topic to cover in my final college project.
      I'm interested in the procedural animation with c++ and OpenGL of creatures, something like a spider for example. Can someone tell me what are the issues I should investigate to carry it out? I understand that it has some dependence on artificial intelligence but I do not know to what extent. Can someone help me to find information about it? Thank you very much.
       
      Examples: 
      - Procedural multi-legged walking animation
      - Procedural Locomotion of Multi-Legged Characters in Dynamic Environments
    • By Lewa
      So, i'm still on my quest to unterstanding the intricacies of HDR and implementing this into my engine. Currently i'm at the step to implementing tonemapping. I stumbled upon this blogposts:
      http://filmicworlds.com/blog/filmic-tonemapping-operators/
      http://frictionalgames.blogspot.com/2012/09/tech-feature-hdr-lightning.html
      and tried to implement some of those mentioned tonemapping methods into my postprocessing shader.
      The issue is that none of them creates the same results as shown in the blogpost which definitely has to do with the initial range in which the values are stored in the HDR buffer. For simplicity sake i store the values between 0 and 1 in the HDR buffer (ambient light is 0.3, directional light is 0.7)
      This is the tonemapping code:
      vec3 Uncharted2Tonemap(vec3 x) { float A = 0.15; float B = 0.50; float C = 0.10; float D = 0.20; float E = 0.02; float F = 0.30; return ((x*(A*x+C*B)+D*E)/(x*(A*x+B)+D*F))-E/F; } This is without the uncharted tonemapping:
      This is with the uncharted tonemapping:
      Which makes the image a lot darker.
      The shader code looks like this:
      void main() { vec3 color = texture2D(texture_diffuse, vTexcoord).rgb; color = Uncharted2Tonemap(color); //gamma correction (use only if not done in tonemapping code) color = gammaCorrection(color); outputF = vec4(color,1.0f); } Now, from my understanding is that tonemapping should bring the range down from HDR to 0-1.
      But the output of the tonemapping function heavily depends on the initial range of the values in the HDR buffer. (You can't expect to set the sun intensity the first time to 10 and the second time to 1000 and excpect the same result if you feed that into the tonemapper.) So i suppose that this also depends on the exposure which i have to implement?
      To check this i plotted the tonemapping curve:
      You can see that the curve goes only up to around to a value of 0.21 (while being fed a value of 1) and then basically flattens out. (which would explain why the image got darker.)
       
      My guestion is: In what range should the values in the HDR buffer be which then get tonemapped? Do i have to bring them down to a range of 0-1 by multiplying with the exposure?
      For example, if i increase the values of the light by 10 (directional light would be 7 and ambient light 3) then i would need to divide HDR values by 10 in order to get a value range of 0-1 which then could be fed into the tonemapping curve. Is that correct?
    • By nOoNEE
      i am reading this book : link
      in the OpenGL Rendering Pipeline section there is a picture like this: link
      but the question is this i dont really understand why it is necessary to turn pixel data in to fragment and then fragment into pixel could please give me a source or a clear Explanation that why it is necessary ? thank you so mu
       
       
    • By Inbar_xz
      I'm using the OPENGL with eclipse+JOGL.
      My goal is to create movement of the camera and the player.
      I create main class, which create some box in 3D and hold 
      an object of PlayerAxis.
      I create PlayerAxis class which hold the axis of the player.
      If we want to move the camera, then in the main class I call to 
      the func "cameraMove"(from PlayerAxis) and it update the player axis.
      That's work good.
      The problem start if I move the camera on 2 axis, 
      for example if I move with the camera right(that's on the y axis)
      and then down(on the x axis) -
      in some point the move front is not to the front anymore..
      In order to move to the front, I do
      player.playerMoving(0, 0, 1);
      And I learn that in order to keep the front move, 
      I need to convert (0, 0, 1) to the player axis, and then add this.
      I think I dont do the convert right.. 
      I will be glad for help!

      Here is part of my PlayerAxis class:
       
      //player coordinate float x[] = new float[3]; float y[] = new float[3]; float z[] = new float[3]; public PlayerAxis(float move_step, float angle_move) { x[0] = 1; y[1] = 1; z[2] = -1; step = move_step; angle = angle_move; setTransMatrix(); } public void cameraMoving(float angle_step, String axis) { float[] new_x = x; float[] new_y = y; float[] new_z = z; float alfa = angle_step * angle; switch(axis) { case "x": new_z = addVectors(multScalar(z, COS(alfa)), multScalar(y, SIN(alfa))); new_y = subVectors(multScalar(y, COS(alfa)), multScalar(z, SIN(alfa))); break; case "y": new_x = addVectors(multScalar(x, COS(alfa)), multScalar(z, SIN(alfa))); new_z = subVectors(multScalar(z, COS(alfa)), multScalar(x, SIN(alfa))); break; case "z": new_x = addVectors(multScalar(x, COS(alfa)), multScalar(y, SIN(alfa))); new_y = subVectors(multScalar(y, COS(alfa)), multScalar(x, SIN(alfa))); } x = new_x; y = new_y; z = new_z; normalization(); } public void playerMoving(float x_move, float y_move, float z_move) { float[] move = new float[3]; move[0] = x_move; move[1] = y_move; move[2] = z_move; setTransMatrix(); float[] trans_move = transVector(move); position[0] = position[0] + step*trans_move[0]; position[1] = position[1] + step*trans_move[1]; position[2] = position[2] + step*trans_move[2]; } public void setTransMatrix() { for (int i = 0; i < 3; i++) { coordiTrans[0][i] = x[i]; coordiTrans[1][i] = y[i]; coordiTrans[2][i] = z[i]; } } public float[] transVector(float[] v) { return multiplyMatrixInVector(coordiTrans, v); }  
      and in the main class i have this:
       
      public void keyPressed(KeyEvent e) { if (e.getKeyCode()== KeyEvent.VK_ESCAPE) { System.exit(0); //player move } else if (e.getKeyCode()== KeyEvent.VK_W) { //front //moveAmount[2] += -0.1f; player.playerMoving(0, 0, 1); } else if (e.getKeyCode()== KeyEvent.VK_S) { //back //moveAmount[2] += 0.1f; player.playerMoving(0, 0, -1); } else if (e.getKeyCode()== KeyEvent.VK_A) { //left //moveAmount[0] += -0.1f; player.playerMoving(-1, 0, 0); } else if (e.getKeyCode()== KeyEvent.VK_D) { //right //moveAmount[0] += 0.1f; player.playerMoving(1, 0, 0); } else if (e.getKeyCode()== KeyEvent.VK_E) { //moveAmount[0] += 0.1f; player.playerMoving(0, 1, 0); } else if (e.getKeyCode()== KeyEvent.VK_Q) { //moveAmount[0] += 0.1f; player.playerMoving(0, -1, 0); //camera move } else if (e.getKeyCode()== KeyEvent.VK_I) { //up player.cameraMoving(1, "x"); } else if (e.getKeyCode()== KeyEvent.VK_K) { //down player.cameraMoving(-1, "x"); } else if (e.getKeyCode()== KeyEvent.VK_L) { //right player.cameraMoving(-1, "y"); } else if (e.getKeyCode()== KeyEvent.VK_J) { //left player.cameraMoving(1, "y"); } else if (e.getKeyCode()== KeyEvent.VK_O) { //right round player.cameraMoving(-1, "z"); } else if (e.getKeyCode()== KeyEvent.VK_U) { //left round player.cameraMoving(1, "z"); } }  
      finallt found it.... i confused with the transformation matrix row and col. thanks anyway!
    • By Lewa
      So, i'm currently trying to implement an SSAO shader from THIS tutorial and i'm running into a few issues here.
      Now, this SSAO method requires view space positions and normals. I'm storing the normals in my deferred renderer in world-space so i had to do a conversion and reconstruct the position from the depth buffer.
      And something there goes horribly wrong (which has probably to do with worldspace to viewspace transformations).
      (here is the full shader source code if someone wants to take a look at it)
      Now, i suspect that the normals are the culprit.
      vec3 normal = ((uNormalViewMatrix*vec4(normalize(texture2D(sNormals, vTexcoord).rgb),1.0)).xyz); "sNormals" is a 2D texture which stores the normals in world space in a RGB FP16 buffer.
      Now i can't use the camera viewspace matrix to transform the normals into viewspace as the cameras position isn't set at (0,0,0), thus skewing the result.
      So what i did is to create a new viewmatrix specifically for this normal without the position at vec3(0,0,0);
      //"camera" is the camera which was used for rendering the normal buffer renderer.setUniform4m(ressources->shaderSSAO->getUniform("uNormalViewMatrix"), glmExt::createViewMatrix(glm::vec3(0,0,0),camera.getForward(),camera.getUp())//parameters are (position,forwardVector,upVector) ); Though i have the feeling this is the wrong approach. Is this right or is there a better/correct way of transforming a world space normal into viewspace?
    • By HawkDeath
      Hi,
      I'm trying mix two textures using own shader system, but I have a problem (I think) with uniforms.
      Code: https://github.com/HawkDeath/shader/tree/test
      To debug I use RenderDocs, but I did not receive good results. In the first attachment is my result, in the second attachment is what should be.
      PS. I base on this tutorial https://learnopengl.com/Getting-started/Textures.


    • By norman784
      I'm having issues loading textures, as I'm clueless on how to handle / load images maybe I missing something, but the past few days I just google a lot to try to find a solution. Well theres two issues I think, one I'm using Kotlin Native (EAP) and OpenGL wrapper / STB image, so I'm not quite sure wheres the issue, if someone with more experience could give me some hints on how to solve this issue?
      The code is here, if I'm not mistaken the workflow is pretty straight forward, stbi_load returns the pixels of the image (as char array or byte array) and you need to pass those pixels directly to glTexImage2D, so a I'm missing something here it seems.
      Regards
    • By Hashbrown
      I've noticed in most post processing tutorials several shaders are used one after another: one for bloom, another for contrast, and so on. For example: 
      postprocessing.quad.bind() // Effect 1 effect1.shader.bind(); postprocessing.texture.bind(); postprocessing.quad.draw(); postprocessing.texture.unbind(); effect1.shader.unbind(); // Effect 2 effect2.shader.bind(); // ...and so on postprocessing.quad.unbind() Is this good practice, how many shaders can I bind and unbind before I hit performance issues? I'm afraid I don't know what the good practices are in open/webGL regarding binding and unbinding resources. 
      I'm guessing binding many shaders at post processing is okay since the scene has already been updated and I'm just working on a quad and texture at that moment. Or is it more optimal to put shader code in chunks and bind less frequently? I'd love to use several shaders at post though. 
      Another example of what I'm doing at the moment:
      1) Loop through GameObjects, bind its phong shader (send color, shadow, spec, normal samplers), unbind all.
      2) At post: bind post processor quad, and loop/bind through different shader effects, and so on ...
      Thanks all! 
  • Advertisement
  • Popular Now

  • Forum Statistics

    • Total Topics
      631393
    • Total Posts
      2999765
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!