User Tools

Site Tools


This is an old revision of the document!

Compiling RTSimpleApp

This application tests audio, the particle system, text input and buttons.

It illustrates how to use entities and components and is a good sample to “clone” when starting your own project.

You can compile and run it by following the directions from RTBareBones with one additional thing:

Installing the FMOD library

If you want to hear anything, you'll need FMOD.

Alternately, you could change AudioManagerFMOD g_audioManager; in App.cpp to AudioManager g_audioManager, this is a dummy audio manager that doesn't actually play anything. Useful for when you want to disable sound code alltogether to debug something.

Let's assume you want FMOD - for legal reasons I can't include it with the sdk, but it's very easy to download and copy into the right place.

First download the Windows 32 bit version of FMOD and install somewhere. (it's ok if you have a 64 bit version of windows)

Locate the directory with file explorer and cut and paste the entire “api” directory into <main proton dir>/shared/win/fmod

Oh, and also copy fmodex.dll from the api directory into <main proton dir>/RTSimpleApp/bin or else you'll get a dll not found error.

The app should now compile!

Building resources

Uh oh, if you ran it you probably got an assert about being “unable to init”. If you check the MSVC output window you will see:

ERROR: Can't open interface/font_trajan.rtfont.
Can't load font 1

What's going on? We forgot to build resources, if you look in the bin directory there is no audio or interface directories. Unlike RTBareBones, you have to run a script to build the font(s) and convert the images (mostly .pngs) to our own .rttex format.

Use file explorer to navigate to <proton dir>/RTSimpleApp/media and double click update_media.bat.

A command prompt will open processing all the files in the RTSimpleApp/media/interface tree and copy the 'final' versions to bin/interface. (audio and game dirs as well, although game will be empty)

Why do it this way?

You don't have to. But it's flexible. Would you like to see what the game looks like using 4 bit .pvr textures for your iPhone build? Easy, change a setting in update_media.bat and you can know. .oggs instead of .mp3s? 16 bit raw textures on Android except for a few important images that should be 32 bit? A .bat file makes it easy to specify things without ever really modifying your master resource files.

Or you may need to non-square textures to be raw data, but square textures to be PVRTC compressed for speed for only a certain platform. (iPhone, cough) RTPack.exe is very powerful and can do this kind of thing with ease.

Remember, when you change a .png, you change it in media/*, and then must run update_media.bat to update the bin versions before you will see it in game. Android/iPhone/WebOS scripts will grab the media from the bin directory. (If you really hate that, yeah, you can just write bmps directly into the bin directory yourself, but you lose the advantages of RTPack.exe being able to convert from nearly any filetype to .rttex and other advantages like padding images to be power of two)

Processing is fast because the RTPack.exe processor can detect changes and only convert changed/new files.

Landscape vs portrait

Assuming you built your resources right, you'll see this. Uh oh, it's sideways because in App::Init() it has:

SetLockedLandscape(true); //we don't allow portrait mode for this game

This means it will force landscape mode. It will do a 180 flip if an iPhone is held upside down, but won't flip to portrait modes.

Before you sustain serious neck injury, set “g_landScapeNoNeckHurtMode = true” in main.cpp's InitVideoSize() function.

It should now look more like this:

Demonstration of using the particle system, click (will be touch, when on a device) the screen to add an explosion.

Text input

A fake highscore screen to test text input. Click the text, then use your keyboard.


It also has options to turn on and off ogg/mp3 background music.

Automatic scaling to fit the screen

It also demonstrates one more interesting thing - auto stretching. This app was designed for 320×480 “primary size” (before rotated to landscape) but will automatically adjust input and rendering to any screen size thanks to a single line of text in its App.cpp:


To see the stretch in action, change the video mode in main.cpp “Nexus One”. You should see…

You should see it properly stretches things to match the screen size.

proton/win_setup2.1288142742.txt.gz · Last modified: 2010/10/27 01:25 by seth