Prevent Clipping issues in first-person with Animations.

A common issue game developers face is clipping. You’ve probably seen this in games where weapons like guns or axes pass through walls, doors, rocks, or other objects. It’s a common problem, even in AAA games. The most popular solution is to render weapons or objects on top of everything else, which works well enough and for most players won't notice. However, it’s not ideal in first-person games where the camera basically can't move as the third person can. I decided to tackle this differently and create a new (well, not entirely new) approach. In my solution, whenever an object like an axe hits another object, it immediately backs off to prevent clipping. How does it work? The system revolves around the three animation stages: Start, Break, and End. Start: The animation begins (the axe swings down near the legs). Break: If a collision is detected using raycasting during the swing, the animation transitions to this stage. The break animation essentially interrupts the motion and smoothly transitions back. End: The final stage, where the object resets to its original pose. (If break didn't play) To achieve this, you’ll need to carefully control how animation frames are rendered. For instance, in the script, you can calculate the normalized time of the animation and reverse it when transitioning to the break stage. This way, collisions feel natural and eliminate clipping entirely.