Jump to content
IGNORED

Drifting into a dreamlike state...ahhhh...8K


Papa

Recommended Posts

Just out of left field with this. What would it take to add just 4K more graphics RAM to the Atari VCS? Could a cart be made that adds more (like a Super Charger) that could then be accessed by Bb? I keep drifting into what if's and how stupendous games could be with just that tiny bit more. Could a newer version of Melody board be made that adds 4K extra or is this just not possible?

 

...So, that's what would have happened if I invented the finglonger. A man can dream. A man can dream.

Edited by Papa
  • Like 1
Link to comment
Share on other sites

Just out of left field with this. What would it take to add just 4K more graphics RAM to the Atari VCS? Could a cart be made that adds more (like a Super Charger) that could then be accessed by Bb? I keep drifting into what if's and how stupendous games could be with just that tiny bit more. Could a newer version of Melody board be made that adds 4K extra or is this just not possible?

 

...So, that's what would have happened if I invented the finglonger. A man can dream. A man can dream.

 

:?

  • Like 2
Link to comment
Share on other sites

Just out of left field with this. What would it take to add just 4K more graphics RAM to the Atari VCS? Could a cart be made that adds more (like a Super Charger) that could then be accessed by Bb? I keep drifting into what if's and how stupendous games could be with just that tiny bit more. Could a newer version of Melody board be made that adds 4K extra or is this just not possible?

 

...So, that's what would have happened if I invented the finglonger. A man can dream. A man can dream.

DPC+ really shows off the graphic capability of the Atari 2600. You're still limited by the TIA chip.

 

Like the MMC5 chip for the NES. Awesome mapper chip, but still bound to the NES graphic capability.

Link to comment
Share on other sites

The secret to longevity of the VCS is that it is a difficult machine to work with. And only the most skilled and innovative programmers can make this machine shine. And that eliminates a lot of riffraff from the ranks. I know I've said this before, but the next most difficult machine to work with is the AGC. Limitations galore. Programs needing to be finalized 6 months ahead with no room for error..

 

Ohh sure the VCS has its share of doggy titles. However none of those titles are crafted with love, so they end up being me-too wannabees. And anybody today can churn out material on today's high-level languages running at thousands of MHz with millions of pre-made libraries - so that eliminates modern machines as being difficult.

  • Like 1
Link to comment
Share on other sites

 

There are already a number of games that use 32K through the miracles of bankswitching.

 

True, but the supercharger has 6K. I thought we were talking about the supercharger.

 

Papa is new to bankswitching. But Batari Basic supports several bankswitching scheme's (iirc) so there should be no problem for Papa to make a 32K game. The supercharger was brought into the conversation to make the game more authentic I guess.

  • Like 1
Link to comment
Share on other sites

I have currently programmed four games that use bankswitching. The SuperCharger has 6K of additional RAM that can be dedicated to graphics. After enabling scripts and compiling with vwBASIC I can see that it would be quite useful for many programs even with the limitations in size. 12K is the max with double SC and a little less with Super Charger or other games. All of the games I've made are 32K (I decided to use the highest amount that could easily be put onto cartridges). DPC+ may complicate that, but I've also use it for two games. Titan Axe is 32k bankswitching using the standard kernel. Run Out is 32K using DPC+ and my newest work, Street Fight World is 32K DPC+. I've been programming with Bb for over three years now. I like vwBasic (I will call it VolksWagon BASIC) and will be studying it while I finish up my latest DPC+ game. I am not new to this. I've programmed in C++, Visual Basic, Assembly (a little with my Coco, and I don't think well with it), and several other 'game-making' programs, like Game Builder, etc...

 

I find Visual Bb to be so easy and yet limiting enough to express with that it fits me like a glove. I just want more than 4K total graphics memory, that's all. I could fit two more characters in my Street Fighter clone and all the backgrounds. :P

  • Like 1
Link to comment
Share on other sites

I have currently programmed four games that use bankswitching. The SuperCharger has 6K of additional RAM that can be dedicated to graphics. After enabling scripts and compiling with vwBASIC I can see that it would be quite useful for many programs even with the limitations in size. 12K is the max with double SC and a little less with Super Charger or other games. All of the games I've made are 32K (I decided to use the highest amount that could easily be put onto cartridges). DPC+ may complicate that, but I've also use it for two games. Titan Axe is 32k bankswitching using the standard kernel. Run Out is 32K using DPC+ and my newest work, Street Fight World is 32K DPC+. I've been programming with Bb for over three years now. I like vwBasic (I will call it VolksWagon BASIC) and will be studying it while I finish up my latest DPC+ game. I am not new to this. I've programmed in C++, Visual Basic, Assembly (a little with my Coco, and I don't think well with it), and several other 'game-making' programs, like Game Builder, etc...

 

I find Visual Bb to be so easy and yet limiting enough to express with that it fits me like a glove. I just want more than 4K total graphics memory, that's all. I could fit two more characters in my Street Fighter clone and all the backgrounds. :P

Awesome you are trying vwBASIC Papa! I like RunOut and Street Fight World, looking forward to seeing what you will build :)

 

 

 

I guess 6K means 6K.

 

 

6K is closer to 32K if the code is compiled, vwBASIC supports about 32K of BASIC code:

 

...both gameloops can hold about 12-14K of code, but they share space for graphics and sound (shared with gameloop2) and array variables (shared with gameloop1).

 

bB is compiled too so it's 32K config is holding something like 128K of BASIC source code. I think we should talk about the memory size available to BASIC to keep perspective.

 

DPC+? WTF happened to all the purist nonsense?

 

It would be interesting to see what kinds of games could be written with the Compumate - it had only 2K of RAM for BASIC code.

2K of memory for BASIC is challenging but it's a fairly usable size; the Altair only had 2K after loading Tiny BASIC from tape, same for the Bally Astrocade.

 

If you really want to get hardcore you could see what you can do in just 63 bytes with Atari's BASIC Programming cartridge; that's kind of like the one-liner contests from bitd where you had to write a program in 80 or 255 characters depending upon what your BASIC's line length was :)

Link to comment
Share on other sites

I have considered trying to code the Atari BASIC cart just to see what could be done. Before my wife found Bb and downloaded it for me ("Hey..I bet you would really like this!") I was looking at the Compumate. I really don't like blister-keys though. I would tolerate it if it was all I had.

 

I consider getting help from the ARM processor to build carts that play on the original system to fit into my own 'purist' ideals. I like assembly and all, but I just can't seem to get as creative with it as I can with BASIC. I really love the sprite maker and playfield drawing tools in Bb and I seem to think in BASIC. I have all those old books on BASIC programming for Amiga and Atari computers and toy with AMOS and QBasic as well, but the fun of just sitting down and getting results immediately, like with a visual environment or vwBASIC, is very exciting.

 

vwBASIC will be my next learning endeavor. I like that it's been upgraded to include labels, but I also think there is nothing wrong with the simplicity of number lines. Now that I see that each loop can approach 12K compiled it seems bigger. One factor with DPC+ is that the first and last banks are taken up by the ARM code. I've also found that progressive scan capable CRT's don't like DPC+. I have HD and CRT TVs that play my games perfectly, but my Progressive Scan CRTs look terrible, with jitters and doubled sprites (something I use regularly to get bigger objects) tearing in half with poor sync.

 

I will print the manual (although a much deeper explanation with more examples would be helpful) like I did with VBb and BasiEgaXorz (another endeavor).

 

Thanks a LOT for the compliments on my latest work. It means a whole heck of a lot coming from someone like you. :thumbsup:

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...