didn't run at 60 fps, and I like games to run buttery smooth.

dual 1.8 intel

8300 GS 128 MB

2 GB ram

Take the blur out and it will run much better; your window is a bit too large for a full screen blur pass.

I completely agree .Davo, add this. You know how.

Why would you would want to use lossy jpg's is beyond me. If anything this will slow your game down more than speed it up. Png's are pretty small to begin with, so I don't know what you are worried about.

once you've got the engine in place it shouldn't be too much work making the whole game.

of course it would. What about those scrolling maze parts? what about all the items? The overworld is massive, and having all those 3d boxes would probably crash the runtime, so you would have to split the overworld into many seperate layouts. It's still a ton of work to program everything in.

remaking the entire game would be a mighty task, I suppose he'll finish the first dungeon at least. It's a nice recreation of the classic, I must admit.

I've gotten these errors from time to time, and I don't know what they do or mean, so i thought i'd ping the devs.

When launching the runtime,

Error loading MENUBLOCK

or

Error loading APPBLOCK

occasionally appear and don't let runtime start. However, clicking ok, then re-launching supposedly fixes the problem.

I just got the error loading APPBLOCK one, and now it seems that my game crashes randomly sometimes. Any ideas?

Try the Tutorial for basic event knowledge.

Else doesn't work 100% correctly yet (at least I don't think so, haven't tested it in the latest build), so I would avoid using it. Also, I wouldn't use 3 ORs in a single condition, there could be problems with it.

Instead of using those ORs, just seperate each condition into there respective sub-event, and copy the action into each one. I know OR adds that ounce of neatness to the code, but I think there could be something wrong with using it like that, especially with the else condition at the end. Just program your own else condition with a variable as a workaround for now.

Just on a side note, The collision bug is still there. It happens less often now, but i'm still getting the occasional collision when an object overlaps the bounding box.

heh, nice one Davo.

System compare

--brick.count=0

next layout

I tested it and it really hurts the fps at the highest setting.

[quote:3g54tt1t][FIX] Collision bug in runtime

Anyone care to specify details?