NoNameNo wrote:

yes you can using drawpart, then screen2texture

but i think drawpart only could do the job you need

Hi, great hornor to be answered by the author!

The problem is that I want to store the textures in an array, for using them later.
I'm making a port of a game, so it is not my decision....here it is the original code:

extern int grap[161][8], mgrap[51];

mgrap[1] = LoadGraph( "res/brock.png" ) ;

x1=1;

for (t=0;t<=6;t++){
   grap[t][x1] = DerivationGraph( 33*t, 0, 30, 30, mgrap[x1]) ;
   grap[t+30][x1] = DerivationGraph( 33*t, 33, 30, 30, mgrap[x1]) ;
   grap[t+60][x1] = DerivationGraph( 33*t, 66, 30, 30, mgrap[x1]) ;
   grap[t+90][x1] = DerivationGraph( 33*t, 99, 30, 30, mgrap[x1]) ;
}

then he display the image using like:

drawimage(grap[1][1], x, y);

The derivationGraph functions seems to select a certain area of the image stored on mpgaph[1] (in this case) and store it in the grap array.

So my idea is to replace LoadGraph with load texture function, and make "grap" a array of (part of) textures, so I can display the textures easily replacing drawimage.

Or do you have a smart idea? (i'm still searching a better solution )

Thanks in advance!

Last edited by scognito (2010-01-10 15:07:04)

I'm at work and cannot code, but since I have some doubt I'll post the code here to "translate" the code "grap[t][x1] = DerivationGraph( 33*t, 0, 30, 30, mgrap[x1]) ;"

Assuming that (m)grap array are arrays of GRRLIB_texImg I would use something like this?

GRRLIB_DrawPart  (  0, 0, 33*t, 0, 30, 30, mgrap[x1], 0, 1,1,0)
GRRLIB_Screen2Texture (30, 30, grap[t][x1], true);

I'm not sure about that though...

Yeah I read the doc, it is very useful, indeed I was confused about the missing width and height values...what I missed was what you just sayd: "and will use the Width and Height you declare when you created the empty texture".
I think you should add this information for helping other users (if you think it is useful).

Can't wait to try this out at home, thanks!

from what i remember when i coded it yes you can specifiy odd or even coord, the only obligation you have is to create free texture using a multiply of 4 for width and height !! this is  needed by GX !! not by grrlib !

i dunno how is your texture, but i think you should also disable antialias, since GX will try to antialias the new texture with around pixels, and around pixels are often from the next tile ... it can introduce a little glish around each tile/new texture.