Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store  

gs80065xe

Members
 View Profile  See their activity

  • Content Count

    142

  • Joined

  • Last visited

Posts posted by gs80065xe

  3. Posted · Edited by gs80065xe

    1 hour ago, dmsc said:

    Now, the collision won't work (same as the Atari BASIC version) because you don't have any portion with "color 3" on the screen (the blue text window does not count as PF2). And you don't see the HIT values because you are printing it *before* they are displayed, you must put the "? PEEK(53252)" after the PAUSE.

     

    Thanks. It's mostly working now. Collision detection is a little weird. Watching the value displayed once P0 collides with the playfield's text, changes to 1 instead of 4. So changed the repeat to check 53252 = 1. But it stops when y=21 because it changes to 1 there. So changed the repeat to 53252=1 and y>21. And it works fine. Don't understand why it is set to 1 after the first loop. But is 0 for all the rest.

     

    I know FastBasic offers PM support. But, I'm  trying to learn two languages at the same time. Assembly from an old assembly book which has examples in Atari Basic. And FastBasic by converting Atari Basic programs to FastBasic. I chose to not use the PM features in FastBasic because they won't be available in Assembly.

  4. Posted

    SKR, I was reading the hex values in memory using Altira's debugger.

     

    TGB1718, thanks for the help. I added the PLA back to the beginning. Your Data statements are the same as what's in the book. But it still hangs. I've attached my FastBasic program. I ported it from Atari basic. Tried the program in Atari Basic as it is in the book, and it works. Not sure what I've done wrong.

     

    collision.atr

  5. Posted

    I'm trying an example program testing PM Collisions. The program has a machine language routine it calls to speed up moving the player vertically. But it isn't working for me. And I still don't have a good grasp of assembly to under stand why. One thing I noticed is the book had two PLA statements at the start of the routine. That caused the program to hang. Removing one of them stops it from hanging. But the player doesn't appear to move. In fact I don't see the player at all. The line it is called on is

     

    st=usr(adr(dli),pb+512+y)

    DLI HEX: 68,68,85,cc,68,85,85,cb,a0,14,b1,cb,c8,91,cb,88,88,c0,ff,d0,f5,60

  14. Posted

    Some more information. This is running on latest Altirra using xl/Xe os and Basic roms. And Rambo 256k to simulate my real hardware. 
     

    I rewrote the program with Atari basic. Same results. Except reset resulted in losing the program.

     

    I noticed the exercise mentions it is more for the 400/800 and basic rev a which lacked an antic mode 14 graphics object. Changed Altirra to mimic an 800 with the Atari rev cart. Loaded the basic program and get a black screen without flickering. But Altirra crashed when I reset to exit the program.

  16. Posted

    Still early in the book. But the author is trying to do some things starting in Basic. He assumes the readers will be familiar with it. And I assume later he will show it in Assembly. But I haven't gotten that far because I'm trying to get my display list working for the last day or two. I know there are Display list methods in FastBasic. But the author wants the reader to manually create the Display List because you'll need to do the same thing in Assembly.

  17. Posted

    I'm studying Assembly language and am currently on Display Lists. The author has an exercise to create an Antic mode 14 display list from scratch. Using what I've learned I created a program in FastBasic. The program is on the attached atr file. But it appears when the program is run, the screen goes blank and there are pixelated artifacts flashing on the screen. Almost like the display list and or screen ram are in a location being used by another program. The flashing continues after I stop the program execution. But now there are characters flashing. I have to do a warm reset to get the display back to normal. I tried to keep it simple. So I'm currently being wasteful with RAM. But the exercise is to focus on creating the display list.

     

    Any ideas? Thanks.

    dlist.atr

  19. Posted

    I’m converting an Atari Basic display list dump program to FastBasic. But the display list starts at the edge of the 16bit integer maximum limit. So many of the addresses are overflowing When using variables. I’ve tried using float variables. But peek and dpeek doesn’t accept them. I get a parser error. Is there a way to only use positive integer variables with values 0 to 65535?

  20. Posted

    21 hours ago, tschak909 said:

    Yup, the wiki shows what is possible. 

     

    The CIO handler itself is still under heavy work (and I am actually in the process of completely rewriting the SIO part of N: in the network-rewrite branch of fujinet-platformio), but you can test it by loading n-handler.atr from atari-apps.irata.online/Networking/n-handler/n-handler.atr over TNFS.

     

    You can also use the network adapter directly over SIO.

     

    -Thom

     

     

     What is the aux2 option #3 in the open command? The wiki only lists 0 and 1. Your Dumbterm program uses it.

AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2021 AtariAge

×
×
  • Create New...