FIFE forums

General Category => Introduce yourself => Topic started by: clfaustus on October 06, 2014, 09:24:37 pm

Title: Hello FIFE community!
Post by: clfaustus on October 06, 2014, 09:24:37 pm
I'm new FIFE forums, but I've done quite a bit of research on FIFE and I'm definite that its versatility is exactly what I'm looking for to design my game. I'm doing a tactical sprg like Final fantasy tactics or X-Com but with a city building element. I'm not the best programmer and am relatively new to game development so if you would like to help me with my project, are interested, or want to offer some criticism or advice on what I've have so far; come check out my blog. (
Title: Re: Hello FIFE community!
Post by: helios on October 09, 2014, 09:54:23 am
Welcome clfaustus :)
You are right, it's possible to create such games with FIFE. If you ran into problems or have other questions than feel free to ask them away.
You can join our IRC channel or ask here.
Title: Re: Hello FIFE community!
Post by: clfaustus on November 01, 2014, 12:48:16 am
Thank you for being so helpful everyone here in the FIFE community seems really great. Sorry how I so mercilessly plugged my project. I've been seriously programming for only a little while, but I'm very passionate about my project and was just trying to see if I could find any benefactors in the forums. I'll be sure to rely on the technical discussions so I pray that everybody can have patience with me. Now unfamiliar with game design as I am I would like to know what the upper limitations of the SDL and GL renderering features of FIFE. I have noticed that the rio de hola, zero_projekt, and unknown horizons all seem to bear graphics very similar to Black isle's infinity engine, sort of a 90s look. Will the engine be able to handle higher pixel count hand drawings  and multiple in battle idle animations that I have planned. Will there be huge slowdown? I apologize for the lack of specificity in my question or if there is a glaring answer I'm simply ignorant of. Thanks again for your patience. :)
Title: Re: Hello FIFE community!
Post by: helios on November 01, 2014, 03:09:28 pm
Hey clfaustus,
I'll try to answer the questions and explain the correlations.
FIFE is a 2.5d engine and currently there is no support for 3d, sorting works mainly with layers. Maybe we will add support for 3d Models in the future, simply to reduce the amount of needed frames for animations. In the good old days the most engines had only 8bit for RGB(A), that means only 255 colors in combination with a color palette. A good example is Fallout 1 and 2 from Black Isle.
But FIFE have support for 16 and 32bit so the color space is much larger. The drawback is that it needs more Video Ram for the same amount of graphics. Little example: A texture with a 1024*1024 size needs 4MB with 32bit depth but only 1MB with 8bit. FIFE will not limit you but your hardware will ;)
So you should thinking about the amount of animations you need and about the frame count and size. Lets say you use a hexagonal grid, you have one animation set for a char that should have 8 actions (stand, walk, run, shoot,...) and each action consists of 30 frames, each with a size of 200px*200px.

Example calculation:
Code: [Select]
200px * 200px * 32bit / 8 = 160000 byte
160000 byte * 30 frames * 8 action * 6 directions (hexgrid) = 230400000 Byte ~ 219,73 MB

As you see that's a lot. In case you would have 10 different fully featured sets than it would eats up 2,2GB. There are some tricks (like ColorOverlay ( but at the end you must limit the amount.

The difference between SDL and OpenGL is that OpenGL have hardware support, so it should be much faster. In case of FIFE the SDL backend is more a fallback in case the platform has no OpenGL support.

It should be no problem to have multiple battle idle animations. You have different options to speed up things. Like your ground titles should be quite large and you should try to combine textures, that belong together, in a texture atlas. Another point is the size of the viewport, if you want to see the whole map at once the rendering is slower.

You can take a look at fife/tests/fife_test, start the press F10 and write in the console: start benchmarktest
In the example are 1000 skels with an idle animation. You could change the amount to 10000 or more and check the FPS.