Jump to content

Search the Community

Showing results for tags 'assembler'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Atari Systems
    • Atari General
    • Atari 2600
    • Atari 5200
    • Atari 7800
    • Atari Lynx
    • Atari Jaguar
    • Atari VCS
    • Dedicated Systems
    • Atari 8-Bit Computers
    • Atari ST/TT/Falcon Computers
  • Classic Consoles
  • Classic Computing
  • Modern Consoles
  • Gaming General
  • Marketplace
  • Community
  • Community
  • Game Programming
  • Site
  • PC Gaming
  • The Club of Clubs's Discussion
  • I Hate Sauron's Topics
  • 1088 XEL/XLD Owners and Builders's Topics
  • Atari BBS Gurus's Community Chat
  • Atari BBS Gurus's BBS Callers
  • Atari BBS Gurus's BBS SysOps
  • Atari BBS Gurus's Resources
  • Atari Lynx Programmer Club's CC65
  • Atari Lynx Programmer Club's ASM
  • Atari Lynx Programmer Club's Lynx Programming
  • Atari Lynx Programmer Club's Music/Sound
  • Atari Lynx Programmer Club's Graphics
  • The Official AtariAge Shitpost Club's Shitty meme repository
  • The Official AtariAge Shitpost Club's Read this before you enter too deep
  • Arcade Gaming's Discussion
  • Tesla's Vehicles
  • Tesla's Solar
  • Tesla's PowerWall
  • Tesla's General
  • Harmony/Melody's CDFJ
  • Harmony/Melody's DPC+
  • Harmony/Melody's BUS
  • Harmony/Melody's General
  • ZeroPage Homebrew's Discussion
  • Furry Club's Chat/RP
  • PSPMinis.com's General PSP Minis Discussion and Questions
  • PSPMinis.com's Reviews
  • Atari Lynx 30th Birthday's 30th Birthday Programming Competition Games
  • 3D Printing Club's Chat
  • Drivers' Club's Members' Vehicles
  • Drivers' Club's Drives & Events
  • Drivers' Club's Wrenching
  • Drivers' Club's Found in the Wild
  • Drivers' Club's General Discussion
  • Dirtarians's General Discussion
  • Dirtarians's Members' Rigs
  • Dirtarians's Trail Runs & Reports
  • Dirtarians's Wrenching
  • The Green Herb's Discussions
  • Robin Gravel's new blog's My blog
  • Robin Gravel's new blog's Games released
  • Atari Video Club's Harmony Games
  • Atari Video Club's The Atari Gamer
  • Atari Video Club's Video Game Summit
  • Atari Video Club's Discsuuions
  • Star Wars - The Original Trilogy's Star Wars Talk
  • PlusCart User's Bug reports
  • PlusCart User's Discussion
  • DMGD Club's Incoming!
  • DASM's General
  • AtariVox's Topics
  • Gran Turismo's Gran Turismo
  • Gran Turismo's Misc.
  • Gran Turismo's Announcements
  • The Food Club's Food
  • The Food Club's Drinks
  • The Food Club's Read me first!
  • The (Not So) Official Arcade Archives Club's Rules (READ FIRST)
  • The (Not So) Official Arcade Archives Club's Feedback
  • The (Not So) Official Arcade Archives Club's Rumor Mill
  • The (Not So) Official Arcade Archives Club's Coming Soon
  • The (Not So) Official Arcade Archives Club's General Talk
  • The (Not So) Official Arcade Archives Club's High Score Arena
  • Adelaide South Australia Atari Chat's General Chat & Welcome
  • Adelaide South Australia Atari Chat's Meets
  • Adelaide South Australia Atari Chat's Trades & Swaps
  • KC-ACE Reboot's KC-ACE Reboot Forum
  • The Official Lost Gaming Club's Lost Gaming
  • The Official Lost Gaming Club's Undumped Games
  • The Official Lost Gaming Club's Tip Of My Tounge
  • The Official Lost Gaming Club's Lost Gaming Vault
  • The Official Lost Gaming Club's Club Info
  • GIMP Users's Discussion

Blogs

There are no results to display.

There are no results to display.

Calendars

  • AtariAge Calendar
  • The Club of Clubs's Events
  • Atari BBS Gurus's Calendar

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website


Facebook


Twitter


Instagram


YouTube


eBay


GitHub


Custom Status


Location


Interests


Currently Playing


Playing Next

Found 51 results

  1. Rather than open a thread each time I had a question, I thought I might just open a thread and consolidate all my questions here. Basically I'm developing a game, called Bike Night. It's a horizontal scroller, with a motorcycle going up and down on a track. In that sense its similar to Excitebike. But unlike Excitebike the goal is not to win a race against other bikes but to do tricks. I am learning assembler - I've written games - for the Ti-99, Colecovision, Palm Pilot and iOS devices. Ti-99 was a extended basic game back in the day - Colecovision & Palm Pilot in C, and for iOS I use the titanium framework to write in javascript. The reason I'm giving you my background so you can understand I've always been a high level programmer. I don't understand how the hardware works - and never had to, but now I want to know. I've decided to split my screen into 3 parts. There will be a top level area which is primarily just there to add color to the screen. It'll horizontal scroll, and you'll see flags, colors, bright lights, etc. Then the 2nd part of the screen is the track area. and the 3rd area of the screen at the bottom will display the score and messages like "Wheelie jump" or "Big Air" - it's a bike trick game, so you get the immediate feedback when completing a trick. OK, so today's question, I am getting started on some coding, and I have made a character set for the track area. I've read some old articles about Atari fine scrolling. My understanding (please correct if wrong) is the hardware can do fine scrolling for a character or two. But the way you got it to scroll over several screens is you combined fine scrolling with coarse scrolling. After you fine scrolled say 8 pixels, then you did a coarse scroll by a character (which involved just changing the pointer to where the screen memory began) OK question take a look at this source from the book "Atari Roots" 10 ; 20 ; THE VISITOR 30 ; 35 TXTBUF=$5041 40 OPNSCR=$5003 50 PRNTLN=$5031 70 ; 80 *=$600 90 ; 0100 TEXT .BYTE $54,$41,$4B,$45,$20,$4D,$45,$20 0110 .BYTE $54,$4F,$20,$59,$4F,$55,$52,$20 0120 .BYTE $4C,$45,$41,$44,$45,$52,$21 0130 ; 0140 VIZTOR 0150 ; 0160 LDX #0 0170 LOOP LDA TEXT,X 0180 STA TXTBUF,X 0190 INX 0200 CPX #23 0210 BNE LOOP 0220 JSR OPNSCR 0230 JSR PRNTLN 0240 INFIN JMP INFIN OK, now, you have the assembler pseudo op ".BYTE" And apparently one is looping through and using the data stored there - how to use it, I get. lets say I have all this data for screens and I put it in .BYTE directives in my source. And I loop through and I place the screen data into memory. What I don't get - this may sound like a ludicrous question, but what I don't get is am I doubling the amount of memory being used??? By that I mean - how does an executable itself work. Lets say my executable is called bnight.exe - when I run that, does the entire game load into memory? If so, do I have the entire screen data loaded into memory and when I copy it to the screen area, I've essentially just doubled the amount of memory being used for this data? Would it make more sense, if trying to save bytes, to leave the screen data in a separate file on disk, and then programatically retrieve it and then load it into the appropriate area, rather than using a byte directive and having that data part of code? Am I completely confused? Thanks!
×
×
  • Create New...