> Even if you don't work on the game physics team, even if the company is already committed to using a third party physics engine, they may argue that your engi

> Even if you don't work on the game physics team, even if the company is already committed to using a third party physics engine, they may argue that your engine belongs to them. Because it's trivial to argue that the ambient knowledge and literal intellectual property that went into developing such an engine were as a direct result of your employment. The conversation at the water cooler. The knowledge that Employee X is having a frustrating time with verlet integration and collision detection. The knowledge you built-up working with great people over the last 3-4 years etc.