FA+
Shop
194
Views
Views
2
Favorites
Favorites
Category
Artwork (Digital) / Abstract
Species Unspecified / Any
Size 1018 x 673
File Size 992.8 kB
Report this content
More from Spykr
An older one of my fractals uploaded as a sort of "sorry" for not being able to get the super-mega-render fractal up.
Done in apophysis 2.02 in February 2010. Took under an hour. I really like the how the color works in this one as well as the sense of movement there is.
Apophysis 2.02
Oh by the way, here's proof of the render: http://i285.photobucket.com/albums/.....g?t=1291512584 I took a screenshot yesterday to document its progress.
Done in apophysis 2.02 in February 2010. Took under an hour. I really like the how the color works in this one as well as the sense of movement there is.
Apophysis 2.02
Oh by the way, here's proof of the render: http://i285.photobucket.com/albums/.....g?t=1291512584 I took a screenshot yesterday to document its progress.
Category Artwork (Digital) / Abstract
Species Unspecified / Any
Size 1018 x 673px
File Size 992.8 kB
As I said, I did this about 10 months ago. I was just starting to use apophysis again. I didn't know there were newer, beta versions.
I haven't touched the 3d hack versions. I work in v2.09, if 2.10 were out I'd be using it. I think they're working on 2.09 beta 2 right now.
I haven't touched the 3d hack versions. I work in v2.09, if 2.10 were out I'd be using it. I think they're working on 2.09 beta 2 right now.
Ok then. Prepare for the long answer! (Decimals have been rounded. Answer may contain some bullshit here and there)
Rendering an image in apophysis works more or less like this: the low-quality 512X484 image as seen in the program is saved onto the computer's hard drive. To do that it must convert the .FLAME file to a .png file, adjust the resolution, re-size the image, move around pixels to fit that size, and drastically boost the number of pixels per inch. In a normal render I take the 512x484 image and double its size to 1024X768. The 512x484 image contains 247,808 pixels. The 1024x768 final render contains... wait for it...786,432 pixels. That's around triple the number of pixels. In this case, I was zoomed into a very small area that was maybe 25x25 pixels, only 625 pixels, the final image would have contained 1,258 times the number of pixels. So, in short, the reason the render took so long is because it had to take a very small thing, greatly increase it in size, vastly increase the resolution, and reorganize the little dots of color to make the pattern correct in the larger size.
There ya go.
Rendering an image in apophysis works more or less like this: the low-quality 512X484 image as seen in the program is saved onto the computer's hard drive. To do that it must convert the .FLAME file to a .png file, adjust the resolution, re-size the image, move around pixels to fit that size, and drastically boost the number of pixels per inch. In a normal render I take the 512x484 image and double its size to 1024X768. The 512x484 image contains 247,808 pixels. The 1024x768 final render contains... wait for it...786,432 pixels. That's around triple the number of pixels. In this case, I was zoomed into a very small area that was maybe 25x25 pixels, only 625 pixels, the final image would have contained 1,258 times the number of pixels. So, in short, the reason the render took so long is because it had to take a very small thing, greatly increase it in size, vastly increase the resolution, and reorganize the little dots of color to make the pattern correct in the larger size.
There ya go.
Comments