[GEM-dev] 2textures + gemframebuffer

[cyrille henry]

IOhannes m zmoelnig a écrit :
> cyrille henry wrote:
>>
>>>
>>> probably i should have a look at a patch where the problem is really 
>>> exposed.
>> ok. you can have a look at this file. on the right : i use a pix_image 
>> to set the texture coordinate, in order to use it in the shader.
>> without loading this (unused) image, it does not work.
> 
> so what would be the preferred way of doing it?
i don't know what is possible. but i think that using a dummy image is strange.
it would be great if this patch could work without the dummy pix_image (and then use the real texture coordinate from the frambuffer, and not the one from an other image).
curently, the dummy image size should be the same as the frambuffer size. if not, you have to make correction in the shader.


> 
> the attached modification of your example works fine and uses the 
> framebuffer itself as a dummy texture. is this what you head in mind?
>>>
>>> (and i should add better aliases for the messages to 
>>> [gemframebuffer]; like "dimen" instead of "dim", 
>> ok
>>> and "rectangle" instead of "mode" to make it in-line with other 
>>> objects...)
>> pix_texture use "mode 0" and "mode 1".
>> what object does use rectangle?
> 
> [pix_texture] :-)
ok. i did not know that.
what is the oposite of rectangular?
> i added this alias because i kept forgetting what "mode" actually means 
> - the rectangle-mode, the repeat-mode, the clientstorage-mode, the 
> quality-mode or the texenv-mode.
yes, i understand.
could you also update the help file?

cyrille

> 
> 
>>
>> i just add a feature request to add a texunit message to the 
>> gemframebuffer, this would be very usefull.
> 
> 
> i have seen it and agree.
> 
> fmasd.r
> IOhannes
> 
>