What do you mean? Number of tris and resolution?
Both as small as possible without destroying the look .
For medium important stuff I´d say around 500 tris and a resolution of 256*256. If you are talking about the scale, 1 unit = 1m does probably do a good job. Float should give enough precision than for small and for big objects, as long as you don´t have distances of lightyears or something .

If you´ve got any ideas for features, feel free to request them here: http://sourceforge.net/tracker/?group_id=318519&atid=1339401 (needs a sourceforge account, to add stuff)

I meant the number of tris and resolution. Thanks.

I have to think about what I would like to see next.
Will need some time to get familiar with sourceforge, too.

I finally got some first stencil shadows to work. They don´t yet work with more complex objects due to the kind of normals the shadows need, but that is going to be easy to fix. A bigger problem is, that my silouette detection is quite slow at the moment. There is space to optimize it, but I am not sure if that is going to be enough.
However, here is a first screenshot:


Fixed the normal "problem":


and some house I´ve thrown together in blender (shows pretty well, that things are slow at the moment^):

I guess that 1GHz will be too less anyway to make reasonable framerates in games for smartphones.
More appropriate is probably a safe decal shadow sprite which sticks to the surfaces.
But, nonetheless, any progress in this project is welcomed!

Well, Doom 3 worked well with my 800MHz CPU and relied heavily on stencil shadows. I am pretty sure that it can still be optimized a lot. It is just well posible that my current approach while being very easy, is most probably also the slowest one .

Okay, then go on with implementing fast animation routines!
(But, you already know my even deeper feature wishes. )

I came up with an idea to precalculate the slower parts of the silouette detection, which basicly works the same way as before but A LOT faster. It is quite memory consuming, but I doubt that this will ever be a problem. That precalculation is kinda slow, but only has to be done once and is independant of light and model positions and orientations.
The spacecraft on the following screenshot was running with about 0.1fps with shadows before, so I´d say that this is a big improvement (the scene should have about 2.5k triangles, maybe a bit more):


And another one (silouette detection is really fast, but rendering of the volume needs some speed up):


And one more

Looks quite nice, but still, you can only develop on a mac, can't you?

Inspired by the epic citadel demo, I just created a small sample project for iSDGE presenting a basic reflection.

The render to texture is quite slow for some strange reason I don´t understand, but I hope to find a solution...

do you currently working only on the iOS version? or do you develop the Android version parallely? or will you port it afterwards?
(Asking, just got new Android phone )