Prizm Useful Routines -- post here!

[z80man]

Not much optimization I can see there other than changing the flags in the makefile. The only thing I might do is include some type casts because your arguments are unsigned chars which don't have the necessary width for your bit shifts. My own personal preference is to use 24 bit color and then convert it to 16 bits using a simple routine because it's much easier to write out in code but your method does have a speed advantage.

[PierrotLL]

IsKeyDown equivalent

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9 10

int keydown(int basic_keycode) { const unsigned short* keyboard_register = (unsigned short*)0xA44B0000; int row, col, word, bit; row = basic_keycode%10; col = basic_keycode/10-1; word = row>>1; bit = col + 8*(row&1); return (0 != (keyboard_register[word] & 1<<bit)); }

Expect a Basic keycode (27=right, 38=left) or 10 to test the AC/ON key.
It allow to detect multiple pressed keys simultaneous.

[Eiyeron]

The size of float based routines is really quite negligible and they don't use any extra ram because the entire executable is stored in flash. You could use a fixed point float in this situation but I would advise against them in this situation as the best way to write them out would be to use pre-defined macros such as TWO_POINT_FIVE which would be 0x00028000 in a 32 bit fixed point notation. The other alternative here is to specify when calling the function what size you would like to scale it to instead of providing a scale factor. Perhaps in this situation 2 different functions ought to be developed. One for rather straightforward scales that can be easily implemented such as x.5, x2, x4 and so on. This would be called as 2 raised to the x power. For example passing 0 as the scale will result in a sprite with no change in size while 1 will be x2, 2 as x4, 3 as x8, and so on. That would also mean that -1 would be .5, -2 as .25 and so on. The second routine would require much more overhead and be called with either a float factor or specify the new image size. If this sounds good I can start work on the first routine and have that out in not too long.

Bump-bi-di-bump the topic for asking someone to realize zoo-msacled sprite drawing function. That could be very useful to some animations..
I think always that 2^factors would be easier and faster to use...

moderator edit: fixed

[DJ Omnimaga]

I think you put your answer inside the quote Eiyeron

[z80man]

The size of float based routines is really quite negligible and they don't use any extra ram because the entire executable is stored in flash. You could use a fixed point float in this situation but I would advise against them in this situation as the best way to write them out would be to use pre-defined macros such as TWO_POINT_FIVE which would be 0x00028000 in a 32 bit fixed point notation. The other alternative here is to specify when calling the function what size you would like to scale it to instead of providing a scale factor. Perhaps in this situation 2 different functions ought to be developed. One for rather straightforward scales that can be easily implemented such as x.5, x2, x4 and so on. This would be called as 2 raised to the x power. For example passing 0 as the scale will result in a sprite with no change in size while 1 will be x2, 2 as x4, 3 as x8, and so on. That would also mean that -1 would be .5, -2 as .25 and so on. The second routine would require much more overhead and be called with either a float factor or specify the new image size. If this sounds good I can start work on the first routine and have that out in not too long.

Bump-bi-di-bump the topic for asking someone to realize zoo-msacled sprite drawing function. That could be very useful to some animations..
I think always that 2^factors would be easier and faster to use...

moderator edit: fixed

For shrinking sprites factors of 2 would be much faster while for enlarging there wouldn't be a difference. What could be done is that the routine checks if a factor of 2 is used and then resizes using the proper routine. It isn't too hard to check whether an integer is a factor of 2 or not especially if you limit the the scale size to something like x16

[Eiyeron]

I think you put your answer inside the quote Eiyeron

I think I should miswrite somewhere: I request the help from someone to make this function...

Anyway, my function for my project

Two pixels are concatened like this:
0bAAAABBBB
or
0xAB

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

void CopySprite_Palette_Alpha_Nibbles(unsigned char* data, unsigned short* palette, int x, int y, int width, int height) {    unsigned short* VRAM = (unsigned short*)0xA8000000;    unsigned short* ptr = VRAM + y*LCD_WIDTH_PX + x;    int i,j;    unsigned char nibble;  //Get the color's index to use.    for(j=0; j<height; j++) {                 for(i = 0; i < width; i+=2)                 {                 nibble = (*data)>>4; We get the first pixel                         if(nibble)  //First index is alpha.                                 *ptr = palette[nibble];  //COpy from the palette                 nibble = (*data) %16; We get the second pixel                         if(nibble)  //On the road again                                 *(ptr+1) = palette[nibble]; /*                      else                                 *(ptr+1) = palette[0];*/ // FOr tests                         ptr+=2; //We go furtherer on the VRAM                         data++; //Idem                 }                 ptr += LCD_WIDTH_PX-width; // Go one line lower.    } }

Max 16 colours, enough for Pokémons, in example... :-°
First index is alpha
(Could you please too adapt this function to add a zoom factor, please? I would be erternally grateful)

[z80man]

Could I get some comments on that routine. Always a good practice cause it can often be difficult for some people to understand others code. I'm out of town right now but I'll write something up when I get back tomorrow

[Eiyeron]

Okay... I'll do that!

EDIT: DONE!

[[email protected]]

Sorry to go off topic, but z80man, PLEASE could you tell me how you got a gb emulator on your casio, and is there a way to run ti games on a casio?

Edit: oh wait, I was on topic, lol, but is there something like ti-boy for casio prizm that converts file to calc format rather than running it as an emulator, or maybe even an emulator (I want Pokemon but emulators are usually too slow but I'm sure GBC will be fine with Prizm if can't use that method)

[JosJuice]

Sorry to go off topic, but z80man, PLEASE could you tell me how you got a gb emulator on your casio, and is there a way to run ti games on a casio?

Edit: oh wait, I was on topic, lol, but is there something like ti-boy for casio prizm that converts file to calc format rather than running it as an emulator, or maybe even an emulator (I want Pokemon but emulators are usually too slow but I'm sure GBC will be fine with Prizm if can't use that method)

TI-Boy is actually an emulator. There aren't any emulators for the Prizm right now, and I don't know of any current projects to make one.

[Eiyeron]

CopySrpite alpha palette with clipping :

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

void CopySprite_Palette_Alpha_clipping(const unsigned char* data, const unsigned short* palette, int x, int y, int width, int height) {    unsigned short* VRAM = (unsigned short*)VRAM_ADRESS;    unsigned short* ptr = VRAM + y*LCD_WIDTH_PX + x;    int i,j;    int real_width = x+width > LCD_WIDTH_PX ? LCD_WIDTH_PX - x : width;    int decal = x < 0? -x : 0;    if(real_width <= 0 || decal >= width) return;    for(j=0; j<height; j++) { ptr += decal; data += decal; for(i = decal; i < real_width; i++) { if(*data) *ptr = palette[*(data)]; ptr++; data++; } data += width - real_width; ptr += LCD_WIDTH_PX-real_width;    } }

[sry9681]

hey z80man. I was just wondering, is it possible to have an emulator on the casio prizm? any type of emulator because i see your avatar picture with pokemon on the screen and i was wondering if that was real or photoshopped?

[calc84maniac]

Emulators are certainly possible, but nobody's written any. Don't look at me... Also I'm pretty sure that's photoshopped from a common TI-Boy blog screenshot