There’s at least few popular approaches to C++ based RTTI (aka Run-Time Type Information) implementation in games. The goal of this post is to discuss strengths and weaknesses of major ones.
But before that let’s have a look at some of the most common uses of RTTI in games. In fact they are not much, if at all, different from any other, non-game related, project.
(a) Run-time type checking and instancing.
Being able to check what’s the actual class of an object is often useful functionality for gameplay programmers:
bool Object::InstanceOf(Class* _class) const;
Another useful feature is ability to instantiate an object knowing its class name:
Class* ClassManager::FindClassByName(const char* className);
Object* Class::CreateInstance();
To implement above basic RTTI functionality, we’re usually required to derive all of our game classes from some base Object class. Supporting multi-inheritance is possible but typically avoided because in most cases it’s just not needed but would make things a lot more complex otherwise.
Reality Prime’s dev blog shows basic implementation of such RTTI system.
(b) Automatic serialization of objects and their attributes.
Instead of implementing custom Read() / Write() methods for each class where every property is manually processed, we can now (with RTTI system in place) implement generic Read() and Write() methods that will work for all classes. Alternatively we can write single Serialize(Serializer&) method that would either read or write (or do other things) depending on implementation of Serializer.
But while this feature sounds great it has one serious downside – very limited support for data versioning. Imagine one day you decide to change some ‘int m_Name‘ attribute into ‘String m_Name‘ attribute. How would you want your game to load the old data and convert into new format? Would you want to perform some kind of ‘offline’ conversion by running hacked version of the game over all of the data? If so, you’d have to do so for all of the relevant game data files at once. In a big team working on a game that is obviously a challenge because the person performing conversion must assure no one else has got any important local changes on their PC.
Or even worse, suppose your game has already been released and there’s tons of content (e.g. levels, quests, puzzles) created by the community. Simply changing the format of the data expected by an updated game executable would break all of that content unless you provide way to convert from the old format into new one.
To some extent this upgrade process can be automated as demonstrated by Insomniacs (unfortunately, to my knowledge, the actual explanation of that can only be found in GDC slides or articles in paid magazines). Their system of lazy upgrade script evaluation assures that every asset you get from asset database is always in latest format.
Having said all that I should point out that some projects don’t need robust data versioning at all and therefore may well benefit from automatic serialization. This is especially true for small projects without support for community created content.
(c) Game editor integration
Another great benefit of RTTI is that it allows class attributes to be automatically exposed for editing within some kind of visual editor. This feature may require additional editor specific attributes to control how each particular type shall be edited. For example you may want to have nice color selection control instead of having to manually type in individual RGB values; or you may want to limit min and max values of fog intensity by 0..1 range, etc.
This best works with WYSIWYG game editors which for the purpose of editing use the same C++ classes as the ones used in the game. There’s no need for intermediate communication layer and every editing action changes the game object directly. As with anything, this has some advantages (mainly easier and cleaner implementation) as well as disadvantages (less efficient and editor-polluted run-time code).
Manual serialization
A well known example of an engine that supports features listed in all above points is Unreal Engine 3. As for the automatic serialization, it only does so for Unreal Script classes. For their C++ classes they use more “manual” method which does make a lot of sense because it allows for a flexible data format versioning. Here’s sample code that demonstrates mentioned “manual” method:
// Deserializes instance of Dog class
void Dog::Read(Reader& reader)
{
// Deserializes all base class attributes
Super::Read(reader);
// Read name value
reader >> m_Name;
// Read color value; only if data has it (old version didn't)
if (reader.GetDataVersion() >= ENGINE_VER_DOG_ADDED_COLOR)
reader >> m_Color;
// Read height value; only if data has it (old version didn't)
if (reader.GetDataVersion() >= ENGINE_VER_DOG_ADDED_HEIGHT)
reader >> m_Height;
}
Implementing automatic serialization that would handle all kinds of data versioning correctly is not possible simply because it’s only programmers who know how data changes between versions. The major limitations of the automatic serialization are as follows:
- only simple type conversion handled correctly (e.g. int into float)
- name changes cause new property to be added and the old one to be removed (thus losing the data)
On the other hand, by manually handling data upgrades, one has full control over data conversion.
Type information generation methods.
We now know why RTTI might be useful. But how do we create it? Again, there’s at least a couple of ways – from manual intrusive macro/template based ones to automatic offline ones.
(a) Manual intrusive macro/template based method.
One very popular way of creating RTTI in C++ is by adding a couple of special macros and functions to every class. This may look something like this:
Header file:
// Sample Dog class
class Dog : public Animal
{
// Tells RTTI that Dog inherits from Animal
// Also defines some helper functions
RTTI_DECLARE_CLASS(Dog, Animal)
private:
int m_Height; // Dog height
String m_Name; // Dog name
};
Source file:
// Function declared in RTTI_DECLARE_CLASS macro
// Adds all attributes to class RTTI
void Dog::RTTI_InitAttributes()
{
// Initializes m_Height attribute; figures out type using templates
RTTI_INIT_ATTRIBUTE(m_Height);
// Initializes m_Name attribute; figures out type using templates
RTTI_INIT_ATTRIBUTE(m_Name);
}
The actual initialization of each class is best done manually – something like this:
void InitMyClasses()
{
Object::RTTI_Init();
Animal::RTTI_Init();
Dog::RTTI_Init();
Cat::RTTI_Init();
[...]
}
To keep things short I’m going to skip implementation of RTTI_DECLARE_CLASS and RTTI_INIT_ATTRIBUTE macros. The nice thing about attribute registration is that using C++ template specialization it’s totally possible to automatically deduce type from a variable – this is useful because it means you can initialize all attributes with call to the same RTTI_INIT_ATTRIBUTE macro.
The major downside of this approach is that the programmer needs to maintain an up-to-date RTTI initialization code. With the help of automatic attribute type deduction and some C++ macro magic, this can be made safe and less inconvenient but it’s still not perfect.
(b) Automatic – parser based.
One totally different approach to building RTTI information is by generating it offline and storing it in a file which is then loaded by run-time. There’s plenty of C++ code parsers available (e.g. Wave or GCCXML) available which you could use but there’s still some coding required in order to extract selected types for RTTI purposes. You’d also need to integrate C++ parsing step with your project building, so it wouldn’t need to be done manually.
One issue with this approach is that the RTTI data generated during preprocessing step might potentially differ between project configurations / platforms. But since gameplay code is typically platform and configuration independent this is probably a very minor issue.
The nice thing about this approach is that, provided parser can extract comments attached to particular class or attribute, it’s possible to use comment based custom annotation language on a per class or attribute basis. This can be useful in a couple of different scenarios including when you want to mark some attributes as serializable or when you’d like RTTI for a specific C++ class not to be generated at all. Annotation technique is something that is widely used in other languages such as Java or C#.
(c) Automatic – debug info based.
Yet another approach to building RTTI information is by extracting it straight from debugging information files such PDB on Windows as described on Maciej Sinilo’s dev blog. It is a very similar method to the one presented before but one small advantage of it is one doesn’t need to implement an additional parsing step themself which, depending on how easy parses integration is, might save a lot of work.
Summary
As it often happens, there’s no best solution that would fit all projects. Every game is different and there’s games that don’t need RTTI at all.
For larger game projects with heaps of gameplay editing involved I’m leaning towards Unreal Engine 3 approach i.e. manual RTTI including manual serialization on the C++ side and automatic RTTI with automatic serialization on the scripting side (assuming there is one). Many popular scripting languages already have full reflection support in place which makes things easier there.
For projects where WYSIWYG editing isn’t priority, full blown RTTI system with attribute level information may not be necessary at all. Even more so with projects where in-place serialization (one block of memory used for multiple objects) is being done making it mostly redundant to maintain any kind of attribute information at run-time.
Gamedev Coder Diary 