128x512 tiled background = 0.25mb VRAM

512x512 tiled background = 1.00mb VRAM

It's nice to know this for sure

To note: Changing layouts is really what you'd want to do, as it goes just the way that Castlevania's rooms behave: every enemy is reset.

-Make your player and player related objects global so you can reposition it.

-make an external event sheet for generic stuff that happens in every room

-include this external event sheet in every room

I'm thinking that you will probably have to split objects into uniform sized pieces. This may be why isometric games use tiles that are all the same size instead of having some large and some small.

I've read this plainly stated in some documents regarding classic isometric games =(

Also, I just got the reasoning why Y-sorting could never possibly work with different heights.

Imagine an iso box stacked on top of another iso box, correctly sorted so that the one above is drawn on top of the other one.

Now imagine the box on top going down. It's not moving on Y, only on W (or Z or whatever). As soon as it goes below the other box, since Y has not changed, it will be incorrectly sorted, drawn above the box that sits on top of it.

SO you have GOT to involve height in the equation. I'm still on that. I just know now that Y-sorting only works for level objects.

replace flat raster billboards with raytraced images.

Yep. Slow.

Uh, I'm probably asking a really stupid question but can't you just drop the .dll you need into the folder that your game is in and zip it up?

Yeah but for PyGame (and other Python dependencies) it's not so easy, it would seem.

Policarpo. Yes, I've read his work before. Hard to forget that name.

It's basically raytracing, just as slow. I mean slow like to give the latest cards a run for their money. Really.

I really think installing python to play a game is overkill for any user.

I know I have ignored games that required me to do that before, it's almost like requiring to install visual studio.

I would not use python in my games if this was the case.

EDIT:

Also, they might have another version installed. Ick.

hey that's a sweet example!

yeah you're doing exactly what I am.

We're probably having the same issues, you can see my results in the 2.5d movement thread, there's an exe.

2.5d mov. is essentially iso platforming, done per pixel, which seems to be exactly what you're doing too. Can you post a .cap or an .exe to see your results?

My current line of thought is that there needs to be some fixed relationship between height and depth or it will never sort correctly. Like... a cube size. Which is a bummer, because doing tall or long moving objects that collide becomes a hassle.

Ordering.

You're setting body parts to the torso, THEN moving the torso to a new position.

You should move the action that sets the torso position above the others.

thank you thank you and YES I've spent time thinking if and how I'll continue working on game related stuff =/

install the update even if you think you have the latest.

the installer will MAKE SURE that you DO have the latest.