>>There are no comments on this article yet. Why don't you add one?

OK, I'll add one.

Correct me if I'm wrong, but this doesn't seem to be extensively documented to the point where a programmer could use voxels in an applied setting.

Without much guesstimation, that is. Is there mathematical documentation or formulas that one should use, or is just graphics?

You should be shot for typing "guesstimation"....

-W-

Would you like to suggest a word that I should have used instead? It is not a guess because it is reasoned and it is not estimation because there is no mathematical or statistical foundation for the figure that results. Or better, would you like to comment on the topic at hand.

Well, how about a real word? Yes I know that it is, but it sounds... stupid.... It probably comes from this other math theacher that does not know shit. She had to ask me for help, and I did not even have her class. She used the word guesstimate. I wanted to shoot her for it.

-W-

"Guesstimation" is just a mix of "guess" and "estimation", and it's perfectly acceptable to use it to mean the same as it sounds. It's kind of like the word "automagically" which is a combination of the words "automatically" and "magically" and means pretty much what it sounds like too.

That stands for "Gnome Estimation". You're wrong, grammar Nazi.

Oh! Would you like some ice for that burn?!

Does the program use fast methods to print numbers into strings ("itoa") and display strings ? Switching from DrawStr to a fast method boosted Ice Hockey 68k.

negative. how fast are the routines from ice hockey compared to DrawStr?
i think the speed benefit will be hardly noticeable. even if i disable any text output (and conversions) i cannot recognize any difference in speed.

@everyone:
i've missed a serious input bug in the V2S executable, it's already fixed now. you can download v1.3 from me or wait for ticalc.org's update.

>>how fast are the routines from ice hockey compared to DrawStr?
They are MUCH faster! When I first implemented them into Ice Hockey, the game speed jumped so much that I couldn't even see the Puck - so I had to add a game speed setting.

If you are drawing text input to the screen every frame (or nearly so), you should definitely notice the difference.

i've reviewed the code, seems promising. it shouldn't take long to replace DrawStr... hopefully the landscape will not disappear like your puck! :-)

i'm drooling over a concrete shed. yum.
Maybe i'd be more positive if i had an 89, but i'm so jealous i have to be negative to cover it up.

That's understandable.

Yeah, the part about "make-you-drool graphics" was right...man, I wish I had an 89...

*drools* now i just need a 86k calc X(

I hope you mean a 68k calc :)

I need a 86k calc too. All I have is a z80 and a 68k.

Yeah, really. Z86k: Motorola/Zilog 180MHz, runs Z80 and M68k programs. Really, really fast.

(Try to find out where the speed came from.)

Um, the Z80 in the Z80 calcs is a Z180?
That's all I can think of.

Clue: the fastest z80 is 15MHz, and the fastest 68k is 12 MHz.

12 * 15 = 180

Precisely. Give yourself a cookie.