16 replies to this topic

[Impaler_26]

I wanna make a game with an up-scrolling playfield and made a few tests. With a normal sprite my test-file works fine but when i use the "player1color" option i get a display-glitch in the lower area of the playfield. It disappears when you move the sprite to the bottom.

So my question is can i use "player1color" and "pfscroll up" together or is it too much to handle for bB?
Maybe i just made a stupid mistake i overlooked?

I hope someone here can help me with this!

Attached Files

•  chim.bas   1.48K   35 downloads
•  chim.bas.bin   2K   46 downloads

Edited by Impaler_26, Tue Jul 29, 2008 7:45 PM.

[Random Terrain]

I want you to know that I have a fix for your problem that I yanked out of another program I'm working on, but I have to adjust the code for it to look right. It's on the way.

[Impaler_26]

That's good to know! Thanks in advance!

[Random Terrain]

Sorry it took so long. I had to go to the dentist and get some sleep, but here is my version with the glitch removed:

 chim_2008y_07m_30d_1817t.bin   2K   61 downloads
 chim_2008y_07m_30d_1817t.bas   3.1K   51 downloads

[Impaler_26]

Random Terrain, on Thu Jul 31, 2008 12:26 AM, said:

Sorry it took so long. I had to go to the dentist and get some sleep, but here is my version with the glitch removed:

chim_200...0d_1817t.bin
chim_200...0d_1817t.bas

Thanks for your help, it's very much appreciated!!

Your version also answered a few other questions for me so now i can finally start making this game!
Yep, no more fooling around - time to make some games (or at least try and fail )!

[Impaler_26]

I played around a bit more with RT's example and while it's a big help it unfortunately didn't really fix the display-glitch in the last line.
I didn't notice the glitch during scrolling but sometimes when the sprite hits the wall and the scrolling stops it shows up like in the screenshot below.

I slowed down my test-files with another drawscreen so you can see the glitch better.
Again this only happens when i use player1colors, it doesn't happen in the file with a single-color sprite.

Meanwhile i saw in other games like Primate Plunge that you can use player1colors and pfscroll together without any problems.

So now i wonder if this is a bug in bB or if something is wrong with my environment? I'm using the latest fixes posted by SeaGtGruff here.

I also think i'm calling drawscreen at the wrong time....

Has anyone any idea what's going on here? I'm confused....

Attached Thumbnails

• 

Attached Files

•  slow_colors.bas   3.12K   33 downloads
•  slow_colors.bas.bin   2K   31 downloads
•  slow.bas   3.01K   39 downloads
•  slow.bas.bin   2K   36 downloads

Edited by Impaler_26, Thu Jul 31, 2008 2:30 PM.

[Random Terrain]

If you add an extra drawscreen, that will totally screw it up.

To slow down the whole thing for testing, it's better to use something like this:

slowdown
 drawscreen
 m=m+1: if m<10 then goto slowdown
 m=0

Here it is with the extra drawscreen removed and the code above added, and the line that removes the glitch in the main part of the game also added under hitwall:

 chim_slow_colors_2008y_07m_31d_1723t.bas.bin   2K   49 downloads

 chim_slow_colors_2008y_07m_31d_1723t.bas   3.24K   43 downloads

[Impaler_26]

Random Terrain, on Thu Jul 31, 2008 11:31 PM, said:

If you add an extra drawscreen, that will totally screw it up.

To slow down the whole thing for testing, it's better to use something like this:

slowdown
 drawscreen
 m=m+1: if m<10 then goto slowdown
 m=0

Here it is with the extra drawscreen removed and the code above added, and the line that removes the glitch in the main part of the game also added under hitwall:

chim_slo...723t.bas.bin

chim_slo...1d_1723t.bas

Oh boy, am i stupid!
But i think i got it now... So this glitch always happens if you don't clear the hidden line before drawscreen...

Another thing i noticed is that your example uses too many cycles but i guess i can find a solution for this.

So after all i learned something today, thanx again!

[Random Terrain]

Impaler_26, on Thu Jul 31, 2008 5:23 PM, said:

Another thing i noticed is that your example uses too many cycles but i guess i can find a solution for this.

Are you just talking the quick and dirty code that slows down the whole game for testing or the other stuff when that slow down code is removed?

[Impaler_26]

Random Terrain, on Fri Aug 1, 2008 3:53 AM, said:

Impaler_26, on Thu Jul 31, 2008 5:23 PM, said:

Another thing i noticed is that your example uses too many cycles but i guess i can find a solution for this.

Are you just talking the quick and dirty code that slows down the whole game for testing or the other stuff when that slow down code is removed?

It's not the slow down code, it's the other stuff you added in your first example. Just thought i'll let you know so you can check if it's the same with your game.
Here's a version of your example from post#4 with debug cyclescore.... Seems like something's not right here..?

Attached Files

•  chim_2008y_cyclescore.bas.bin   2K   33 downloads

[Random Terrain]

Impaler_26, on Thu Jul 31, 2008 11:12 PM, said:

It's not the slow down code, it's the other stuff you added in your first example. Just thought i'll let you know so you can check if it's the same with your game.
Here's a version of your example from post#4 with debug cyclescore.... Seems like something's not right here..?

Thanks. When I did your version, I switched to pfhline instead of using playfield variables. I did that so it would use less code and would be less confusing. I'll switch it over to playfield variables tonight and see if that makes a big enough difference in the number of cycles.

[Impaler_26]

Random Terrain, on Fri Aug 1, 2008 5:43 AM, said:

.....
I did that so it would use less code......

Don't worry about that, i just set the romsize to 2k to keep the sample-files small.

[Random Terrain]

I was trying to find ways to crunch this down, but since it has already taken too long, I'll just post the bloated version:

 chim_2008y_08m_02d_0456t.bin   4K   42 downloads
 chim_2008y_08m_02d_0456t.bas   3.91K   35 downloads

This is similar to what I am using in another program that I'm working on where I make a solid line, make the hole on the left side, then slide the hole over into position. I think this wastes fewer cycles.

[Random Terrain]

OK, I finally figured out that I could change a number and that would allow the program to skip more code until it's needed, so this should waste even fewer cycles:

 chim_2008y_08m_02d_1852t.bin   4K   47 downloads
 chim_2008y_08m_02d_1852t.bas   3.91K   43 downloads

[Impaler_26]

Random Terrain, on Sun Aug 3, 2008 1:17 AM, said:

OK, I finally figured out that I could change a number and that would allow the program to skip more code until it's needed, so this should waste even fewer cycles:

chim_200...2d_1852t.bin
chim_200...2d_1852t.bas

That's much better, thanks!
I'll spend the next few weeks with "learning by doing" and see if i can come up with something...

[yuppicide]

Nice game so far. I had the idea that it should be Alice in Wonderland falling.. like this:

http://www.alice-in-...bbit-hole-1.jpg

Maybe some sprites of chairs and lamps and whatever could fly around also that you have to avoid.

[Impaler_26]

yuppicide, on Tue Aug 5, 2008 5:19 AM, said:

Nice game so far. I had the idea that it should be Alice in Wonderland falling.. like this:

http://www.alice-in-...bbit-hole-1.jpg

Maybe some sprites of chairs and lamps and whatever could fly around also that you have to avoid.

Actually this is supposed to become a port of a neat little C64 basic-game called Down The Chimney.
I'm planning to add a few more things to it like a falling brick (ball sprite) and maybe a cloud of soot (player0) you have to avoid. Also it should start with slow scrolling and become faster each level and the gaps should become narrower each level.
But i like your idea about Alice in Wonderland, this would also be a nice theme for the game...
Hmm... maybe i'll have to make 2 games then...

But remember that i'm still a bloody beginner with bB so don't expect anything playable before X-Mas.... 2009.