Farseer has one specific not always easy to deal with : your world is meant in KMS (kilo meter second) whereas your rendering is in pixel.
\nAdded to that, your world and rendering are two complete different things which does not make it easy to debug.<\/p>\n
This where the DebugViewXNA class kicks in : it will render your world \ud83d\ude42
\nThis and a few other things like stats, datas, etc.<\/p>\n
The how to use the DebugViewXNA class is rather easy :<\/p>\n
–add the project reference<\/strong> to debugview.xna.dll A video to illustrate switching between rendering and debugging.
\n–add an imports<\/strong> to FarseerPhysics.DebugView
\n–declare <\/strong>a _debugView As DebugViewXNA
\n–set it up<\/strong> in loadcontent (for instance) :
\n
\n_debugView = New DebugViewXNA(world)
\n _debugView.AppendFlags(DebugViewFlags.DebugPanel)
\n _debugView.DebugPanelPosition = New Vector2(15, 15)
\n _debugView.DefaultShapeColor = Color.White
\n _debugView.SleepingShapeColor = Color.LightGray
\n _debugView.LoadContent(GraphicsDevice, Content)
\n<\/code>
\n-use it in your draw method (after your spritebatch.end) :
\n
\nDim projection As Matrix = Matrix.CreateOrthographicOffCenter(0.0F, graphics.GraphicsDevice.Viewport.Width * DrawablePhysicsObject.pixelToUnit, graphics.GraphicsDevice.Viewport.Height * DrawablePhysicsObject.pixelToUnit, 0.0F, 0.0F, 1.0F)
\n_debugView.RenderDebugDataVB(projection)
\n<\/code><\/p>\n
\n