I know you sort of answered this before, but a 3D sprite object would work right?
I mean an object that works like a sprite but uses a 3D character model (and animations) instead?
Would that have problems being implemented (such as collisions and such)?
I'd imagine not since it would behave like a 2D sprite (collisions and all) but use a model instead of a sprite. But then again, I'm no genius.
That's one of the things I hated most with you know who's product, oh what the heck, actually I mean MMF. They had a 3D sprite object, but it was very poorly implemented and they never did anything with it (but then again, their engine couldn't really handle 3D in the first place while Construct is made for Direct X9).
Like I mentioned before, I want to make a game like Contra: Shattered Soldier (2.5D platformer). I don't like working with sprites. I'd rather use a 3D model (and I don't mean one prerendered as a 2D sprite, because that looks.. yuck) because it would be a lot easier to work with. I would rather animate a 3D model (easier) then try to animate a sprite (very hard for me). Plus I think it looks better and much more "modern", which suits my style better.
Anyway, sorry to ramble off like that but to get back to the point: Would a psuedo-3D type of sprite object would have the same collision problems as a full 3D implementation? You know, just a 3D model that works like a sprite object (except displays a polygonal model rather than pixels)?
Because if anything (as far as 3D goes), if this program could have a feature like that (and I know it CAN, but rather if it DOES if not anything else), it would make my life a lot easier and make me one happy camper.