In article <1278637131.1858.14.camel@jonathan-desktop>, Jonathan Osuch <osuchj@avalon.net> writes:
Do you mean which line in the MandAutoCritInZ formula, or do you mean which line in the parsers?
It could be either way; either we find the offending bit in the formula or in the code. The formula isn't universally offending, because depending on parameter values it usually renders the same on both. Are we just saying "its a precision issue" and throwing up our hands, or are we trying to achieve parity? If the former, then I guess there's no reason to continue the conversation; if the latter, then we should try to find out where/when we need more precision in the "C" code and go to bignums.
The parsers inherently operate at different precisions and when the level of zoom is high enough or the complexity of the calculations is high, there are going to be differences in the images generated.
I would have thought that bignums would kick in if it was a zoom issue. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/> Legalize Adulthood! <http://legalizeadulthood.wordpress.com>