Author Topic: next version of xlib features (Read 18326 times)

DJ Omnimaga · « **Reply #45 on:** July 26, 2006, 03:14:00 am »

I always had problems with real(9 especially when calling it right before real(2, tr1p never found the pb tho

kalan_vod · « **Reply #46 on:** July 26, 2006, 07:57:00 am »

Hmm, how long ago was that? I might give it a try later, but I think it works fine to do it after

(I do this in chips).

DJ Omnimaga · « **Reply #47 on:** July 26, 2006, 08:42:00 am »

that was when I restarted working on diortem

Demon · « **Reply #48 on:** July 31, 2006, 09:00:00 am »

QUOTE

e.g. if you type "real(9.1.randint(0,255))"->Y1 and then press GRAPH your RAM 'll be cleared
Something is wrong with this command...

Well, one thing is that you said randInt(0,255) - maybe that should be randInt(1,255).

Zeromus · « **Reply #49 on:** August 01, 2006, 03:11:00 am »

The only real( issues I have ever had where when I did not complete the syntax

Halifax · « **Reply #50 on:** August 09, 2006, 01:19:00 pm »

There should be a routine so you can display grayscale by display the lcd 66% of the time and then have the second layer displayed 33% of the time so we can create 4 level grayscale easier.

DJ Omnimaga · « **Reply #51 on:** August 09, 2006, 01:25:00 pm »

pyro went on tcpa today and did !seen tr1p1ea and this is the result

[19:41:54] "tr1p1ea ([email protected]) was last seen quitting from #tcpa 9 days, 8 hours, 48 minutes ago stating (Read error: Operation timed out)."

not really good at all, *xlibman

Dragon__lance · « **Reply #52 on:** August 09, 2006, 03:32:00 pm »

@killerplayer: that'd be sweet! But it'd be incredibly hard to implement in xlib,from my own ASM experience.

Halifax · « **Reply #53 on:** August 09, 2006, 04:06:00 pm »

O well you could prot the routine from TIGCC couldn't you??

kalan_vod · « **Reply #54 on:** August 09, 2006, 05:16:00 pm »

QuoteBegin-xlibman+Aug 9 2006, 07:25 PM-->

QUOTE (xlibman @ Aug 9 2006, 07:25 PM)

pyro went on tcpa today and did !seen tr1p1ea and this is the result

[19:41:54] "tr1p1ea ([email protected]) was last seen quitting from #tcpa 9 days, 8 hours, 48 minutes ago stating (Read error: Operation timed out)."

not really good at all, *xlibman is getting worried

He has been really busy, he has been posting at MC and RS..give him time

threefingeredguy · « **Reply #55 on:** August 09, 2006, 10:08:00 pm »

QuoteBegin-Killerplayer+Aug 9 2006, 07:19 PM-->

QUOTE (Killerplayer @ Aug 9 2006, 07:19 PM)

There should be a routine so you can display grayscale by display the lcd 66% of the time and then have the second layer displayed 33% of the time so we can create 4 level grayscale easier.

Not possible.

DJ Omnimaga · « **Reply #56 on:** August 10, 2006, 02:36:00 am »

not posssible indeed. From ASM in 28 days:

QUOTE

The TI-85 and higher-number calculators have a memory mapped screen. That means a section of the calculator's RAM that holds a bit image of the screen is constantly being monitored. Whenever a byte in this area is changed, the display changes immediately. It is also possible to change the RAM area the driver looks at with a single port output. By switching the buffer location back and forth rapidly, you could create Game Boy-style flickerless 4- or 8-level grayscale.

Unfortunately, the "crap series" (everything lower than a TI-85) uses a driver that stores the screen image in its own RAM. In order to change the display, you have to send each byte in the image to the driver. It is also a very slow driver which needs a delay every time it is accessed.
Hopefully you are sufficiently depressed now, so let's look at how to make the Toshiba T6A04 (that's the name of the driver) our b****.

Control Ports
The two ports that control the LCD are
$10

Logged

Now active at https://discord.gg/cuZcfcF (CodeWalrus server)

lolje

LV5 Advanced (Next: 300)
Posts: 299
Rating: +2/-0

next version of xlib features

« Reply #57 on: August 10, 2006, 02:56:00 am »

When I hear greyscale+basic...
Really genious would be aroutine which needs 2 pics input and then uses them for displaying a greyscale-picture while waiting for a key and storing the number of the key into ans.

That could be e.g. used for Rpgs... you only need 2 layers to create 4-lvl-greyscale, allright? So you could create the two pics with the tilemap-function, store them, and then use THIS new function to create a (think so) quite flickerless greyscale. And when you have the getkey in ans afterward it would be perfect!
Basically that would be the loop containing grey+getkey, just in asm.

Logged

83+/84+ xLIB projects
Age of culture II (~89%)

Contact: [email protected]

DJ Omnimaga

Clacualters are teh gr33t
CoT Emeritus
LV15 Omnimagician (Next: --)
Posts: 55942
Rating: +3154/-232
CodeWalrus founder & retired Omnimaga founder

next version of xlib features

« Reply #58 on: August 10, 2006, 03:32:00 am »

well actually I made a tutorial explaining gs for BASIC, altough it use omnicalc, but its mostly a matter of XORing a checkered pattern very fast, basically assuming the xor mask is in pic 0 call a real(3,0,0,1 command after every BASIC command in your walking engine.It will look almost flickerless on every calcs, except threefingeredguy's

Logged

Now active at https://discord.gg/cuZcfcF (CodeWalrus server)

Dragon__lance

Guest

next version of xlib features

« Reply #59 on: August 10, 2006, 04:27:00 am »

That's the main way to do grayscale in BASIC.The only way to do th e idea of pic swapping,would be for xlib to run a interrupt in the basic program,like every other line of code,it'll automatically swap the pics.I'm not quite sure if that's possible in ASM (anyone care to correct me?)

Logged

Print

Pages: 1 2 3 [4] 5 6 Go Up

« previous next »