BEPUphysics

What I am observing is that if I throw the ball towards the ground, it skids to the edge of the field, then goes past the field for some distance and then falls off. I expect it to fall right when the field ends, because the field model is kept at default scale. Why this might be happening?

Like real balls I would like to implement a rotating ball when ball moves along ground, but right now, after ball hits the ground it mostly slides and doesn't rotate? What is the appropriate way to make the ball rotate when its moving along the ground?

I am also confused when to use StaticFriction and when to use KineticFriction in real game dev scenarios.

what are the ways to implement this (represent the human model with bat in Physics Environment and have relatively precise collision detection for bat) in Bepu.

For fielders who stop the ball, I am thinking of creating a "bigger" box around the player with center positioned at Player's center. Then when the ball collides with the outer Box, I can have Collision event handlers to play specific animation, like dive for catch or simply bend down and pick up ball

then I need to check for collision events at mesh level(collision with hands) to pick up the ball.

Once that is done, the fielder needs to throw the ball. For that, the game knows the approximate destination , speed of throw, but the throwing angle (projectile) needs to be calculated. Is the whole thing possible and do we have helper functions to calculate these things (like throwing angle).

            //StadiumModel
            stadia = new StadiumModel(content.Load<Model>("ThreeDEE/Models/Stadiums/Base/stadium"),
                new Vector3(0f, 0f, 0f), //Position
                new Vector3(0f, 0f, 0f), //Rotation
                new Vector3(1f , 1f , 1f), //Scale
                sceneEngine.GraphicsDevice,
                "Stadia1",   //Descriptive name
                1); //ID for internal use

            //Create a physical environment from a triangle mesh.
            TriangleMesh.GetVerticesAndIndicesFromModel(
                stadia.model, 
                out vertices, 
                out indices);

            //Give the mesh information to a new StaticMesh.  
            var mesh = new StaticMesh(vertices, indices, new AffineTransform(new Vector3(0, 0, 49)));

            stadia.PhysicsEntity = mesh;

            //Add it to the Environment!
            PhysicsEnvironment.Add(mesh);

The ball should rotate given the default values, unless the ball's inertia has been manually set to infinity or the friction of the involved objects has been set to 0. Is it truly not rotating, or is the graphic just not rotating?

I tried with a cube model and the cube model rotates when falls at odd angles. But this ball model is not rotating. I haven't tinkered with any values. The texture is mapped to model and models transformation is dependent on the entities transformation as well, so the graphics should rotate too.

I almost got the idea of implementing a human body using capsules, but I didnt understand what to use to represent a bat. Would a cuboid work well? Ofcourse the physics cuboid would be slightly bigger than the graphical bat to help in shot making.

Is the problem of attaining precise or atleast 60% precise Bat Edge/Ball collision common to all physics engine or is this specific to Bepu's implementation?

In physics engine, is it possible to simulate that, so that relatively lighter mass objects don bend it too much when hit (the pole dosent get uprooted, but may get angular displacement), whereas larger mass objects or faster moving objects can make it fall (or uprooted from ground)

das_vicky wrote: So I have a 3D model of the playing field (implemented as a thin cylinder), for which I created a StaticMesh (I assume this is correct way to go for a playing field). I have a 3D model of a ball (implemented as a sphere). (...) What I am observing is that if I throw the ball towards the ground, it skids to the edge of the field, then goes past the field for some distance and then falls off. I expect it to fall right when the field ends, because the field model is kept at default scale. Why this might be happening?