MaxCoderz

yea... phpbb2 is old

hurray!


...did my screens take too much bandwidth?

i had a bit (a lot, actually) of progress this week

because im lazy, and this site doesn't like 2 MB screens...

http://www.revsoft.org/phpBB2/viewtopic.php?t=1039

next time il actually upload the screens here, i promise

but i used istudio to convert it to hex

use a small delay (20ms) and use that repeatly

uhh thanks the engine is near finished, i need to word on the: bombs, 3 types more enamies, one is right-handed... but i still need to make a menu, and compress all levels... creating (copying..) takes about an hour, there are 111 levels... i may release another demo next week whit a few levels :yes...

already announced on UTI, now on maxcoders TM! anyway... for those who don't know, supaplex is one of the more famous versions of boulder dash type of games. features: its an app, 2 or 3 pages (the original had over 1 mb of data :excited: ) 111 levels (if i can fit them on the calc.... levels take 5...

<---- yava noob

from another thread:

King Harold wrote:Same thing probably, but maybe you could just put a Sleep in it somewhere, that would help.. Just sleep for 1 milisecond or something that's already a whole lot (seeing as most instructions take a fraction of a nanosecond..)

solution: use sleep(delay)
?

damn...

it was worth a try, tho

ok, this thread is old, but i got an idea:

cheap 'inc h' trick

can't you just swap the damn ram page?

Wesley wrote:Sometimes I hold my calculator and chant the words "feel the power" .

epic quote

*insert motivational speech here*

More than everything put together+1, because everything+1 = 255+1 = 0!

so...

triangle:
(5,0,3)
(5,8,4)
(2,4,5)

you calucate the points on the screen:
x=x/z
y=y/z

you get these on-screen coordinates:
(5/3,0)
(5/4,2)
(2/5,4/5)

then you draw the lines of the triangle, and fill it using scanline algoritm...

that makes sense, thanks

so... how does 3d on low-end machines work anyway?

you basely display an array of triangles?

people write 3d engines for it, beacause whit screen resolution of 1024*768 (= low) and 30 FPS, you need to calucate
1024*768*30=23 592 960 rays a second, that is more then the calucator has cycles in fast mode

you can image that shaving off 1 clock cycle saves alot of time