In article <000d01cb4f9c$7ec19760$4001a8c0@lan>, "Gerald K. Dobiasovsky" <gerald.dob@aon.at> writes:
From: "Richard" Sent: Wednesday, September 08, 2010 7:42 AM
Weird! I wonder if this is a bug in fractint?
For what it's worth, the .GIF itself contains a reference to EpsilonCrossJ.
Opening it in Fractint (ver. 20.04 patch 9) shows the EpsilonCrossJ formula on the bottom of the 'z' screen (the input screen for fractal specifics), and writing a .par entry from this also has "formula=EpsilonCrossJ".
OK, this tells me that its just a typo in the posting to the mailing list. These are early parsets when Roger was still working out his posting style :-).
Mind you, this is DOS Fractint on a MS-DOS 6.22 partition.
Yeah, but that particular code should be OK compared to xfractint. There's no assembly in there and its all relatively portable C. I will check the GIF on my Windows port when I get home though to make sure. The Windows port is closer to xfractint than the DOS code.
BTW, I checked the "noise!" .par you asked about in the Fractdev list: Again .par and .gif work normally (loaded the .gif and changed the resolution to force Fractint to redrawing the image). Everything worked ok.
But again, this is DOS Fractint in its native environment.
Yeah, I expected that one to be fine in DOS. However, when I rendered it on xfractint I got a black screen that took 5 minutes to render. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/> Legalize Adulthood! <http://legalizeadulthood.wordpress.com>