Page 2 of 6

Posted: Fri 17 Feb, 2006 10:28 pm
by KermMartian
Probably it uses some Ion routines.

Posted: Fri 17 Feb, 2006 10:39 pm
by Timendus
I don't believe so. I think it should work for any shell, as long as it works with the writeback.

Posted: Sat 18 Feb, 2006 4:31 am
by tr1p1ea
Ducks sprite routines indeed use ion's ... but its an easy modification to make them shell independent. Jim e rewrote the sprite routines so that they are faster and smaller. You can check out his grayscale package here: http://www.revsoft.org/phpBB2/viewtopic ... 26&start=0

Posted: Sat 18 Feb, 2006 3:02 pm
by Timendus
tr1p1ea wrote:Ducks sprite routines indeed use ion's ...
Really? I thought they were adaptations. But I haven't seen the GPP source for ages, guess I was mistaken :)

Posted: Sun 19 Feb, 2006 12:36 am
by threefingeredguy
I have heard that Jim e's is faster, you should follow that link that tr1p1ea provided.

Posted: Sun 19 Feb, 2006 6:00 am
by tr1p1ea
Jim e's is faster. His routine can mix the buffers and out in 73 cycles per byte iirc, Duck's is at 76. His sprite routines are faster/better as well. It also allows for more processing power for the application as the grayscale interrupt it syncronised (as best it can) with the lcd. This helps reduce flicker and enables grayscale at a much less tacing rate.

Posted: Sun 19 Feb, 2006 2:53 pm
by Liazon
now if only I can get it to compile in Latenite. Any help ben?

Posted: Mon 20 Feb, 2006 6:34 pm
by thegamefreak0134
I did some pouring through the package ad noticed a couple of things. The only calls to ion routines in Ducks package are for the sprite routines. I have enough knowledge to write a sprite routine myself (and prolly should for the project) so I can live without his. That leaves the issue of not being able to use the interrupt routines too effectively.

One interesting note is that on all the calculators I tried it on, an interrupt frequency of 6 proved to not only be the fastest, but the best looking. Why the others are there baffles me...

What I need at this point is to get something simple, like a picture or something, up and running in ducks package. I will probably ask for help with the interrupt routine, as it uses a lot of jp and djnz commands and I don't know how to effectively handle these on code cpoying. If everything were relative jumps, I imagine the routine would work fine...

-gamefreak

PS: Does "Jim e" exist on these forums?

Posted: Mon 20 Feb, 2006 9:21 pm
by tr1p1ea
Jim e is a prominent member of these forums. I also suggest that you use his package as you will get more performance out of your calculator. Also if you use BRASS there are options to relocate code which should help with the routine relocation.

Posted: Mon 20 Feb, 2006 9:34 pm
by threefingeredguy
Jim e's code has been written to be faster and more accurate. It uses the built in crystal timers to update the LCD at the perfect time to achieve the maximum effect.

Posted: Mon 20 Feb, 2006 9:45 pm
by thegamefreak0134
OK. And if I gather correctly, since it is a re-do of ducks routines, it should behave basically the same, right?

Where can I get said awesome package?

Posted: Mon 20 Feb, 2006 10:04 pm
by threefingeredguy
Why, my signature points to the related website. This is more exact link.

Posted: Tue 21 Feb, 2006 1:45 pm
by thegamefreak0134
Darn darn darn darn darn stupid school filters... DARN!

For some odd reason, I can't convince our nice network admin that free hosts are not bad. As such, I cannot get anywhere near the file for the package. Could I get someone to e-mail it to me? (thegamefreak0134@yahoo.com) Thanks!

Posted: Tue 21 Feb, 2006 2:17 pm
by kv83
Liazon wrote:now if only I can get it to compile in Latenite. Any help ben?
place a

Code: Select all

#define TI83
at the top of your source file if you compile it for 83. GPP expects that, so it's not on ben's side. Duck made a batch file, which would include the define depending on which calculator you were writing for. If anybody would make a GrayScale template for LateNite, the problem would be away aswell I guess. ("#define TI83P" for a 83+ btw)

Posted: Tue 21 Feb, 2006 2:21 pm
by benryves
kv83 wrote:
Liazon wrote:now if only I can get it to compile in Latenite. Any help ben?
place a

Code: Select all

#define TI83
at the top of your source file if you compile it for 83. GPP expects that, so it's not on ben's side. Duck made a batch file, which would include the define depending on which calculator you were writing for. If anybody would make a GrayScale template for LateNite, the problem would be away aswell I guess. ("#define TI83P" for a 83+ btw)
No, it's my fault. It also breaks compatibility with the API.
The next release of Latenite should come with a fixed Brass template which does away with this problem :(