2) Normally, even the characters are prerendered, but if you wanna use 3d characters, use .3ds-file format. It is an Max-export format and easy to read. You can find some information on www.wotsit.org .

3) You can use shadows in iso-engines without D3D, but the algorithms are mostly really complex. I guess Geoff wrote something about on www.lupinegames.com . I did never use lighting and things like that. But for example for a limited viewport, you need 2 different maps, one with the colored map and one monochrom one, and then simply use rays. This shouldn't be such a big problem, but it's slow, I guess. As I said, I never tried it out. I've seen some more article on this topic, but I'm not sure, maybe www.perplexed.com/GPMega/ ?

CU

------------------
Skullpture Entertainment
#40842461

there's many a programmer who would like to make realistic shadows, in iso, in 3d.

and its possible, of course.

but what a lot of programmers forget--you dont have to be perfect. you just have to look "good enough"-- the people who are playing your game arent going to notice the little inconsistancies you do.

for example, diablo.

after you read this, play it. on levels 1-4, make your character go around one of the pillars thats in the middle of the rooms.

you will notice that while the lighting algorithm is still in play, the shadow of the pillar remains in a fixed spot.

had you noticed that before? maybe, if you've really looked at diablo from a critical programming standpoint. if you were just a player, you wouldnt have noticed.

you can do shadows, and you can do pixel perfect shadows. however, doing them in realtime is not viable, nor is it necessary.

when people play your game, they arent going to say "wow, those shadows are perfect! this game rocks"... of course they wont. they'll talk about how much fun your game is to play, and they will forgive (if for some reason they are aware) any little shadow inconsistencies you may have.

of course, this is not to say that you shouldnt seek SOME resemblance to realism. i'm just saying that perfection isnt the goal here.

there IS a clear difference. 3d does perspective correction, and iso does not.

however, there is also a clear similarity-- they are both 3d projections.

the tiles themselves (the little diamonds) should probably be bitmaps of some sort. also, depending on circumstances, the objects and creatures should be either 3d, or bitmapped.

and which one you use depends on the following criteria: polycount vs animation frame size and animation frame count

3d images can be manipulated, so that no matter what the poly count, you dont have the problem with storing the animation frames.

however, a large polycount will be a lot slower than a prerendered bitmap.

however, if there are a lot of animation frames, and/or the animation frames are large (big creatures) then the amount of memory is way larger than that required for a 3d object.

so, you have to balance between these...

for example, static objects, having only 1 animation frame, may as well be bitmaps. since they do not move, why deal with the polys?

however, a human figure, being flexible and mobile, may need to face 16 directions, and have 4 animation frames for each direction's movement, not counting attacking or any other type of action, so you might want to make it 3d.

also, today, there is less of a premium on memory... its cheap, plus you can always use RLE bitmaps.

however, 3d hardware is more prevalent, and hardware assistance more commonplace.

so, i say... do what looks good, and do whats fast. thats the only thing players pay attention to anyway.