Commodore 64 basic. They accidentally sent me the BASIC book instead of the thin quick start guide. When I was 11, I just wanted to know how to load games, now I'm a programmer working on enterprise apps. Thank you the muse of fate!!!!!
I got a c64 for my 8th bday and the manual had a ton of BASIC type-ins and guides in it, fairly standard i think? But yeah, same, if it wasn't for that birthday present I wouldn't have the career I've got now. Having shitty grades all through school/uni might have mattered!
Using data statements to define a sprite was doing it the hard way. Most of us started out like that but in basic it's a waste of memory as you've got to store the sprite created from the data as well as have the basic program larger because it has the data statements as well. For a simple program and an example like this it makes perfect sense, though. I started on a Vic 20 with 3.5k available in basic so I created a basic program to design characters using a joystick or keyboard with the 8 * 8 block for normal screen mode characters. It had the option to then dump out the entire redefined char set to a binary file onto the datasette. Any programs I wrote could then just have a small loader in it to load in this file after the main program had loaded from the tape and it would be in the correct memory location for graphics data. I could then just switch to the correct graphics screen and there'd be no need for reading in the data to slow down the program start up - tape loading time permitting, of course. When I upgraded to a C64 I updated the same program to work for that as it was mainly just a case of changing the screen locations as the basic was virtually identical. I later did it for sprites as well. I can remember how many hours I spent, as well as how much fun I had, doing all this in my youth. Nowdays most of the grunt work is done for you so you can get on with the easier stuff but it's not quite the same. A lot of people who used C64's during the day had a decent grasp of how the machine worked so would understand when something pretty clever was being shown to them. Now stuff is just expected to work and nobody gives a stuff how much memory it's using or badly optimised it all is. Glad I was there in the eighties doing all this stuff the hard way - I loved it.
I really envy you. I started to learn Python and I'm 25 years old now. I always regret that I started too late. I grow up playing with my uncle's Amiga 500 and I adored the artwork on them. I wanted recreate my favorite game too. But I always wished to live in 80s and create some stuff in the commodore without being online. It was the bestest feeling when I'm discovering and learning new things by my own on windows 95 and Amiga games. Now I'm working as a 3D modeller and I'm really interested in C64. But I have no idea where to start. I'm using some emulators since I don't have Commodore64 but my Amiga500 is still workin'.
I really envy you. I started to learn Python and I'm 25 years old now. I always regret that I started too late. I grow up playing with my uncle's Amiga 500 and I adored the artwork on them. I wanted recreate my favorite game too. But I always wished to live in 80s and create some stuff in the commodore without being online. It was the bestest feeling when I'm discovering and learning new things by my own on windows 95 and Amiga games. Now I'm working as a 3D modeller and I'm really interested in C64. But I have no idea where to start. I'm using some emulators since I don't have Commodore64 but my Amiga500 is still workin'.
@@alestesart6429 Start with putting a real C64 on your desk, Then get a fastload cart and SD2IEC , The rest is finding the time but it's very rewarding just to see it on your desk every day.
Nice, i did the same kind of program, on my C64. I could design the sprites with my joystick, in 2 or 4 colors, and then save them. But beside a begining of a "shot them up" game that i never finished, i didn't use it, sad.
I used to LOVE programming the C64. Especially in Assembly. 6510 assembly was so easy. There were a few hidden commands that were used for assembly on the C64 that you could use in BASIC if you knew the address to call the SYS command. For example, to plot the cursor on screen somewhere POKE211,X:POKE214,Y:SYS58732 There's some REALLY good ones (like playing sound effects with a couple pokes and a PRINT... )
@@AllGamingStarred Used to. Been literally decades since I last programmed one. Probably close to 30 years. Maybe some day I will boot up the emulator and give it a shot again. These days my love of programming has been fading. Don't know why, enthusiasm just isn't there. Used to be I would be up all night until I heard the birds chirping at sunrise! LOL
@@NeilRoy "Don't know why, enthusiasm just isn't there." - Yup, (somehow) I know that feeling... Something - not quite sure what - got lost along the way; and I do fear I'll never get it back again...
Aaah, those infamous data statements. I made a horse racing game in BASIC on my C64 a few years ago with this - I might still have it on a tape. This amazing machine sparked my interest in programming, especially on older systems.
i remember at 80s, when i was 9 , 10 years old i used basic language, lot of times... i learning at the manual books and the compute! magazine and ahoy!, so many memories... i remember when i made my first game, then now im a web & multimedia designer and systems engineer. lol
Very similar to the Atari 800. I wrote an animated volleyball game in basic using Atari's unlimited length string for the sprite ram area and then used the very fast string moving routines to move the sprites vertically. (On the Atari, a sprite is moved vertically by moving the sprite image definition up and down in memory).
@@PATZAWA I agree sprites are easier to use on the C64, ' a piece of cake compared to the Atari ' is stretching the truth a bit. And yes, the same person who perfected the graphics on the Atari 8-bit also designed the graphics for the Amiga. It's a pity Jack Tramiel chose not to continue perfecting the Amiga and instead came out with the Atari ST line. In fairness to the ST, I had one and it got me through 3 1/2 years of college. The fact that you could turn an ST into a Mac was interesting too; it at least proved it wasn't a toy computer.
I used to stack sprite data statements from printouts so I could get the animations right, lol. Seriously though the C64 sprite's were revolutionary. If you know Atari they cannot move freely on a vertical plane (without some character shifting). I'm hoping to get in contact with Commodore 64 lovers as I will be starting a programming tutorial from Basic to Assembly language soon.
The Atari 8-bit machine had sprites 3 years before Commodore but Commodore were revolutionary ??? Not TOO biased, are you? Atari sprites can't move freely on a vertical plane. Yeah, moving up and down memory is a REAL challenge ??? I used slow Atari Basic to move sprites vertically without using machine language and achieved decent vertical speed by tricking the basic into thinking the player/missile graphics area was really a string variable and then use Atari Basic's very fast move memory commands to move the sprites.
I remember my first games with Hi-res sprites using Basic, thanks God there's assembler ;]. I'm still doing some stuff on C64 thanks to assembler, it's great fun! Nice vid, thx for add!
C=64 BASIC was the first computer I used, and I was programming in BASIC on it within a few weeks. I saw someone make the screen flash random colours and had text scrolling up. It was the coolest tech thing I had ever seen, lol. They used POKE commands, so I just memorised what they were and learned by tweaking their code until I understood what did what.
SO MANY DATA STATEMENTS!!! Does anyone remember sitting there with a piece of graph paper and drawing out the sprites and then adding the values up for the data statements?
I readraw a dragon tatoo from a friends arm on a transparence foil and add a grid over it, for to use it as a data statement on a TI 99 4A home computer using modified ASCII characters.
Bravo. I have made at the 90 s something like this. I hope i will found and show the experiment. Nice to see such beautiful work. Keep the good dreams on air. Bye
Trying this on the C64 Mini. BASIC is alright to use on it, apart from the odd keymapping issue. Symbols can be a real pain to get going due to the hotkey combinations you have to use, which can conflict with other hotkey combinations.
@gjc82071 For a total beginner the user guide is the best way to start learn and you can learn lot only with this :) For example the chapter 6 is all that you need to understand this sprite program. Thanks to sprite it is possible to program simple arcade game with BASIC on C64. Unfortunately the BASIC of C64 is very limited (and slow), you must use PEEK/POKE instructions to manipulate graphics/sprite/sound. But in other side, this limitation makes the "transition" Basic/Assembling easier.
@jci10 - You know what I was so sure I was correct that I dug out the programming guide for CBM Basic V2, only to find that you are indeed correct! I must be confusing CBM Basic V2 for something else that has optimisations for integer arithmatic. Sorry about that!
yes, (i'm writing one at the moment and I will upload a video on it soon) but you need to be an extremely patient person and you need to be prepared to spend months mastering extremely difficult notation and mathematics.
Thanks for this. I was trying to get the sprite example from the user's guide to work, but I got a cube instead of balloon. It seems they made an error either on line 12 or 20 but your combination of "POKE 2042,13" and "POKE 832" is correct.
I did not notice any problems on user manual the main problem is the explanation about the sprite pointer (At least in french manual). Poke 2042,13 means that the data of the sprite no1 (this is the second sprite) comes from the bank no13 and since each bank have 64 bytes length, the address of sprite data is 64*13 = 832 : and that is the reason of poking data sprite from address 832 . The most common problem is typing errors on data statement ;)
@senorverde09 I doesn't because i discovered C64 later, long time after his gold period. But If i had to program the C64 during this period i created (with basic) and used an simple sprite editor and load the sprite with basic from a file. The same way with assembler: instead type data directly it's easier to create an assembler compiler and loading the opcode from a bin file. But preparing sprite and opcode data with a simple pencil/paper and after type all through basic is Fun :)
2 problems with VICE 3.1: 1. I keep having to retype due to other keys I didn't even press being shown onscreen (I press e and get b right next to it) and 2. the above program is not working for me. I keep getting an out of data error in 45
When you press Shift key and Clr/Home key simultaneously, the screen is cleared. Now, when you start to type PRINT " (don't forget the quotation caracter ") and if you press the Shift-Clr/Home combination, instead to clear screen, the heart caracter shoud appear. Type " after that and you should obtain PRINT "♥" which is actually the command to clear the whole screen.
@PATZAWThx, I was there already/have'em all. I guess i should just start there? As for the other stuff, coding, assembly, etc, it's a matter of learning to walk b4 run, eh? Thx again!
This is really cool. God, I really wish I knew how to program, so badly. I always wanted to learn, but never did. I still do! I wish i could make C64 games. I don't know what code/ing, assembler or anything means. All I know is (1 print "hello", 2 goto1, run) For a total beginner, what is the best way to start (on C64)?
+Franz Maurer hold shift down and type clr/home key (usually is the equivalent of HOME key in a pc keyboard), you have to type it between apostrophes, or it will clear out the entire screen :)
It is similar. Certain registers must be set to certain values to set up sprite graphic mode. It's a bit harder in Atari Basic because you have to set aside sprite memory by hand. There was another basic that had sprite graphics commands to do most of the work for the programmer.
Very strange. In this case try simply VX = 1 and VY = 1 these must work. Also you can try in a new basic program just typing ? INT(RND(1)*4-2) and check if it works and if you do not enter something wrong... Are you using a real C-64 ? or an emulator ? With a real C-64, sometimes a failed components can give strange errors.
Thanks for the programming example. It might be just my imagination, but I seem to remember seeing that sprite in a famous Activision game. 😁 In any regard, I tweaked the code a bit just for grins... 110 poke53280,11:poke53281,0:poke646,5:printchr$(147) 120 forx=0to62:readn:poke832+x,n:next:poke918,24:poke921,16 130 forx=0to59:poke963+x,peek(832+x):next:poke973,0:poke979,0:poke982,0 140 poke53288,10:poke53289,15:forx=0to2:poke2040+x,13+x:next 150 poke53271,7:poke53277,7:poke53269,7:x=160:y=130 160 y=y+rnd(1)*5-2and255:x=x+rnd(1)*4-2:ifx344thenx=0 180 xl=xand255:xh=int(x/256)and255:ifxh0thenxh=7 190 poke53248,xl:poke53249,y:poke53250,xl:poke53251,y:poke53252,xl:poke53253,y 200 poke53264,xh 210 getk$:ifk$=""then160 220 poke53269,0:end 300 data 0,1,0,0,14,0,0,28,0,0,62,0,0,87,0,0,127,0,0,247,128,0,199,128 310 data 0,111,0,1,255,128,15,255,192,31,255,224,112,252,96,193,252,48 320 data 3,255,0,1,255,0,0,255,224,0,63,240,0,0,254,0,0,0,0,0,0
my goodness! I vaguely remember coding sprites this way back in 1982. I decided a C64 was too lame and waited for a 128. However, discovered that the lameness is BASIC 2.0. With added ML modules, all these pain is gone. I have created DotBASIC, with accessory programs for sprite and screen design. Very easy. Write me for more info.
![How to Make a C64 Game in BASIC Ep.1 [HOW2] | Nostalgia Nerd](http://i.ytimg.com/vi/MTG1q_QGAS8/mqdefault.jpg)
Commodore 64 basic. They accidentally sent me the BASIC book instead of the thin quick start guide. When I was 11, I just wanted to know how to load games, now I'm a programmer working on enterprise apps. Thank you the muse of fate!!!!!
I got a c64 for my 8th bday and the manual had a ton of BASIC type-ins and guides in it, fairly standard i think? But yeah, same, if it wasn't for that birthday present I wouldn't have the career I've got now. Having shitty grades all through school/uni might have mattered!
INT(RND(1)*4-2) gives you a random value between -2 and +1 - so the ghost will always move up and left over time.
Using data statements to define a sprite was doing it the hard way. Most of us started out like that but in basic it's a waste of memory as you've got to store the sprite created from the data as well as have the basic program larger because it has the data statements as well.
For a simple program and an example like this it makes perfect sense, though.
I started on a Vic 20 with 3.5k available in basic so I created a basic program to design characters using a joystick or keyboard with the 8 * 8 block for normal screen mode characters. It had the option to then dump out the entire redefined char set to a binary file onto the datasette. Any programs I wrote could then just have a small loader in it to load in this file after the main program had loaded from the tape and it would be in the correct memory location for graphics data. I could then just switch to the correct graphics screen and there'd be no need for reading in the data to slow down the program start up - tape loading time permitting, of course.
When I upgraded to a C64 I updated the same program to work for that as it was mainly just a case of changing the screen locations as the basic was virtually identical. I later did it for sprites as well.
I can remember how many hours I spent, as well as how much fun I had, doing all this in my youth. Nowdays most of the grunt work is done for you so you can get on with the easier stuff but it's not quite the same. A lot of people who used C64's during the day had a decent grasp of how the machine worked so would understand when something pretty clever was being shown to them. Now stuff is just expected to work and nobody gives a stuff how much memory it's using or badly optimised it all is.
Glad I was there in the eighties doing all this stuff the hard way - I loved it.
I really envy you. I started to learn Python and I'm 25 years old now. I always regret that I started too late. I grow up playing with my uncle's Amiga 500 and I adored the artwork on them. I wanted recreate my favorite game too. But I always wished to live in 80s and create some stuff in the commodore without being online. It was the bestest feeling when I'm discovering and learning new things by my own on windows 95 and Amiga games. Now I'm working as a 3D modeller and I'm really interested in C64. But I have no idea where to start. I'm using some emulators since I don't have Commodore64 but my Amiga500 is still workin'.
I really envy you. I started to learn Python and I'm 25 years old now. I always regret that I started too late. I grow up playing with my uncle's Amiga 500 and I adored the artwork on them. I wanted recreate my favorite game too. But I always wished to live in 80s and create some stuff in the commodore without being online. It was the bestest feeling when I'm discovering and learning new things by my own on windows 95 and Amiga games. Now I'm working as a 3D modeller and I'm really interested in C64. But I have no idea where to start. I'm using some emulators since I don't have Commodore64 but my Amiga500 is still workin'.
@@alestesart6429 Start with putting a real C64 on your desk, Then get a fastload cart and SD2IEC , The rest is finding the time but it's very rewarding just to see it on your desk every day.
Weird flex, but ok
Nice, i did the same kind of program, on my C64. I could design the sprites with my joystick, in 2 or 4 colors, and then save them. But beside a begining of a "shot them up" game that i never finished, i didn't use it, sad.
I used to LOVE programming the C64. Especially in Assembly. 6510 assembly was so easy. There were a few hidden commands that were used for assembly on the C64 that you could use in BASIC if you knew the address to call the SYS command. For example, to plot the cursor on screen somewhere
POKE211,X:POKE214,Y:SYS58732
There's some REALLY good ones (like playing sound effects with a couple pokes and a PRINT... )
used to?
@@AllGamingStarred Used to. Been literally decades since I last programmed one. Probably close to 30 years. Maybe some day I will boot up the emulator and give it a shot again. These days my love of programming has been fading. Don't know why, enthusiasm just isn't there. Used to be I would be up all night until I heard the birds chirping at sunrise! LOL
sys64738 :)
@@Yossarian0011 Yeah right. Might want to save your work before you try that one out. :)
@@NeilRoy "Don't know why, enthusiasm just isn't there." - Yup, (somehow) I know that feeling... Something - not quite sure what - got lost along the way; and I do fear I'll never get it back again...
I don't know what was more fun: programming the game or playing it on C64 ^^
Aaah, those infamous data statements. I made a horse racing game in BASIC on my C64 a few years ago with this - I might still have it on a tape.
This amazing machine sparked my interest in programming, especially on older systems.
what machines do not require data statements?
"I might still have it on a tape."
Oh the memories lol. You know, I still need to find a copy of Blue Thunder somewhere...
i remember at 80s, when i was 9 , 10 years old i used basic language, lot of times... i learning at the manual books and the compute! magazine and ahoy!, so many memories... i remember when i made my first game, then now im a web & multimedia designer and systems engineer. lol
*****
it was sys 64738, it was used for reset the memory and dump it... regards
Imagine if typing rub instead of run undid all that code and he had to type it again
Fortunately you'd just get a syntax error on the Commodore 64.
What a flash back! Great.
POKE 53280,0:POKE 53281,0 ;-)
ABSOLUTELY... THE BACKGROUND SCREEN IN BLACK! LOL...
Very similar to the Atari 800. I wrote an animated volleyball game in basic using Atari's unlimited length string for the sprite ram area and then used the very fast string moving routines to move the sprites vertically. (On the Atari, a sprite is moved vertically by moving the sprite image definition up and down in memory).
Oh yeah ! that's why sprite in c-64 is piece of cake comparing to Atari. By the way, we see on Atari8bits a sketch of what will be Sprites in Amiga
@@PATZAWA I agree sprites are easier to use on the C64, ' a piece of cake compared to the Atari ' is stretching the truth a bit.
And yes, the same person who perfected the graphics on the Atari 8-bit also designed the graphics for the Amiga. It's a pity Jack Tramiel chose not to continue perfecting the Amiga and instead came out with the Atari ST line. In fairness to the ST, I had one and it got me through 3 1/2 years of college. The fact that you could turn an ST into a Mac was interesting too; it at least proved it wasn't a toy computer.
Awesome, brings back sooo many good memories! I'm planning to bring back home my C64 to show and teach some cool stuff to my kids :)
I spent my childhood doing this 💙
If I had a nickel for every time I typed RUB instead of RUN, I would've been a millionaire by the time I was 15.
lol
I share your pain!
Wow that really takes me back. I loved Sprite programming back in the day.
did you make any games?
I used to stack sprite data statements from printouts so I could get the animations right, lol. Seriously though the C64 sprite's were revolutionary. If you know Atari they cannot move freely on a vertical plane (without some character shifting). I'm hoping to get in contact with Commodore 64 lovers as I will be starting a programming tutorial from Basic to Assembly language soon.
The Atari 8-bit machine had sprites 3 years before Commodore but Commodore were revolutionary ??? Not TOO biased, are you?
Atari sprites can't move freely on a vertical plane. Yeah, moving up and down memory is a REAL challenge ??? I used slow Atari Basic to move sprites vertically without using machine language and achieved decent vertical speed by tricking the basic into thinking the player/missile graphics area was really a string variable and then use Atari Basic's very fast move memory commands to move the sprites.
I remember my first games with Hi-res sprites using Basic, thanks God there's assembler ;]. I'm still doing some stuff on C64 thanks to assembler, it's great fun! Nice vid, thx for add!
C=64 BASIC was the first computer I used, and I was programming in BASIC on it within a few weeks. I saw someone make the screen flash random colours and had text scrolling up. It was the coolest tech thing I had ever seen, lol. They used POKE commands, so I just memorised what they were and learned by tweaking their code until I understood what did what.
Excellent, really excellent :-) Many thanks... You got me typing like a kid again!
SO MANY DATA STATEMENTS!!! Does anyone remember sitting there with a piece of graph paper and drawing out the sprites and then adding the values up for the data statements?
Yes!
I readraw a dragon tatoo from a friends arm on a transparence foil and add a grid over it, for to use it as a data statement on a TI 99 4A home computer using modified ASCII characters.
Bravo. I have made at the 90 s something like this. I hope i will found and show the experiment. Nice to see such beautiful work. Keep the good dreams on air. Bye
All it takes is a passion and effort.
change V, X, Y, VX and VY to V%, X%, Y%, VX% and VY% to switch them to integer variables for a speed boost ;-)
@gjc82071
I think that the "Commodore 64 Users Guide" is a good way to start.
I was waiting for you to fix that 90 goto 90 line
padistedor same here lol
what's wrong with that? He wanted the program to just sit there without ending. Perhaps when the program stops running the sprite goes away.
Definitely and don't forget Mapping the Commodore 64 when you are ready to master the machine.
I learned assembly and raster interrupts on the 64.
Back to the very beginning :)
The very beginning was a 40 column display with characters built into rom a monochrome screen and limited basic compared to others. I love my pet
Trying this on the C64 Mini. BASIC is alright to use on it, apart from the odd keymapping issue. Symbols can be a real pain to get going due to the hotkey combinations you have to use, which can conflict with other hotkey combinations.
@gjc82071
For a total beginner the user guide is the best way to start learn and you can learn lot only with this :) For example the chapter 6 is all that you need to understand this sprite program. Thanks to sprite it is possible to program simple arcade game with BASIC on C64.
Unfortunately the BASIC of C64 is very limited (and slow), you must use PEEK/POKE instructions to manipulate graphics/sprite/sound.
But in other side, this limitation makes the "transition" Basic/Assembling easier.
@jci10 - You know what I was so sure I was correct that I dug out the programming guide for CBM Basic V2, only to find that you are indeed correct! I must be confusing CBM Basic V2 for something else that has optimisations for integer arithmatic. Sorry about that!
i just got a C64 and i showed my dad this trick
Que de souvenir, même avant avec ke zx81
yes, (i'm writing one at the moment and I will upload a video on it soon) but you need to be an extremely patient person and you need to be prepared to spend months mastering extremely difficult notation and mathematics.
finally managed it. cool bro
Thanks for this. I was trying to get the sprite example from the user's guide to work, but I got a cube instead of balloon. It seems they made an error either on line 12 or 20 but your combination of "POKE 2042,13" and "POKE 832" is correct.
I did not notice any problems on user manual the main problem is the explanation about the sprite pointer (At least in french manual). Poke 2042,13 means that the data of the sprite no1 (this is the second sprite) comes from the bank no13 and since each bank have 64 bytes length, the address of sprite data is 64*13 = 832 : and that is the reason of poking data sprite from address 832 . The most common problem is typing errors on data statement ;)
@@PATZAWA My 1983 version of the manual contains an error but later ones (from 1984) have it corrected, I found out.
@@megakek4457 ah ! ok ! thanks for precisions :-)
I LOVE C64 👍🥂🎩
I think this algorithm is directly borrowed from the book "Sprite Graphics for the Commodore 64" written by Sally Greenwood in 1983 🥳
@senorverde09
I doesn't because i discovered C64 later, long time after his gold period. But If i had to program the C64 during this period i created (with basic) and used an simple sprite editor and load the sprite with basic from a file. The same way with assembler: instead type data directly it's easier to create an assembler compiler and loading the opcode from a bin file.
But preparing sprite and opcode data with a simple pencil/paper and after type all through basic is Fun :)
Surely poking a value to a constant is quicker than poking to a variable plus a contstant?
2 problems with VICE 3.1: 1. I keep having to retype due to other keys I didn't even press being shown onscreen (I press e and get b right next to it) and 2. the above program is not working for me. I keep getting an out of data error in 45
Nice!!!
Is this a sprite or a UDG?
Hei PATZAWA, GREAT + I've done and it works, Im sooo glad, Genious :-)
wow this code is amazing. Can you link to joystick control also ?
How do you make that heart that way? My heart is different
When you press Shift key and Clr/Home key simultaneously, the screen is cleared. Now, when you start to type PRINT " (don't forget the quotation caracter ") and if you press the Shift-Clr/Home combination, instead to clear screen, the heart caracter shoud appear. Type " after that and you should obtain PRINT "♥" which is actually the command to clear the whole screen.
Thanks for asking this. I wondered about the same thing
I used to be able to see the sprite in my head just by looking at the data-statements :) call me weird.
This is really cool.
Ohhhhh, you've got some great stuff on you're channel. I will check it out for sure. =D
@PATZAWThx, I was there already/have'em all. I guess i should just start there? As for the other stuff, coding, assembly, etc, it's a matter of learning to walk b4 run, eh? Thx again!
Jajaja me hizo recordar días afiebrados!!! Jajaja
Well sure. The same can be said for almost anything. But with programming......I just don't know where to start.
in the future i make sector os for commodore 64
This is really cool. God, I really wish I knew how to program, so badly. I always wanted to learn, but never did. I still do! I wish i could make C64 games. I don't know what code/ing, assembler or anything means. All I know is (1 print "hello", 2 goto1, run) For a total beginner, what is the best way to start (on C64)?
Very Good.
does it work with petit computer
How to move a sprite with sinus/cosinus in basic
correct me if i'm wrong but is there a syntax error in here? : 10 graphic 1,1 20 color 1,1 30 box 4,2,1. i'm using the 128
super cool
Very cool video!!
It was you who was programming?
Tell me something, what is the command POKE?
Can you explain in detail please?
J0hNF_UK and PEEK allows you to see the value inserted in the memory address.
Didn't the 128 have a built in sprite editor so you could cheat?
OBS Studio for Commodore C64 :)
won't work, it says I have an error in 55
I'm glad I learned assembly language. It's much easier to program.
Is there a fast track to being able to make pixelated nipples? Hope so. Player 2.
how to make negative of a charater?
+Franz Maurer hold shift down and type clr/home key (usually is the equivalent of HOME key in a pc keyboard), you have to type it between apostrophes, or it will clear out the entire screen :)
so the bug is predominately red? I tried to make one out of diamonds and it just came out as red dots
what do all those numbers do?
no-one really knows, still an unsolved mystery in computer science.
very very cool!! can you teach me to programming a game in a commodore 64??
RUB
Haha 😂
And a genie comes out of the lamp. Fitting.
You only needed 3 zeros on line 155.
yes: i was too lazzy to count exactly (even it's easy 6x10) ;p
No audio to describe what you're doing?
with my french accent it would be not very understandable ;) cc would be more suitable
sir, it seems your c64 is posessed
is this the same way to program in 800xl ..?
very nice..
It is similar. Certain registers must be set to certain values to set up sprite graphic mode. It's a bit harder in Atari Basic because you have to set aside sprite memory by hand. There was another basic that had sprite graphics commands to do most of the work for the programmer.
50 illegal quantity?
It gives me ?syntax error in 65, but all is right.... somebody who can help me?
Are you correctly typed ?
VX = INT(RND(1)*4-2)
PATZAWA Yes, but it still gives error
Very strange. In this case try simply VX = 1 and VY = 1 these must work. Also you can try in a new basic program just typing ? INT(RND(1)*4-2) and check if it works and if you do not enter something wrong... Are you using a real C-64 ? or an emulator ? With a real C-64, sometimes a failed components can give strange errors.
PATZAWA tomorrow i'll again
I discovered that i was using the wrong bracket type, so it wasn't working, but now it works
sprites are not that difficult its more the character sets and bitmapping
Who you gonna' call?
SPRITE BUSTERS.
my hands hurt, all that typing for no payoff?
@gjc82071
2 links on description ;)
Lol. The good ole days.
знаем.... знаем... мы тоже так умеем!!!
Thanks for the programming example. It might be just my imagination, but I seem to remember seeing that sprite in a famous Activision game. 😁 In any regard, I tweaked the code a bit just for grins...
110 poke53280,11:poke53281,0:poke646,5:printchr$(147)
120 forx=0to62:readn:poke832+x,n:next:poke918,24:poke921,16
130 forx=0to59:poke963+x,peek(832+x):next:poke973,0:poke979,0:poke982,0
140 poke53288,10:poke53289,15:forx=0to2:poke2040+x,13+x:next
150 poke53271,7:poke53277,7:poke53269,7:x=160:y=130
160 y=y+rnd(1)*5-2and255:x=x+rnd(1)*4-2:ifx344thenx=0
180 xl=xand255:xh=int(x/256)and255:ifxh0thenxh=7
190 poke53248,xl:poke53249,y:poke53250,xl:poke53251,y:poke53252,xl:poke53253,y
200 poke53264,xh
210 getk$:ifk$=""then160
220 poke53269,0:end
300 data 0,1,0,0,14,0,0,28,0,0,62,0,0,87,0,0,127,0,0,247,128,0,199,128
310 data 0,111,0,1,255,128,15,255,192,31,255,224,112,252,96,193,252,48
320 data 3,255,0,1,255,0,0,255,224,0,63,240,0,0,254,0,0,0,0,0,0
no no it is not your imagination 🙂 Thank you for tweaking the code !!!
my goodness! I vaguely remember coding sprites this way back in 1982. I decided a C64 was too lame and waited for a 128. However, discovered that the lameness is BASIC 2.0. With added ML modules, all these pain is gone. I have created DotBASIC, with accessory programs for sprite and screen design. Very easy. Write me for more info.
Ghostbusters
👍
Not work
:(
GENIAL!!!!
👍🕹
poke 53280,0 :)
Phil McGroin
like Gta Vice CIty;)
Thank god for JS
😂😂😂😂😂😂
Man, please type program vith sount keyboard :)