MaxCoderz

Also, the lower quality will be even less noticeable once I add objects, because the sprites are going to be normal resolution.

Dwedit wrote:How did you decrease the quality?

I pretty much made the resolution 48x64 and stretched it. Slightly more than half the calculation needed as before.

Wow that is looking incredible, its amazingly fast! Are you using any neat tricks for speed increases? For one thing, I'm using the BC, DE, and HL normal and shadow registers for the innermost loop. Also, a bit of SMC. I have decreased the quality since the earlier versions, which almost doubled th...

Some of you have seen the screenshots floating around on IRC. Now, it's official! Check out the project forum here.

Art_of_camelot wrote:PC= A BIGGER BETTER calc.

You are correct in your insinuation that blue means better.

*bumpity bump bump*
Any progress whatsoever in the last 4 months?

Well, it's getting to the busier time of the year in regards to schoolwork. It'll pick up a lot in the summer, it always does.

Heh, might as well post mine too. It's concise and to the point, holds most z80 command info you'll ever need (and more), and easily printable on one page.
calc84maniac's z80 reference

driesguldolf wrote:

• If someone can tell me how to recognize a 2 byte token I can support that too

He doesn't want two byte token support, because that's the major slowdown factor in the TI-OS routines.

*cough* Fn+/ *cough*

It means you don't have enough posts. It's a spambot deterrent.

vuurrobin wrote:does the tokens for the hacked pics work with archive/unarchive. if so, could you tell me/us how to get those tokens, (or create a small asm program that gets the tokens).

http://www.ticalc.org/archives/files/fi ... 39138.html
[/self promotion]

kalan_vod wrote:It should, you might want to email the maker of the oncalc assembler. Make sure include if he had any hooks installed (noshell xlib omnicalc etc..).

What do I have to do with anything? Other than something like this happened to my first calc and I didn't know about the Del trick...

But this won't search for the appvar at each parser fire-up, only at the real(50 (or whatever it is).

...or store in an appvar?