[GEM-dev] same patch different machines different outcome

Erich Berger eb at randomseed.org
Mon Apr 4 14:15:47 CEST 2005


hi,

since two days i m pondering on this problem.

i have 2 machines:

1) debian testing with old mach64 and experimental dri drivers
2) debian testing with nvidia GF4200Ti drivers 1.0-7174 headers installed
    and gem compiled with them

both run latest gem-cvs

the attached patch is a texture feedback with pix_alpha
in a manner that black becomes alpha.

this works fine on the mach64, but not on the nvidia.
see scrrenshots at:
http://randomseed.org/mach64.gif
http://randomseed.org/nvidia.gif

if u exchange pix_snap with pix_snap2tex then everything works
as desired except on can not use pix_alpha anymore as the
captured image is already textured.

anybody an idea what could be the reason ?

ps: on nvidia an image on the square appears when one
sets the pix_coordinate parameter over 230, but it is a single feedback
and the pix_alpha disappears in a certain area.

ps2: additionally creating the window results on both machines in:
error Gem: Someone sent a bogus pointer to copy2Image
error Gem: pix object [pix_alpha] cannot handle YUV image

isnt native colorspace rgba ?

thx for your help in advance

erich
-------------- next part --------------
#N canvas 227 6 431 643 10;
#X obj 42 429 square 3;
#X obj 12 20 gemhead 50;
#X msg 67 158 0 0;
#X msg 102 158 256 256;
#X obj 12 60 rotate 0 1 0 0;
#X obj 12 40 translate 1 0 1 0;
#X msg 52 371 \$1 \$1 0 \$1 0 0 \$1 0;
#X floatatom 52 351 3 0 256 0 - - -;
#X obj 42 400 pix_coordinate;
#X obj 42 185 pix_snap;
#X obj 42 324 pix_texture;
#X msg 12 153 snap;
#X obj 42 295 pix_alpha;
#X msg 85 257 0 0 0;
#X obj 71 209 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1
;
#X obj 56 233 invert;
#X obj 180 149 sphere;
#X obj 180 91 gemhead 49;
#X obj 180 129 translate -1 0 1 0;
#X obj 180 110 rotate 0 1 1 1;
#X msg 82 350 4;
#X obj 12 124 t b a;
#X obj 175 240 loadbang;
#X floatatom 285 67 5 0 0 0 - - -;
#X msg 285 43 100;
#X obj 151 16 cnv 15 100 60 empty empty empty 20 12 0 14 -233017 -66577
0;
#N canvas 15 422 450 300 gemwin 0;
#X obj 132 136 gemwin;
#X obj 67 89 outlet;
#X obj 67 10 inlet;
#X obj 67 41 route create;
#X msg 67 70 set destroy;
#X msg 142 68 set create;
#X msg 268 112 destroy;
#X msg 132 112 create \, 1;
#X connect 2 0 3 0;
#X connect 3 0 4 0;
#X connect 3 0 7 0;
#X connect 3 1 5 0;
#X connect 3 1 6 0;
#X connect 4 0 1 0;
#X connect 5 0 1 0;
#X connect 6 0 0 0;
#X connect 7 0 0 0;
#X restore 155 57 pd gemwin;
#X text 151 17 Create window:;
#X msg 155 38 destroy;
#X obj 12 82 alpha;
#X obj 55 84 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1
;
#X obj 12 104 color 0.7 0.7 0.7;
#X text 6 592 another error: creating window results in:;
#X text 7 605 error Gem: Someone sent a bogus pointer to copy2Image
;
#X text 7 621 error Gem: pix object [pix_alpha] cannot handle YUV image
;
#X text 7 484 texture feedback is visable as the sphere underneath
the square http://randomseed.org/mach64.gif;
#X text 8 458 problem: on ati mach64 debian testing it looks like i
expect it should:;
#X text 6 511 on nvidia GF4 4200 TI debian testing driver 1.0-7174
i would say it is not working: http://randomseed.org/nvidia.gif;
#X text 6 557 both machines run latest gem-cvs \, nvidia headers etc.
installed;
#X connect 1 0 5 0;
#X connect 2 0 9 1;
#X connect 3 0 9 2;
#X connect 4 0 29 0;
#X connect 5 0 4 0;
#X connect 6 0 8 1;
#X connect 7 0 6 0;
#X connect 8 0 0 0;
#X connect 9 0 12 0;
#X connect 10 0 8 0;
#X connect 11 0 9 0;
#X connect 12 0 10 0;
#X connect 13 0 12 3;
#X connect 13 0 12 4;
#X connect 14 0 15 0;
#X connect 14 0 12 2;
#X connect 15 0 12 1;
#X connect 17 0 19 0;
#X connect 18 0 16 0;
#X connect 19 0 18 0;
#X connect 20 0 7 0;
#X connect 21 0 11 0;
#X connect 21 1 9 0;
#X connect 22 0 2 0;
#X connect 22 0 3 0;
#X connect 22 0 13 0;
#X connect 22 0 14 0;
#X connect 22 0 20 0;
#X connect 22 0 24 0;
#X connect 23 0 19 1;
#X connect 24 0 23 0;
#X connect 26 0 28 0;
#X connect 28 0 26 0;
#X connect 29 0 31 0;
#X connect 30 0 29 0;
#X connect 31 0 21 0;


More information about the GEM-dev mailing list