Geometry is bent post-gameplay update, so after input, collision and resolution. If you're deforming verts in the vertex shader, you don't need bent traces like you're suggesting, because rendering occurs after game logic.
You're better off just using bent traces, which will be more accurate and given you're probably projecting spherically, more cost effective. Lastly, you don't want to fake bent traces with multiple traces, you're just going to add needless cost and inaccuracy (you still need to be aware of the curvature in your simulation and that has to come from somewhere after all, although thankfully it should be constant). One example is collision detection between two objects and that as an example will rely on traces and whilst you can get away with standard collision detection between objects that do not move a significant distance between frames as inaccuracy is probably within tolerable bounds (but only if the frame rate remains consistent and stable, which is not an assumption you should make), a fast moving object that can travel a considerable distance between frames will cause you issues. There's more to game physics than 'gravity'. Unity is designed for public use and because of that every aspect of the api is open and extendable and can easily conform to pretty much any project. They assume its like these other engines that were designed for specific use only in their internal environment and require source code and lots of people to do some drastic changes. I think there is a misconception from people who havent used Unity. If you do want a bent raycast for some reason its easy enough to make a raycast wrapper that shoots multiple rays to simulate a bent ray.
In most cases you dont want bent raycasts (which you would be forced to have with vertex deformation). Beyond that you just have to keep a players feet pointed at the ground which is also very simple. Why would you have to handle physics manually? All you have to do is apply gravity to objects which is an extremely simple formula.
0 kommentar(er)
