Quoting chris clepper <[EMAIL PROTECTED]>: > On 10/14/07, Thomas Mayer <[EMAIL PROTECTED]> wrote: >> >> >> > [gemhead] >> > | >> > [pix_(movie|film|image)] <-- reg_exp for human reading only >> > | >> > [pix_texture] >> > | >> > [gemhead] | >> > | | >> > [pix_texture] >> > | >> > [square] > > > I can't figure out what this diagram is showing.
the diagram shows: one [gemhead] is uploading an image to the gfx-card via [pix_texture]. another gemhead uses this texture and displays it onto a square. the 2nd outlet of [pix_texture] should output enough information, so that another [pix_texture] (without a pix in the chain), can re-use the same texture when it get's the info in its 2nd inlet. thomas: what is the problem? "not working" is a rather vague description. i recently discovered that the output of the 1st pix-texture would give wrong texture coordinates when using normalized textures (power-of-two sized). the w32-binaries certainly still have this bug. for now i can think of two workarounds: - if your machine/build supports it, try using rectangle-textures and see if it works. - if it is not supported, try manually setting the texture-coordinates to 1,1 (e.g. use [pix_coordinate]) (you could also manually set the texcoords by modifying the messages that comes out of [pix_texture]; it is human-readable and of the form (iirc): "<texid> <width> <height> <texmode>"; you want to modify <width> and <height>) mfa.dr IOhannes ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
