CurtisP

I just don't understand all the fuss. I love Courier (and not that New one either).

The Driving Controller does not work like a paddle at all. It actually generates a binary gray code. You would need a specialized ASM read routine to read it.

I really hate to be negative, and don't want to discourage you, but I have to admit that the preview comes across as ameteurish, particularly the lack of copy editing. I'm afraid that this might dissuade others from paying for the actual issues, just as it has dissuaded me.

You should call it Grand Theft Atari.

Thanks for checking that out for me. I've compiled the data for further study.

I've been looking at scans of "black" manuals (Adventure, Combat, and Bowling) and the height to width ratio do not match 5"x7". If anyone has one handy, could you measure it?

Here's the thing. The moment you create an artistic work, in the US and most other countries, its automatically copyrighted, and you are a copyright owner. Copyright registration just makes it easier to prove ownership in court, but otherwise gives you no other benefit. You have every right to put a copyright symbol on your own work. If you put your name on the manual and have ID on you, you can probably get the Stinkos cop to lay off. Or take your business elsewhere. In addition, all copy places should have a standard release form for you to sign which is you stating that you may legally copy the work in question, which leave them off the hook.

I was thinking about writing Telengard for the 2600. This would require referring to the manual for actual game play. There were carts in the old days you couldn't play without the manual. Two that spring to mind are "Raiders of the Lost Ark" and "Space Shuttle"

Is there a list somewhere of the sizes of the various 2600 manuals?

I have often that that raycasting would work with the bBasic playfield.

Personally, I'd rather not pay $10 to $20 for a preloaded Credit Card when I have a Paypal account that works just fine.

You could do a lot in 4K if you optimized your code.

"Stealing bandwidth" generally refers to embedding data in your webpages that come from another server. For example, having a page full of img tags that all refer to images hosted on another server. In this case, your server is only serving the 1 or 2 k HTML file, but the other server (owned by some one else) is serving the 100s of K of image files. This was more of a concern when metered hosting was more common. This differs from linking in that the file only gets served from the other server if the user clicks on the link. As far as linking goes, I think, that in these days of Google adsense and other advertising methods, the best etiquette is to link to the containing page, so that the owner of the page and file can get his revenue.

quote name='Nati' date='Sat Aug 15, 2009 11:39 AM' post='1816982'] how about Ari the ant? And the enemies could be spiders, and deadly. The walls would just stop you from moving. Code for Ari is here http://www.atariage.com/forums/index.php?showtopic=148331

This would make a good generic function or subroutine.

Wow, it's been almost two years since I last updated this tutorial. I'll try not to wait as long next time. Here is the latest example program. pmopts.bas pmopts.bin

Good work. See if you can make Astroboy into a multicolored sprite.

Ari has been animated. The code is not at all optimized, but it works. aritest.bas aritest.bin

*Smack* Home don't play dat!

Added four lines of code to do smooth scrolling. Since indexes are limited to a single byte (0-255), the most lines you can have in your playfield is 64. Scroll3A.bas Scroll3A.bin

It appears that ARI is the Japanese word for Ant. Here he comes, There he goes. He's the Ant named Ari And when he Wins the game, He will yell Atari! Go, Ari, Go!

Ari Ant as a 16 line high single player. I'm pretty happy with the front and back view. The side view could use some work though.

Remember kid's don't do drugs...

I'm all for Ari Ant. We need some player data.

Now that's what I call a circuit!