Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 23 Aug 2011
Offline Last Active May 09 2012 10:50 PM

Topics I've Started

How do navMesh work with agents in different sizes?

19 April 2012 - 11:29 PM

Attached File  navMeshQues.png   14.58KB   25 downloads
As shown in the graph above, without considering the size of agent, the result path from polygon A to polygon C would be A->B->C.

But if considered the size, because of the minimum passable width α from A to C in B is less than the agent's diameter, the detecting should avoid to across B from A to C while doing a pathfinding, and the result path should be A ->B->D->E->F->B->C.

The question is how to know which polygon or which exit border of a polygon should be avoid during a pathfinding?

How to get data from render-target when device is lost?

12 February 2012 - 08:54 AM

For resetting device after it was lost, all D3DPOOL_DEFAULT resources should be released. I want to restore some render-target textures after the device is reseted, so I'm trying to save their data to D3DPOOL_SYSTEMMEM texture when device is lost, but I cannot call IDirect3DDevice9::GetRenderTargetData successfully because the device was lost. The DX debug report says:

"Failing copy from video-memory surface to system-memory or managed surface because device is lost. UpdateSurface returns D3DERR_DEVICELOST"

Is there another way to restore the D3DPOOL_DEFAULT resources after a device losing?