Yuku free message boards

Scorpius I took a quick look at the code, it looks good but you are rendering to the size of the wings window correct?
That will give you two problems:
1: performance on high resolution screens and the user have a fullscreen wings window.
2: the resolution will not be square i.e. the window is most often wider than the height which will cause a slight miscalculation.

I think the render window should always be square, and I think a 32x32 window will be enough actually most apps use
a byte per vertex (and every who bakes it to a texture use that), i.e. 256 different values and math:sqrt(256) is 16
so that 16x16 is the minimum.
You could use 32x32 or higher for antialising issues and test some higher to see what the performance impact is,
but the results will not be better when you in the in end will be rounding it off a byte.

Or maybe my reasoning is totaly wrong :-)

But that should give better results and be a lot faster.

But it was nice and short code, I've been wanting to have this for several years and it's so simple when you see the code,
really nice.

Another idea if you do this from inside the autouv code, you can create a temporary #we{} which does the calculation and
then use those vertex colors in uv-rendering. Then the users won't loose there uv-coords but the result is only on the uv-map.