dave, i thought you used blitz? that should be able to handle 3m tiles easily
"Say you're hanging from a huge cliff at the top of mt. everest and a guy comes along and says he'll save you, and proceeds to throw religious pamphlets at you while simultaniously giving a sermon." - Dustin G
Even assembly would have a tough time with 3 million tiles. Even if they were small, 16x16 tiles (256 pixels), that's 768,000,000 setpixels to draw them all.
Mind you, you wouldn't draw them all at once. Assembly might be able to iterate all the tiles in a reasonable amount of time (<1ms) but something like Darkbasic is going to be way slower, a lot of speed is lost in interpretation.
he's not drawing them all at once. He could just code it to only deal with the tiles on the screen
"Say you're hanging from a huge cliff at the top of mt. everest and a guy comes along and says he'll save you, and proceeds to throw religious pamphlets at you while simultaniously giving a sermon." - Dustin G
As I said, you would probably still need to iterate all tiles to check which are on screen. Maybe a short wait in assembly but interpretation really kills the speediness of loops (unless you're using something like Java with compile on-the-fly)
last_blockx = first_blockx+20 // not 19, in case there are blocks that are only just on screen
last_blocky = first_blocky+15
for x = first_blockx to last_blockx
for y = first_blocky to last_blocky
...
next
next
Edit: woo lots of edits
Edited by the Author.
"Say you're hanging from a huge cliff at the top of mt. everest and a guy comes along and says he'll save you, and proceeds to throw religious pamphlets at you while simultaniously giving a sermon." - Dustin G
Wow, I'd hate to see how you allocate your memory. Anyway, I thought he wanted to do something with EVERY tile, not just the ones on screen which is easy-peasy to do?
Advertisement
Post Reply
Edited by the Author.
