MultipleChoice wrote:> @fldr , @tunepunk
looks promising! Here is an example capx i did for isometric, multilevel and multilayer (one screen) purposes. There is a solution for auto z-indexing according to the position.
Very effective, with no collision checking at all check it out, it might inspire you the right direction. Let me know, if it helps.
Passing beneath/above object (being on different floors)
Finally all the basic features are included. Not using solid-behavior or pushout absicly at all, since you have to be able to pass under walls, which must be colliding with the player on the same floor. (There still can be some reduced even now, eg "guides"). Players can just swap places, like with the wall being put in the foreground or background according to any layers, which is not implemented yet, but easy from here.
Obviously, you can work more with collisions, also adding solid behavior -- which is more stable and might be necessary especially on slow devices to prevent passing through walls when slowing down to few ticks per sec. --, and just use this method when both players are on different floors, to disable solid temporarily, but enable the collision-control-lock. But I don't know, how many objects you are going to end up with.. it's always good not to have too many collisions, especially, if you plan to play it on phones/tablets. So its a balancing...
Formula, Family and Harmony
Also, it is just a sketch, I'm sure it can be optimized a bit. Sorry for any longer Formula, but I try to work with families and relative values, to build up a proper engine with all object types are being easily replaced or added easily, without further coding basically, so anyone can use it to start with. Of course, most of them will be registered, to provide some more transparency, (as I did already in this file). I am also thinking of putting them as a collection online somewhere in this forum, since I really enjoy developing different ones and got a bunch of them by now.
Player A = AWSD
player B = L/R/UP-ARROWS
newt wrote:Its too bad you can't have a an invisible 2d layer, and just project the isometric objects to the isometric coordinates.... oh wait.
today i started working on an isometric tower defense game, using the lovely assets by Kenney.
Didnt got much yet, only a map, some enemy walking the path and making sure everything has the wright z-order. Isometric game design is totally new to me and i had a hard time figuring everything out with this damn z-order and where to place the tiles
but anyway, you can see what i got here: http://fldr.de/tower3
newt wrote:First you make the game in 2d topdown.
Each object there would have a isometric counterpart on another layer that is offset to isometric coordinates.
iso x= 2d x- 2d y *(tile width/2)
iso y = 2d x+2d y *(tile height/2)
Let me add containers work pretty good, except the container spawns on the parent objects layer.
QuaziGNRLnose wrote:If you use Q3D for rendering, it implements a proper Z-Buffer and would correctly render things based on X-Y-Z without the ordering trouble . It has a 2D sprite object you could use so its actually works well for isometric stuff too, and also gives you the freedom to add 3D stuff if you have to and use 3D collision detection, you could also use normal maps on 2D planes and add lights too. There's a bunch of features that would help with this type of project, since ISO is really mostly just 3D game development with 2D sprites instead of models.
Users browsing this forum: No registered users and 2 guests