# Why Change from one coordinate system to another?

When dealing with affine transformations, why do we need to change from one frame to another? What are some reasons. What are the pros and cons of doing this and the limitations if this was not possible.(Change of Coordinate Transformations)

• Can you give an example​ of the kind of coordinate system change you're talking about? We use a lot of coordinate systems in games — local, parent, world, tile, view, projected, clip, normalized device coordinates, screen pixel coordinates, texture coordinates, barycentric, tangent space, bone or blend space... — so covering the gamut in one answer would be a big undertaking. I imagine you've encountered coordinate transforms in the context of a particular application or feature in your game, so can you tell us more about this use case you'd like explained? May 25, 2017 at 12:10
• Cartesian to Cartesian May 25, 2017 at 12:14
• Most of the coordinate systems I listed are Cartesian (I neglected to even touch on spherical and polar coordinates or the various hex grid coordinate systems, oops!), so that doesn't narrow things down much. ;) It might help if you describe the specific game feature you're trying to implement, and we can tell you how coordinate transforms can help with that type of work. A fully general answer is liable to end up being quite vague and not very helpful or applicable, which is why I'm hunting for some more specific game context. Without this it looks a lot like a question for a math site. May 25, 2017 at 12:26
• Why do I have to change the frame of reference? If the object stays rigid but just translate to a different location but with different basis vectors. What is the reason needed to have different basis vectors. As in the picture, frame A is in different orientation than B. In contrast to just rotating, scaling and translating. May 25, 2017 at 12:38
• Nevermind, I guess I can say Frames of reference are particularly important when describing an object's displacement May 25, 2017 at 12:48