Jump to content

potatohead

Members
  • Content Count

    4,808
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by potatohead

  1. Well, ok a game can be made with this. I just put up a coupla walls, used one player for the ball, the other for the paddle, made some edits and got moving objects. So far, no hardware collision is used. Just math controlling the motion of the ball. Boring as hell actually, but hey this does prove the learning curve is quite a bit better using this tool. --Nice work, I've got something in a day running on a 2600 Here is the basic code: 1 rem smartbranching on 10 x = 50 : y = 90 : w = 40 : v = 40 11 d = 1 : e = 1 : f = 0 : g = 0 20 COLUPF = 30 30 COLUP0 = 120 : player0x = x : player0y = y 40 scorecolor = 10 45 player0: %01000010 %11111111 %11111111 %00000000 end 46 player1: %00000000 %00011000 %00111100 %01111110 %00111100 %00011000 %00000000 end 47 a = a + 1 : if a < 3 then 90 49 a = 0 51 w = w + d : v = v + e 64 player1x = w : player1y = v 65 pfvline 0 0 11 on 66 pfhline 0 0 31 on 67 pfvline 31 0 11 on 68 pfhline 0 11 31 on 90 drawscreen 91 f = x + 250 : g = x + 5 95 if v > 88 then 99 96 goto 173 99 e = 255 100 if w < f then e = 1 102 if w > g then e = 1 173 if v < 15 then e = 1 175 if w > 148 then d = 255 177 if w < 35 then d = 1 180 if joy0left then x = x - 1 190 if joy0right then x = x + 1 200 goto 30 Screenie and binary attached. boring_game.zip
  2. "I don't see the market flooded with 100's of homebrews from Newbies. It still has some learning curve to it. I see more homebrews being made, but not 100's." Give it some time.... I spent a little time this morning playing with the basic, then looking at the assembly. (Man, it's been a long time.) Just being able to express basic changes in a simple, high level, way really helps clarify the whole process. --at least it does for me. Anyway, it all works good on Linux. I futzed around with different player shapes, movements and other things. Doing those things, from a raw assembly code file would have taken most of the day. --Nice, IMHO. I want the ball!
  3. I lied Success! The output is still goofy from dasm: DASM V2.20.09, Macro Assembler ©1988-2003 Warning: Unable to open 'vcs.h' Warning: Unable to open 'macro.h' Warning: Unable to open '2600basic.h' Warning: Unable to open 'vcs.h' Warning: Unable to open 'macro.h' Warning: Unable to open '2600basic.h' Warning: Unable to open 'vcs.h' Warning: Unable to open 'macro.h' Warning: Unable to open '2600basic.h' Complete. But it does indeed produce a working binary file. Very cool stuff. I've been watching this stuff with great interest. It's nice to finally have a simple dev path on my Linux box for some futzing around. This project should speed some of the learning curve. After years of banging around on my 400, as a kid, seeing this 6502 stuff go is just great. Mandrake 10, BTW, using Stella for emulation.
  4. I'll give it a shot tomorrow. --Thanks.
  5. Hello everyone, Have been lurking for a very long time. Had a bit of free time today, thought I might give this project a quick try. I compiled under Linux too. No worries there. This worked for me, but for the last bit: ./2600bas<sample.bas>sample.asm cat 2600basic.asm sample.asm 2600basicfooter.asm > test.asm ./dasm test.asm -f3 -otest.bin I just worked through this and ran into a snag. dasm says: DASM V2.20.09, Macro Assembler ©1988-2003 Warning: Unable to open 'vcs.h' Warning: Unable to open 'macro.h' Warning: Unable to open '2600basic.h' test.asm (766): error: Syntax Error ''. test.asm (766): error: Syntax Error ''. Unrecoverable error(s) in pass, aborting assembly! Complete. Specified the include directories on the command line, edited the test.asm file, what gives? I'm assuming there is some prep for DASM that I don't know about? I just grabbed the latest package, copied the Linux binary into the working directory and ??? EDIT: Everything referenced in the test.asm file is in the same working directory.
×
×
  • Create New...