[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 131-color mode
- Subject: Re: 131-color mode
- From: "BLuRry" <brendan.robert@gmail.com>
- Date: 11 May 2006 10:38:48 -0700
- Complaints-to: groups-abuse@google.com
- In-reply-to: <446370a9$0$1362$9a6e19ea@news.newshosting.com>
- Injection-info: i39g2000cwa.googlegroups.com; posting-host=206.210.17.33; posting-account=N5hIbA0AAACzTGVDiZh9ucUYdzqr6aq7
- Newsgroups: comp.sys.apple2
- Organization: http://groups.google.com
- References: <1147323379.578269.85920@i40g2000cwc.googlegroups.com> <446370a9$0$1362$9a6e19ea@news.newshosting.com>
- User-agent: G2/0.2
- Xref: g2news2.google.com comp.sys.apple2:7360
yeah, the 65c02 opcodes were intentional. I didn't *have* to use them
but wanted to write my storeWord macro to optimize to stz whenever
possible to save a miniscule amount of time and memory. Since my next
stop with this will be applied to double-hires images, I figured nobody
would be completely pissed off. sorry I didn't mention it -- the
applewin debugger works beautifully at disassembling it, FWIW.
Maybe a middle-of-the-road approach to keep a game's framerate up would
be to use the 80x48 double lo-res mode with the 131-color hack. If you
wanted to use this to make an enhanced color game, you'd have to write
code that could update a page completely during the vbl. Might make
for a slow or limited game.