Chris,
Substituting pix_film for pix_movie brings on the previously discussed rendering problems.
I'm not sure if you meant for me to try pix_texture in the same place, but when I did I got the following messages immediately:
gamepad_input.pd 44 0 59 1 (gatom->pix_texture) connection failed gamepad_input.pd 59 1 39 0 (pix_texture->unpack) connection failed gamepad_input.pd 59 2 43 0 (pix_texture->bng) connection failed
And I got the following messages when trying to use the patch to open a video:
pix_texture: not using client storage error: pix_texture: no method for 'open'
Despite some of the messages above, the gamepad input worked fine all the time.
J
On 24/1/06 18:30, "chris clepper" cgc@humboldtblvd.com wrote:
If you substitute pix_film and pix_texture for pix_movie does it do the same thing? There is a problem that I introduced recently with turning rendering on and off, but that should not be in the released version of GEM 0.90.
On 1/24/06, Jonathan Goodwin jonathan@jgoodwin.co.uk wrote:
Ok, I've attached my patch so far...be prepared for some obvious mistakes I expect!...i'm very new to this!
I think I may have found the problem...The rendering problems begin when I try to add more than one set of GEM objects. In the working patch I've included, you'll see that I have mapped a playstation controller to act as a video trigger. I'm looking to have more than one channel of video, hopefully 4 or 5, which will each be triggered by different gamepad keys. So what I was doing was copy & pasting the working set of GEM objects and linking them to a separate controller key. This is when the problems start.
Many thanks, Jonathan