Thanks to all the people that apparently stay up all night working on fractals I can be more specific. The size of a GIF picture is the four bytes immediately after the GIF89a. If the picture was done and saved in the preview in V mode the size that shows is the actual size of the picture and the viewing program puts it where it wants to on the screen. Here is the problem I am seeing with Fractint 99. Using R to display an old 640 by 480 file the a line on the mode select screen says nonstandard aspect ratio. Then selecting the 640X480 GDI mode and the screen showing warning about the v mode shows up. Proceed and the picture fills the window. Save this and the new file still shows as 640X480. Do a routine mandelbrot scan and the x axis is obviously squashed. Save this and the picture is still 640X480. Because Fractint 99 can't cope with the v mode I am at a loss as to where to look next. Charles
In article <45F2E2CD.9090103@thuntek.net>, "Lee H. Skinner" <skinner@thuntek.net> writes:
What is Fractint 99?? I know of no such version!
He's talking about one of the betas which are arbitrarily labelled 20.99 patch level N. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>
Charles F Crocker wrote:
Using R to display an old 640 by 480 file the [WARNING] line on the mode select screen says "non-standard aspect ratio; loading will change...". Then selecting the 640X480 GDI mode and the screen showing warning about the v mode shows up.
The way that the BETA version was distributed no longer matches all of the prior versions when it comes to video modes. Try comparing any of the older FRACTINT.CFG files with the one that was sent out with the BETA release. The Disk Video selections should never have been established with the SF# key choices. It would have been better to use the CF# and AF# key selections. Also, when using the <v> mode to get to the "View Window Options" screen, you will probably notice that the Zoombox scrolling value is incorrect, when it should have a choice of either "f" (fixed) or "r" (relaxed). And if you try to even tab down into that field, FractInt will crash with an "Unexpected Error". Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/
These issues are fixed in the next beta, but it probably won't be for a few weeks. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>
In article <1173559363.3991.7.camel@linux.site>, Jonathan Osuch <osuchj@avalon.net> writes:
These issues are fixed in the next beta, but it probably won't be for a few weeks.
Is there a reason you are keeping the virtual screen prompts on the View Window screen?
I'm not sure I understand the question. As a guess I would imagine that my attempt to change the default aspecct ratio to 1.0 resulted in this as a side-effect. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>
Rich,
Is there a reason you are keeping the virtual screen prompts on the View Window screen?
I'm not sure I understand the question. As a guess I would imagine that my attempt to change the default aspecct ratio to 1.0 resulted in this as a side-effect.
If you look at line 796 in the version of prompts2.c in HEAD, you'll see the line: if (virtual && dotmode == 28) { Everything from this line to the matching brace should be deleted since virtual screens were meant as a way for the DOS version to handle images larger than the physical screen. Another problem I've seen is that when a GIF is restored that was created in integer mode, you end up in an infinite loop when you change something that regenerates the image. I did this with the View Window screen when changing from a small image to a full screen image. Pressing <F> a couple of times also causes the hang. Yes, I'm using the latest CVS source. Jonathan
In article <1173561804.3991.17.camel@linux.site>, Jonathan Osuch <osuchj@avalon.net> writes:
Another problem I've seen is that when a GIF is restored that was created in integer mode, you end up in an infinite loop when you change something that regenerates the image.
This is an incentive for someone to port the integer fractal compute code from 16-bit assembly to 32-bit inline assembly :-) -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>
On Saturday 10 March 2007 19:58, Paul N. Lee wrote:
Also, when using the <v> mode to get to the "View Window Options" screen, you will probably notice that the Zoombox scrolling value is incorrect, when it should have a choice of either "f" (fixed) or "r" (relaxed). And if you try to even tab down into that field, FractInt will crash with an "Unexpected Error".
interesting, this made me look at the options under the v menu again and i see one can change the pixel dimension of the image but that this does not resize the display window, one would still have to drag it large enough for larger renders, or is there a way around that ? sammi
On Mon, 2007-03-12 at 14:43 +0000, sam ende wrote:
Also, when using the <v> mode to get to the "View Window Options" screen, you will probably notice that the Zoombox scrolling value is incorrect, when it should have a choice of either "f" (fixed) or "r" (relaxed). And if you try to even tab down into that field, FractInt will crash with an "Unexpected Error".
interesting, this made me look at the options under the v menu again and i see one can change the pixel dimension of the image but that this does not resize the display window, one would still have to drag it large enough for larger renders, or is there a way around that ?
Resizing the image from the View Window screen should only work when using a disk video mode when using Fractint for Windows. This will be fixed in the next beta version. Jonathan
participants (6)
-
Charles F Crocker -
Jonathan Osuch -
Lee H. Skinner -
Paul N. Lee -
Richard -
sam ende