As a beginner, I've been toying around with my own home brew game engine for the last few months to learn the ropes of game programming. In the book Game Engine Architecture by Jacob Gregory there is code snippet that looks like

void AddAxes(const Transform& xfm, ...);

In Box2D there is a simple Transform structure that seemingly holds a Rotation structure and a Position (vector or point is unbeknownst to me).

On the other spectrum, Unity has their own Transform class that holds just about anything relating to transforming something (scale, rotation, translation, child/parent transform relations and helper methods).

Being notoriously hard to google, if I'd implement my own Transform structure, What should it contain? Is it just a general transformation container abstraction or does it hold some kind of meaning in game programming?

I'm up to implementing a debug camera system so I'm wanting to use this said transform for more general purpose than just adding axes to the canvas.

Many thanks

Fred

2 hours ago, PlanetExp said:

Is it just a general transformation container abstraction or does it hold some kind of meaning in game programming?

There are no rules as to what a 'transform' might contain. You could put parent child relationships as part of a transform, or you might not. It might include for example a 4x4 matrix, and / or a position, quaternion and scale, or just a 2d offset. What it contains will depend on what you are using it for. The needs of e.g. a 3d modelling tool may be different to a physics engine or highly optimized renderer. Indeed you may end up having more than one transform structure within the same program.

Box2D has no scaling because scaling is not useful for a physics engine most of the time. Unity has scaling, because their transform is a general purpose tool to place anything anywhere with any rotate/scaling/translation.

Thank you for such incredibly helpful replies! It makes sense to have a transform in the rendering engine to describe all general transforms that applies to your game objects (and other objects too) in one neat container. In hindsight it seem quite self-explanatory. Why Jason Gregory have it in their debug code in the AddAxis method also make sense: you'd put a set of axis in the world after it's been transformed -- if the axis don't end up where you want probably means you got something wrong somewhere.

Many thanks again! Learning game programming has been an exhilarating, albeit somewhat painful experience

Fred