yay! source is included!

Darn ... right when I'm making a Chess game in Basic ... oh well.
And what's with all these first post comments, even though all but one of them are first post?

Even my (admittidely horrible) othello ai is slow in basic.

I guess a 2 player chess is alwright in basic though.

oh, and I would like to see this (or similar) on my 83+

so would we all!

I probably would have had a working version of my Chess game out already (the current version that's out draws pretty pictures, in black and white of course, and then dies after you try to move) except for some odd, horrible, obscure reason, it keeps on skipping one of the If Then statements ... and then gives a domain error ...

Try looking for places where you use GoTo-s to exit statements that have an end statement.

like look for something similar to the following
---------


if Ans == 2: Then
2->B
Goto A
Else
"Do Something
End

lbl a

or a goto from a loop (repeat, while...)

It seems that ti calcs see that you exit the loop (The next end statement it encounters does not take you back to the begining of the loop if there was a goto outisde of it), but the stack continues to grow.

I have *never* had that problem. Which calculators are you talking about (number-wise)?

It's only a real problem if there are a lot of GoTos from block statements, which is probably the case with a chess game (which might have somewhat complicated algorithms).

I don't have too many of those ... it mostly calls various subroutines (programs that do a certain function and then return).

What it is is these people don't check the posted site first and they have no idea if they are really going to be first post. So, they just say so for fun.

First post!!!

38th post!!! (I think...)



w00t!
!t00w

w00t!t00w

Oh, I had this great idea for better "on-calc" programming. You could type in ASM programs in a program editor type thing and then there could be a compile thing that would check for syntax errors and stuff and then it could compile them, wouldn't that be so cooL?

ticalc only puts up posts every 2 mins or so, so it may look like theres no other posts, that happened to me with omnicalc

i beat you to that one!!

Why does the 86 get so much attention when an ASM game comes out? I know it is capable of 4-bit grayscale, but wtf? Maybe I should get an 86...
w00t!

Actually, most TI-86 games use 2-bit grayscale. 4-bit is 16 shades of gray.

2-bit?

Oh, never mind, I get it

00
01
10
11

but wouldnt that only end up being 3 colors?

4 if you count white as one of the colors, I believe.

I remember in BASIC when I used to try to make grayscale by flickering black and white off and on. :)

Ha, yeah... or the TI-89 CyclePic command...

Speaking of CyclePic, I've made a fractal program that draws 2 or 3 pictures, one for each gray layer. When I CyclePic them, I get a slightly flickery grayscale image.

If you don't care for details, ignore below. These details are for 3 layers.
Layer 0 is light gray (1/7 as dark as black), layer 1 is medium gray (2/7 as dark as black), and layer 2 is dark gray (4/7 as dark as black). This allows for any combination of layers to get 8 grays (0/7 up to 7/7; easy to see if you understand binary at all).

To use these layers with CyclePic, I saved layer 0 in mandel7; layer 1 in mandel[5 and 6]; and layer 2 in mandel[1 to 4] (reverse ordering simplifies it somewhat). I just did 'CyclePic "pic",7,0.01' to see the completed image.

Note: I've found that any delay value below 0.05, even 0.04999..., has no delay at all. This might have something to do with the 200 Hz interrupt clock, or something.

LOL never got that to work properly

Well I'm just making this up, of course, but
00 could be black
01 could be dark-gray
10 could be light-gray
11 could be white

...or something, I don't really know how it works :}

One layer typically is displayed for 2/3 of the time...So 00 would be white, 10 would be light gray, 01 would be dark gray, and 11 would be black.

More logically would to have

00 white
01 light gray
10 dark gray
11 black

due to the bit weights.

That's no different from what I described...either you have the first layer for 2/3 the time, or the second...it doesn't matter at all.

I know they're really the same, but describing the dark gray layer with bit 1 rather than bit 0 just makes more sense to me.

well PHBTBTBTBTBTTTTBPBTBTBTBTBTT!!!

Don't make a p00p!

port Chessmaster 86 to the 83!
PLEASE!

Okay, I'm getting sick of reading these port requests. Whenever I write a program, I write it because I think it's fun and I'm interested in it. I don't really care about chess, sorry. I will program what I want, so please stop pestering for port requests. If you want something ported, do it yourself.

Yeah, guess that makes more sense.

The 89 is capable of 8bit, and (slowly) 16bit grayscale, but know one seems to care...

--but me.

The 86 is also capable of 8-bit and 16-bit grayscale ... Levi Lansing's Animation Studio 86 makes movies in 1-bit, 2-bit, 4-bit, 8bit, and 16-bit grayscale. But I've never seen a game that's used 16-bit grayscale (or 8-bit I think) grayscale for sprites or graphics ...

It's because of three reasons: having more grays is slower, and more grays (for sprites) means more storage requirements.

I think the third reason that you forgot to mention is that it flickers like crazy!

...therefore, anything above 4-bit (or even 2-bit) grayscale is not worth having in games. That's the way I see it. p00t!

a00t!
b00t!
c00t!
d00t!
e00t!
f00t!
g00t!
h00t!
i00t!
j00t!
k00t!
l00t!
m00t!
n00t!
o00t!
p00t!
q00t!
r00t!
s00t!
t00t!
u00t!
v00t!
w00t!
x00t!
y00t!
z00t!

No, no, NO! It's capable of 8 LEVEL and 16 LEVEL grayscale, not 8-BIT and 16-BIT. There is no way a TI-89 can handle 32 shades of gray, which is what 16-bit grayscale is. That would take a a) much faster processor and b) much faster refresh rate than what the 89 has.

16-bit is 256 shades. 16^2

What are you guys smoking?! 16-bit is 65536 shades of gray (2^16 = 65536, not 16^2). It's just simple arithmetic.

WTF? It's 256!

No, 16-bit is 65,536. Each bit is either 0 or 1, thus 2 possible values. So if you had 2 bits, then the possible values you could store would be 2 * 2. Three bits would be 2 * 2 * 2, and so on. Thus, a 16-bit number can hold 2^16 (65,536) values, typically in the range 0 - 65535.

Sometimes it's so damn depressing to see so many posts written by people who don't even have the faintest idea what they are talking about...

But in this case it is rather funny. :P

LOL I like funny!

no, it's not worth the money. If *your* going to spend that much, get a 68k calc.

get an 89

Voyage *cough* 200 *cough* will be good too!

Nah ... stick with the 89. At least it's not banned on the SAT ...
But if you care that much, get an 86. Not banned on ANYTHING (except no calculator/scientific calculator-only tests hehe). And, it's pretty good for most stuff, unless you want to do symbolic operations.
The reason why there's all this fuss about 86 ASM programs is because very few are made ... look in the file updates and you see this huge list for 83/+ and 89, and then very few for the 86.

but what about the dusty TI-80's & TI-81's (i think they need cleaning)? Not many games come out for them too...

That's because you'd have to type them in by hand if there were any games.

lol

I used my 89 on the ACT, too... apparently, they didn't really care.

oh no.
i'm speachless
the going has finally arrived


(your/you're)

Yeah, I'm peachless too.

...

707

717

707 upside-down LOL is.

The 717 is old, I like the 747 myself. That and the long-range version of the 777 :)

737

++ ++
|| ||
|| || -<+
|| ||
|| ||

Not funny.

You need two...


NOT FUNNY!