The softviewer does Reflectionmaps now (this is quite slow of course) and evaluates the transparencyEnabled flag from the renderinghints for compatibility reasons (I am still not happy with this flag since it can cause a lot of confusion...).
BTW is it true, that the ImagaData now allways gives 4-byte per pixel arrays? the softviewer used the length to determine wether a texture has alpha and therefore the textured triangles need to be treated like transparent ones. Allways getting 4-byte textures therefore gave those textured triangles quite a performance penalty. Now of course the transparencyEnabled flag can force the renderer to ignore the (in fact absent) alpha.
Is there any other way to get information on wether a texture has transparency !=0 or not?
Tim
softviewer update
Re: softviewer update
Looks great!timh wrote:The softviewer does Reflectionmaps now (this is quite slow of course) and evaluates the transparencyEnabled flag from the renderinghints for compatibility reasons (I am still not happy with this flag since it can cause a lot of confusion...).
ImageData always had 4 bytes for each color as far as I could see from cvs history.timh wrote:BTW is it true, that the ImagaData now allways gives 4-byte per pixel arrays? the softviewer used the length to determine wether a texture has alpha and therefore the textured triangles need to be treated like transparent ones. Allways getting 4-byte textures therefore gave those textured triangles quite a performance penalty. Now of course the transparencyEnabled flag can force the renderer to ignore the (in fact absent) alpha.
Is there any other way to get information on wether a texture has transparency !=0 or not?
Steffen.