[GEM-dev] mesh object for gem

[cyrille henry]

hello,

marius schebella a écrit :
> hi cyrille,
> this is cool! I am no friend of the gem standard anyway, so, if the 
> range is between 0 and 1 that would be perfect. but if you want to go 
> with the gem standard, then maybe you can add a message flag to switch 
> between gem standard (-1 to 1) and shader standard.
yes, this is also a good option.

> what do mean by precomputed? would that mean everytime you change the 
> dimension the values get recalculated?
yes, curently, the texture coordinate a computed every time the texture change.
> I guess that would make the object faster, no?
i don't know if 2 multiplication is slower than reading in a 2d array.

cyrille

> marius.
> 
> cyrille henry wrote:
>> hello,
>>
>> here is a square mesh generator object i made mixing code from a square 
>> and newWave, disigned to be used with vertex shader.
>> i don't know if it should go from -1 to 1 (gem standart), or from 0 to 1 
>> (best for vertex shader)
>> i also don't know if texture coordinate should be precomputed (like in 
>> newWave) or not.
>>
>> so, tell me what you think.
>>
>> maybe i should accept cvs write access and commit this myself...
>>
>> cyrille
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> GEM-dev mailing list
>> GEM-dev at iem.at
>> http://lists.puredata.info/listinfo/gem-dev
> 
> 
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev
> 
>