davepermen
Regular
as far as i can see this algo does indeed replace the ordinary way to do full trilinear filtering in some cases. the only reason why the bits are different is simple: round-off-errors. this always happens if you shuffle / replace EQUAL operations in a filter. this is something we have to face all the time.
because of that, i don't see all the complains. ati found a an optimisation, where certain ops are useless for the trilinear, so it doesn't always need to do the full job (but result in the same output, except for roundoffs). this is all fine.
this is like saying a mult instruction is not allowed to simply return 0 if one of the ops is 0, because it would not calculate it then. there is no difference (in this case, not even a roundoff), so whats the mather? and if one of the ops is one, you're allowed to directly return the other op, instead of calculate *1.
this is about what this algo does (except, more complex, much more clever, and with a lot of work behind the scenes, to get it done..).
because of that, i don't see all the complains. ati found a an optimisation, where certain ops are useless for the trilinear, so it doesn't always need to do the full job (but result in the same output, except for roundoffs). this is all fine.
this is like saying a mult instruction is not allowed to simply return 0 if one of the ops is 0, because it would not calculate it then. there is no difference (in this case, not even a roundoff), so whats the mather? and if one of the ops is one, you're allowed to directly return the other op, instead of calculate *1.
this is about what this algo does (except, more complex, much more clever, and with a lot of work behind the scenes, to get it done..).