Messages

Brings me back to my Amiga days!!

Thanks guys...wow!
I need to look into that Poly-ma-thingy!

Like the robot from that spill'berg film said... "...need more input!"

[Arrow keys]

This is my approach to smooth scrolling. This is my game I'm working on called The Legend of Blobo: Castle of Deceit. It works roughly like Symphony of the Night (PSX Castlevania.) Unzip everything and run the program.

Controls
Arrow keys = move / navigate menus
Z = cancel / attack
X = accept / jump
I = inventory
F1 = debug
F3 = display FPS
C = mega jump in debug mode

Let me know if it's the kind of system you're looking for. It is not tile based. It is object based. You can have infinity objects per map, and maps are infinite in size. This is possible at 60 FPS because the game only draws what's on-screen, including animated enemies. Objects can also have transparency and draw priority (e.g, in front of the main character.) Enemies react to objects on the map, such as falling until they hit a solid object or stopping and going another direction when hitting a wall. Objects can also move horizontally and vertically like moving platforms in Mario (this is experimental...) and there is HP and EXP and stats and equipment. It's a work in progress :3


<edit note: the attachment for me for some reason downloads as a .php file... renaming it to .zip allowed me to extract the archive. Maybe it's just a firefox / glb forums bug. lol >

Very nice indeed!
I loved the debugging option F1
Plus the superjump made me dizzy...

Nice and smooth...

So how do you use objects rather than tiles??

I am seeing that polyvector / newpolystrip can be useful and is used a lot but I dont yet fully understand what they are good for.
Are they for drawing only or other uses also...

Excellent!!

Love the editors and the code usage!
Hmmm New Toys!!!!

hi,

Use Debug <value> + "\n" to output the values for testing.

Also,
It's very similar in function to MS Access Debugging so If you read up on that you might get some good tips!

Great stuff! Thanks guys...
Will have a go with this soon!

Are 8x8 or 16x16 tiles the most common?
What is best to suit both Android & iPhone? Or does it even matter?

Hi,

I will be looking to do this shortly and wondered if there was a simple enough approach to making a scrolling screen containing a lot of sprite objects.

I could have the screen reset and show a new screen when the main sprite hits the borders but I want a smooth scrolling screen if possible...

Would I have to iterate thru the sprite x,y coords and update to simulate a scrolling effect?
I think this method would be heavy on CPU and cause a bad flicker.

Any other ideas?

G

I got it working !!

My calcs were wrong... my x and y of the sprite were correct (odd numbers)
but my waters sections x (odd) y(even)

So along the way I evened out a 'y' axis value.

I really need to use my debugger better from now on!!

Thanks Guys!

[BW]

Thanks Kitty,

But I am still a bit confused because...
I kinda do that with the current array except the block are multiples of the 16 x 16 sizes.

So a block could be 64 x 32, or 128 x 32 etc...

I then step through the screen in 16 x 16 blocks
which is like the [100][100] as x,y are divided by 16px simulating the screen as a 16x16 grided area.

When I collide I find that I need to loop through the whole array once again to test against the position before the collision and to the left and right of the 32x32 block (2 x 16px blocks)


I will try to explain in a diagram

B = My Sprite Block 32 x 32
W = Water sections in arrays with height of 32 but width varies in mulples of 16

B moves down 16px then accross from far left in blocks of 16 until it collides

START:
                             B

                     WWW
                WWWWWWWWWWWWWWWWW

COLLISION DETECTED:           

                     BWWW
                WWWWWWWWWWWWWWWWW

COLLISION ITEM IS MOVED UP AND PLACED IN POSITION:           
                      B
                     WWW
                WWWWWWWWWWWWWWWWW

HOWEVER THE IDEAL POSITION IN ABOVE IS:

                     
                     WWW     B
                WWWWWWWWWWWWWWWWW

This is due to having adequate water below and space above in equal measure...
So the collision is reversed and areas around need to be checked for collisions and empty squares...

Its finding the solution to this problem that I am struggling with...


G

Hi,

I have a screen divided in to 16x16 sections

Using for loops that are stepped by 16 from 1 to 800 and 1 to 512 (high)

An array of an objects is placed within the confines of the grid by a measure of 16x16 squares or a multiple of the same...

But the item I move around the screen (also 16x16) is not flush with some sections of the sprite array and every second section of the grid is out or incorrectly...any ideas??

Code (glbasic) Select Expand

FUNCTION hitobject: xx,yy

FOREACH w IN waters[]

IF BOXCOLL(xx,yy,16,16,w.wx,w.wy,w.width,w.height) THEN RETURN 1
NEXT


ENDFUNCTION

Bump!
Next help!

Hi,

thanks, in that case i shall post a bit of code...
What I am trying to do place an object next to a body of objects providing the 32x32 sections on either side of the object are free from other objects...
I think this is simple enough but am getting my approach wrong...

Code (glbasic) Select Expand

LOADSPRITE "castle1.png", 11
result% = 0


FOR f=1 TO 512 STEP 16

FOR n = 1 TO 800 STEP 16

//FOREACH test IN waters[]
FOR i = 0 TO BOUNDS(waters[],0)-1


// IF BOXCOLL (test.wx, test.wy,test.width,32, n,f,32,32)
IF BOXCOLL (waters[i].wx, waters[i].wy,waters[i].width,32, n,f,32,32)


// TEST SIDE SECTIONS
FOREACH leftside IN waters[]

IF BOXCOLL (leftside.wx, leftside.wy,leftside.width,32, n-32,f-16,32,32)=FALSE AND BOXCOLL (leftside.wx, leftside.wy,leftside.width,32, n+64,f-16,32,32)=FALSE



result = 1

ELSE
result = 0
ENDIF

NEXT

IF result = 1

DRAWSPRITE 11, n, f-16


GOTO scr1

ENDIF

ENDIF

NEXT

NEXT

NEXT

Hi,

I have a problem with my collision detections...

I have code (not at hand right now...) written that looks for box collision item against an array of items ... by iterating through screen section in blocks of 16 pxls

When it finds the item the collision should revert back to pre position and then validate that the 32 pixels of either side of the 32 px box is collision free before continuing....

Hope i made myself clear...

I expect that using array objects is the only collision method and that useasbmp and current pixel colouring cannot be checked to provide an alternative?

Checking the colour of pixels as test would be a nice way based on the useasbmp so that 100s of arrays do not need to be examined...

G.