Quote .. Apophysis ... It's almost there! A brand new version of Apophysis will be released in a minutes (or days ;) ) ... There's lot of new stuff in it - as always new variations, some of them are non-fractal anymore, giving you new possibilities; the mapping transform called here FinalXForm - having a major influence to your creations; some really cool new editor features, bugfixes, etc. :D ..
Furthermore, flam3 developers got all those new variations into the newest flam3 release (2.7), so it will be synchronised with our beloved tool :) ... On the other side we have put into Apophysis some newest flam3-render control parameters, such as Density Estimator and Gamma Treshold, so one can easily render their Apophysis flames with flam3 without bothering editing a source file for this flame :D
I hope all of you will be happy with this new version!
The kind folks at flam3 .. as mentioned above .. check the download page .. (set the renderer as a replacement "export flame" using the "paths" tab of the "options" screen .. replacing HQI
Boy, am I way behind. My computer has taken a disliking to apophysis recently. Whenever i try to render anything, one of the fans in my pc starts working overtime. Not a pleasent sound, any ideas?
Thanks for the info though, very interesting. May prove useful in a fanless future:)
I shall certainly give that a go. I've had the casing off once already to clean all that strange fluff stuff that builds up. At the very least it will tell me who the culprit is.
Hmm, I am curious ... just downloaded the new one and the file seemed awfully small, only 1.17 megs. Any idea ... wait one sec. ... (oh, and for us IE people we still ... or at least I had to ... may have to choose another mirror to start the download and depending on your security settings, one more clicky thing to start the d/l ... just an f.y.i.) ... uhm, nvm ... *he said sheepishly after checking previous version sizes*
I took a look at the test render you offered up and I didn't recognize any of it as being Apophysis, had me thinking maybe the new version had gone in a new direction.
Thank you for your time ... I am done now ... I think ... *ponders a bit* ... now I am done. :o)
actually .. what I recommend is to download the "original" apophysis 2.02 from Mark Townsend ... it has an "installer" (if I remember correctly) .. and will set up folders for scripts (most of which are obsolete due to it being capped at 12 triangles and the newer versions using up to 100) .. but .. it sets the folders up for you .. like parameters .. etc
the versions from Utak3r and Zueuk are just an executable file (apo.exe) .. so .. just replace your apo2.02.exe with the newer versions
download the updated scripts .. HERE .. don't delete the original scripts until you try them .. the problem is .. because apo2.02 only used 12 transforms the scripts generally say "add maximum transforms" and that is now 100 ... this usually renders your image as a distant star field
but not all scripts do this .. like "make bilateral" .. which just mirrors your flame with itself .. and is quite handy if you like that
and .. the new version HAS gone in a new direction ... not too late for YOU to emerge as the apo guru, assisting the neophyte grasshoppers walk the rice paper
show me, again, the hot-coal-induced tattoos on your forearms .. I NEVER tire of seeing them
Yeah, found out about Apop 2.02 at least behaving somewhat more like a normal install through some Apop misadventures with 2.03c. Question though ... do you see no need or use for keeping the 2.02 executable hanging around?
If I follow what you are suggesting, and to me it seems that you are indeed suggesting to go into the Apop 2.02 program folder and copy over the 2.02 exe with the newer version. Effectively wiping the folder clean of any remnants of the 2.02 exe file.
I do get that by using the 2.02 program folder and its' subfolders, it will be nicely setup for other scripts and such, with folders already in place. Which would be a blessing and save me some time from having to navigate through levels of folders and and ... to get to the new scripts.
'K, I was going to PM you these questions and considerations, but, I think maybe there might be some who could benefit from this discusssion.
Thanks for your time, I really appreciate it.
Oh, and those hot-coal-induced tattoos on my forearms? ... they actually came from lifting my tower while I was trying to render a flame ... a rather deep, deep, deep zoom with an oversample setting of 1,000,002 ... so that even my pc fans could not keep the searing heat emanating from my graphics card spreading to the sides of my tower.
I suppose some Asian lettering would have been cooler to that of "Antec." :oP
No .. I'm not really suggesting that .. you can, of course, lose it if you want ... I have had stability issues with the Utak3r-Zueuk, et al, releases .. and I alone, apparently ... Hard lockups, BSOD's requiring a reboot ... so, therefore 202 still occupies a place in my heart
What "I" do is make a folder for each release labeled, for example, Apophysis-204b ... and then just change where my shortcut points to ... or .. I right-click on the executable and choose "Pin to Start Menu" ... and it shows up in the short list of programs there
I also SAVE all parameters from a given release to a FAV's file with the version # .. because, as they add features, those features won't be supported by older versions
so .. Sorry for any confusion (*he says sheepishly*)
You can, of course, re-lable the original to Apophysis_v2.02.exe ... you're bound to have a favorite version as they continue to move forward and do things that you may not agree with .. for example .. I used to use FLAM3 as my export renderer .. I can't get it to work NOW, even though I have the most recent, as they suggest
I still haven't figured out some (read = ALL) of the new stuff
I have a habit of leaving my computer on & Apophysis open for several days at a time. Which was never a problem until recently, but this morning when I got up I noticed for the second time Apophysis 2.04beta had closed itself down. Luckily I had saved a couple parameters, but I still wanted to work on what was on my screen....& no, I didn't save that one.
Has anyone else noticed this happening to them ?
as you may know .. apo crashes my computer frequently .. and I rarely use it anymore .. most of my crashes are hard lock-ups where mouse movement is only a distant memory .. and the BSOD's made famous by windows 1.0
I can almost say that apo is the only thing that crashes my machine with THAT kind of chutzpah
but .. I think I remember it just winking off quickly with out saying buh, bye
the built in renderer is supposedly "render to disk" .. which usually means you can resume a render .. (at least you can in Ultra-Fractal) .. so, maybe if the machine hasn't been turned off or re-booted .. it could be resumed .. (don't hold your breath)
The problem was I wasn't rendering anything then...just hanging onto the variation I was currently playing around with. The darn thing must time out, is that right ? Never had this problem with 2.03c .....*grumble*
Thanks though Keith .. :o)
as you may know .. the Apo of U+Z fame is the red-headed stepchild of our software libraries
you just want to smack the precocious little twit .. more than you want to hug it
I guess I should have prefaced that with .. In My Humble Opinion .. or .. Speaking For Myself
PS .. did you test render what you lost at all .. because the prog saves all renders to a .flame file somewhere .. I've salvaged a couple that way .. (for some reason if you changed gradients several times these changes aren't saved .. you'll have 6 of the same thing)
No, I almost never do test renders ...just render them to see what to see....I usually play with gradients first or any other tweaking that needs to be done.
But this is the second time the darn thing has closed up shop on me.....before I was done browsing too !
Update .. scroll down to April 20
`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·
From Utak3r's Journal (04-14-06)
`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·
Quote .. Apophysis ... It's almost there! A brand new version of Apophysis will be released in a minutes (or days ;) ) ... There's lot of new stuff in it - as always new variations, some of them are non-fractal anymore, giving you new possibilities; the mapping transform called here FinalXForm - having a major influence to your creations; some really cool new editor features, bugfixes, etc. :D ..
Furthermore, flam3 developers got all those new variations into the newest flam3 release (2.7), so it will be synchronised with our beloved tool :) ... On the other side we have put into Apophysis some newest flam3-render control parameters, such as Density Estimator and Gamma Treshold, so one can easily render their Apophysis flames with flam3 without bothering editing a source file for this flame :D
I hope all of you will be happy with this new version!
`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·
Some links .. for those interested
The kind folks at flam3 .. as mentioned above .. check the download page .. (set the renderer as a replacement "export flame" using the "paths" tab of the "options" screen .. replacing HQI
an example of Final-X-Form .. mentioned above
an example of Perspective mapping
an example of Juliascope
an example of Another Test render using 2.03d
a fixed script .. pbAnimate .. for those that may use it
`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·`·.¸¸.·´´¯`··._.·
my name is keifer .. and I approved this message