Apophysis 7x is an improved version of the famous fractal flame editor Apophysis which is used by artists all over
the world to generate stunning abstract images and cosmic animations. Apophysis is based on an algorithm introduced
by Scott Draves. Apophysis 7x got the following improvements against the original version:
- Flame thumbnails
- Missing plugin and parsing error detection
- Improved 3D fractal flames
- Dozens of variations included
- An easy-to-use template system to get you started fast
- Revamped user interface to allow it integrate into the beautiful modern windows shells
- Numerous smaller enhancements such as hiding unused variations and variables as well as naming transforms or searching for variations
- Autosave functionality
- Warnings about potential memory overflows
- Windows 7 Shell Integration
- Multi-language support - now with UTF-8 support
- DirectColor technology to enable variations to color your fractal
- Color curves editor to fine-tune the colors of your fractal professionally
- 64 bit-version
Why was it written?
Apophysis 7x started out as a simple modification of Apophysis 3D which was refreshing the user
interface into a more modern look. On popular demand, multiple versions evolved through fixing bugs from both, the
original version and Apophysis 7x. Over the time, the project was focused on adding more features and continuing the
improvement of the code stability.
Multi-language support?
Yes! Since version 15, Apophysis 7x offers a multilingual user interface. That was done so new users could fit into
this rather complicated program more easily through not having to translate everything in their mother language.
The language format is open (XML) so everybody can easily add more languages. Apophysis 7x uses Delphi XE2 as it's compiler which enables users to add even non-western languages to the repository since the whole code has been updated to use UTF-8 as the primary encoding.
64 bit?
Yes! Since version 15c, Apophysis 7x uses Delphi XE2 which allows the compilation of a 64 bit-version. However, plugins and scripts are not supported in the 64 bit-version as now now. But there is no memory limit anymore.
What do I need?
All you need is a Microsoft Windows operating system (XP at least). To use the Windows 7 shell integration, you
need Windows 7 of course. If you want to run Apophysis 7x on Linux or MacOS, you need at least WINE 1.2.x. To
use the 64 bit-version, you need a 64 bit processor and a 64 bit operating system.
Is it expensive?
Apophysis 7x is free, open-source software. That means, it does not cost you a cent. In addition, everyone is able
to change the software using the available source code.
How to install?
Get the download package and extract the ZIP archive to the installation folder. After that, you can execute Apophysis7X.exe or Apophysis7X64.exe right away!
If you are on Linux or MacOS, you need to start Apophysis7X.exe or Apophysis7X64.exe using WINE. Be aware that not all features might be supported when executing Apophysis 7x on Linux- or MacOS-systems. 64 bit support depends on whether WINE offers it.
An installer version for Windows-systems is available. There is no package manager-file or DMG-file for Linux or MacOS at the moment.
Credits
Kudos to the translators:
Also to the original Apophysis developers: Peter Sbodnov,
Piotr Borys, Roland Hordijk and Mark Townsend.
Apophysis 7x was written in 2009 by Georg Kiehne.
The original source code repository (CVS) is located on SourceForge.
The official website of Apophysis is located on apophysis.org.
Big thanks to the great folks on deviantART, who helped finding bugs and
developing new ideas. Also visit the Aposhack chat room (login required)
to chat with other Apophysis users, participate in live tutorials and share parameters.
Languages
- German
- Italian
- Chinese
- French
- Czech
- Dutch (work in progress)
- Indonesian (w.i.p.)
- Spanish (work in progress)
- Polish (work in progress)
- Turkish (work in progress)
- Slovak (work in progress)
- Danish (work in progress)
If you are into programming or you want to create resources like translations for Apophysis, you may want to look into one of the following resources:
Version 7x.15c -
Download
- Added loc, polar2, cross, wedge, epispiral, (pre-/post-)bwraps, (pre-/post-)falloff2, blur_circle, blur_zoom, blur_pixelize, splits, separation, bipolar, loonie, escher, scry, ngon, foci, lazysusan, mobius, (pre-/post-)crop, elliptic, waves2, auger, pre_spherical, pre_sinusoidal, pre_disc and post_curl-variations
- Changed all variations which were in Apophysis before so that they are 3D-aware. This means that all variations PRESERVE the z-position of their points instead of resetting it to zero like before. Your 3D parameters likely need tweaking HOWEVER I added some code in the loader which should automatically "fix" most of the parameters. BE AWARE THAT PARAMETERS SAVED WITH 7X ARE LIKELY TO BE INCOMPATIBLE WITH THE 3D HACK FROM NOW ON!
- Added a variation search box in the editor
- Added possibility to specify custom plugin path
- Added color curves tab in the adjustment window
- Fixed the multithreaded renderer. It is now safe to enable multithreading in the options. Leave a few threads open, however. If you got a dual-core, leave it at 1; if you got a quad-core, set it to 2-3; and so on.
- Changed the general buffer depth to 32 bit floating point in the 32 bit version and 64 bit floating point in the 64 bit version to improve numeric accurancy and speed (less conversion)
- Removed the EXIF-writing for JPEG-renders (couldn't find up-to-date and free library)
- Introduced an experimental 64 bit version with no plugin support (which is why I added so many variations) and no scripting support as of now (waiting for TMS Software to add 64 bit support to Scripter Studio)
- Fixed the editor toolbar glitch
- Fixed MT renderer not recognizing the transform opacity value
- Updated string handling to UTF-8 encoding
- Removed the T-500 version and the separate executable for the lite-version. You can run the lite version with the command-line switch "-lite" now
Version 7x.15b -
Download
- Fixed DPI glitches in "Export UPR", "Gradient Browser" and "Message Log" windows.
- Fixed a bug which made it impossible to render in slices due to "Out of Memory" errors.
- Fixed a bug which caused wrong thumbnails after deleting a flame from the list to the left in the main window.
- Updated Chaotica integration. Only versions since V0.45 of Chaotica are supported now. Directory structure is significant.
- Added optional editor background preview. It is off by default. When on, the mini preview in the editor is replaced by the flame drawn on the background.
- All buffer depths except 32 bit integer have been removed. A proper 64 bit-renderer shall be re-introduced in V16 where the only number type will be float.
- Fixed a bug which caused improper listing of used variations from the final transform in the "Summarize flame" feature and the variation enumeration for Chaotica.
- Added a link to Tara Roys' Apophysis manual in the help menu.
- Added experimental thumbnail embedding - default is off since it has no real-world use right now
- Added a better notification system for missing plugins
- Added options to toggle thumbnail embedding and missing plugin warnings on/off
- Added background features to support dynamic plugin loading/unloading as well
- Added a (disabled yet) module to load the new and old parameter format - the old parameter format is still used solely in this version
- Added multilanguage support so users can write their own translation files for their native languages using a text-editor
- Added an option to generate a quick flame report
- Added built-in Chaotica export functionality
- Changed resize code in editor window to allow users setting higher font sizes in their system without the editor being messed up
- Changed most parts of the GUI to allow dynamic strings being placed in while loading translation files
- Changed thumbnail code to allow non-square thumbnails (maintains original aspect ratio)
- Changed thumbnail loading code to be threaded (loading in background)
- Changed loading progress bar in main window to be at the status panel (was on the image frame)
- Changed default flame list size to make the thumbnails appear centered
- Changed "Export flame" to "Export to flam3" in order to better integrate the new Chaotica support
- Fixed a bug with the time-attribute on unnamed flames ('' is not a valid integer)
- Fixed assembly code for some built-in variations
- Fixed a bug where the system shut down after first flame when rendering all flames if shutdown option was enabled
- Fixed a bug where the options window was always nagging the user with restart
- Fixed Flame.GammaThreshold in the scripting system - it now reads and writes like the option in the adjust window (please edit your scripts)
- Fixed the internal script-from-flame feature which placed weight modifier settings at the wrong place resulting in the flame being inaccurate when using Xaos
- Fixed a memory leak within the thumbnail generation code.
- Merged the Apophysis7X/DC-branch into the main code. DirectColoring is now generally available for Apophysis 7X.
- Added a transform property named "var_color" which blends DirectColoring for an individual transform between zero (off) and one (on) - you can access this feature on the color-tab in the editor window. (captioned "Direct color")
- Added script support for var_color. (access with "Transform.VarColor")
- Added descriptive icons in the variation lost of the editor which indicate whether the individual variation supports 3D or DC.
- Fixed the "multithreading"-glitch in the options window. The field now represents the actual setting again.
- If you hover a triangle in the editor, the text on the bottom right now also contains the variation weights for each variation applied.
- Added dc_linear, dc_bubble and dc_carped as optional plugins to the installer. All of these support DirectColoring.
- Fixed a bug which prevented the mouse cursors from changing when hovering a transform "widget" in the editor window.
- Changed the script procedure "ShowStatus([string])" so it now displays a status message again in the first panel of the main status bar.
- Rotating the gradient using a drag operation on the gradient display now updates the value text box.
- Fixed some random weirdness within the built-in curl- and curl3D-variations.
- Enabled the "Opacity" field in the editor to react on double clicks. (changes to zero if opacity is set to one, elsewise to one)
- Fixed a bug which could made the script system unable to change the transform data after using an AddTransform-command in some very rare cases.
- Made some "cosmetic" changes to the application icon and title string.
- Changed the guidelines notice in the options window as it is indeed possible to show them when transparency is not enabled in the main preview.
- Fixed numerous "Floating point"-errors in the 32- and 48-bit renderer code.
- Added an enumeration of scripts within the "[ApoDirectory]\Scripts" folder. This enumeration is shown in the scripts menu to quick-access your script library.
- "GammaTreshold" is now accessible in scripts. ("Flame.GammaTreshold := value")
- You can now also use "ColorSpeed" to access the symmetry property in scripts. ("Transform.ColorSpeed := value")
- Added functionality to turn a given flame into a script which reproduces the flame except of its gradient.
- Renamed "randFilename" to "Apophysis7X.rand" (was "apophysis.rand"), "undoFilename" to "Apophysis7X.undo" (was "apophysis.undo") and "templateFilename" to "Apophysis7X.temp" (was "default.temp")
- You can now specify a script which executes automatically when Apophysis starts. You have to name this file "autoexec.asc" and it must be in the Apophysis directory.
- The plugin selection in the installer was simplified to groups rather than individual plugins.
- The installer contains the official plugin pack from SourceForge now.
- The default scripts from Apo2.02 were replaced by a smaller set of example scripts. These remain optional and can be selected in the installer.
- The default path of the function library is now [ApoDirectory]\functions.asc (moved out of the scripts folder as it will be enumerated in the program)
- Changed the plugin enumeration code so that the plugins folder must now be at the location of the EXE-file rather than the location specified by the "Work Directory"-variable (CDIR)
- Added file type registration of .flam and .asc files to the installer so they open with Apo7X on double-click and assigned an icon to them (located at [ApoDirectory]\Resources\*.ico) - flames are simply being opened and displayed, scripts are opened and the script editor is shown.
- Template files (.template) got a file type registration as well. Double-clicking those will start a new tool which installs them into the correct directory. This tool works with the following command line: "resinstall.exe template [file name]". If you want to use this install tool separately, replace "file name" with the source path of the template pack wrapped in quotes (usually you don't need to do that)
- Disabled the (unfunctional yet) distance estimation tab in the adjust-window as this feature is still not ready in this release (sorry...)
- When clicking "save all parameters" in the file menu after editing one flame in a batch, the changes were reverted and the target file did not appear in the file system. This has been fixed.
- Included a new and recent help file as the previous versions were still using an ancient version from Apophysis 2.02. The new help file is way more detailed and should cover (almost) every recent feature of Apophysis 7X.
- Enabled the renderer to write EXIF-data in JPEG files. This feature is optional. If it is enabled, Flame name, Apophysis version and optionally a custom author string and the corresponding parameters are written into the metatags of the JPEG render. This data will remain if you postwork your render in Photoshop.
- Added optional guidelines in the main window preview panel (originally appeared in Jed Kelseys Apo2.09 JK)
- Added functionality to change help file path (so you can insert the tutorial of your choice)
- Changed the entry "The fractal flame algorithm" in the help menu to open the following document in your default browser:
http://www.flam3.com/flame_draves.pdf
- The plugin code had some little burps. Fixed these
- You can now distinguish whether you started the normal or the T500-version from the titlebar text
- Following the 2.09 update, I've renamed the "symmetry" parameter to "color speed" to avoid any confusion among the new users
- Finally implemented the "transform opacity" option from 2.09 replacing the older "plotmode" a.k.a. "invisibility" parameter. It also can be scripted
- Apophysis 7X can now autosave in 1, 2, 5 and 10 minute intervals! You can set the autosave target as well as the interval in the option dialog. This is also the place where you enable and disable it
- Added a "T500" version which can handle up to 500 transforms
- Prepared the code for density estimation. It is an inactive feature yet but I try to finish it as soon as possible to help you kill the grain
- Performed tiny little fixes all over the code
- Added copy and paste buttons in editor toolbar
- Added value textbox and reset button in gradient adjustment window
- Moved "Add linked XForm" button to the end of toolbar in editor window
- Gradient now randomized when a new flame is created from template
- Fixed the issue where the render dialog did not properly pass the default file extension to the Commdlg32-library (always ".bmp" extension selected)
- Fixed a bug which caused some variables to reset when duplicating an XForm
- Changed the toolbar routine back to fixed layout on popular demand
- Removed the update feature (the application connecting to the internet is reason of concern amonst a lot of people)
- Reverted the plugin code to 7X.8 state (the most stable version)
- Removed countless smaller bugs
- Added functionality to check for updates on startup
- Added "opacity" tag in XML parser to make flames compatible to official 2.09 version of Apophysis
- Added "Reset file content list width" button in options menu
- Added possibility to set a name for an XForm
- Improved update system to get the list of changes visible in the program
- Fixed a bug where the color box in post render window did not react on clicks
- Added "create linked xform" button in editor toolbar
- Fixed loading glitch in template system
- Fixed a bug where the "open" dialogs have a "save" button instead of an "open" one
- Removed confirm box when selecting .flame file in the "Save flame" dialog
- Added template system
- Moved weight box below transform selection in editor
- Changed open/save file dialogs to those natively offered by OS
- Added possibility to remember last open flame file
- Added possibility to change thumbnail size out of small (96x96) and large (128x128)
- Replaced main toolbar component to make sub-toolbars able to be reordered
- Fixed OnClick procedure in editor's color bar
- Fixed a bug causing "Invalid ImageList Index" when deleting flame in classic list view mode
- Added "New flame" and "Render all" buttons in main toolbar
- Added progress bar for preview rendering
- Added gradient display bar in editor's color tab
- Added a button to clear out variations in editor's variation tab
- Added a "Go to folder" button in render window
- Moved "Options" button in main toolbar
- Resized quality box in main toolbar
- Resized thumbnails to 96x96 pixels
- Made "hide unused variables" default
- Changed main toolbar to wrap when window is too small
- Made variation names case-insensitive in scripts
- Made color box in editor react on clicks again
- Fixed background color box in options window
- Fixed a bug which caused "Access violation" error when deleting a flame
- Fixed a bug which caused the clear-out of "renders3D.flame"
- Fixed a bug which caused editor background being white when there are no registry settings yet
- Fixed a bug which made the paste feature malfunctioning and giving "Cannot open clipboard" error sometimes
- Fixed a bug where the script engine did not translate from radians to angle and vice versa when using Flame.Pitch or Flame.Yaw
- Renamed "renders3D.flame" to "renders7X.flame"
- Added security checks to avoid "List Index out of Bounds" error on several places
- Changed thumbnail feature to be disabled by default
- Added possibility to check for updates within Apophysis
- Added possibility to hide unused variations and variables
- Added loading progress bar and decreased thumbnail quality for faster loading
- Re-enabled export flame feature
- Fixed the batch render function
Is there a beginners tutorial?
There are many of them. Just browse here
or here.
A few recommended tutorials are here:
Where can I find flamepacks/scripts?
You can find them here and
here.
How can I make animations?
You can either use the script Apophymator
or flam3. Please check the corresponding documentations to learn
how they work.
I have changed the font size (DPI) setting in Windows and now my editor window / script dialogs
are messed up. What should I do?
Apophysis does not support changed font sizes fully. Version 15 addressed some changes in the editor
window but there still may be problems. Please use the default font size for Apophysis.
Apophysis crashes on start with XML errors. What is going wrong?
Most likely, you have installed a language file and this file is corrupt or faulty. Please try
re-downloading said file and if there are still problems, disable the use of a language file
in the options or remove your settings like described here.
I have a beast of a computer. Why does Apophysis still run slow and/or tells me that there is not
enough memory sometimes?
Apophysis is a very old application. It was created, developed and tested on 32-bit (x86) computers
and had it's first users on Windows 95/98. Apophysis is unable to use more than 3GB of RAM except if you use the new 64 bit version (but this one doesn't support plugins)
Plugins
How do you get a plugin to work?
You must create a folder at the install location named "Plugins" and move the downloaded .dll
files in there (the .c files are not for end-users but for developers - ignore them if you don't
need them)
Where can I find plugins?
Plugins can be found here.
There are also plugins listed in the Fractal-Resources
and Apophysis-Plugins groups on deviantART. The
most popular choice is the
Aposhack all-in-one plugin pack - but beware! Do not install all plugins at once. Apophysis can
only handle a specific amount of plugins at a time depending on the amount of system memory (RAM) you
have installed. If you get error messages, remove some plugins and try starting Apophysis again. The 64 bit version can not load plugins.
When I open Apophysis I get an error message "access violation at address [...] in module [...]. Write
of address [...]" How can I fix that?
Most likely, you have too many plugins installed. Try removing some first. If that does not work, try
resetting your settings:
- Click Start/Run or hit Windows+R
- Type "regedit" and click OK
- In the left area of the now opened window, browse to "HKEY_CURRENT_USER", then to "Software"
- If you are using Apophysis 2.x, 3D or JK, delete the item "Apophysis 2.0" by clicking it and
pressing "delete" on your keyboard. If you are using Apophysis 7x, delete "Apophysis 7x".
- Close the window and try starting Apophysis again
If nothing of that helps, backup your flames, delete the Apophysis folder (and all settings as shown above)
and download and install the most recent version of Apophysis.
Flames
How can I make a flamepack? How can I save more than one parameter per file?
Apophysis generally saves flames in .flame files, which are actually collections of fractal flames.
If you click the "Save" button in the toolbar, a dialog opens. The field on the top is the path of your flamepack.
The field on the bottom is the name of the flame within the flamepack.
What's the maximum number of transforms I can use for a flame?
Generally 100. Apophysis 7x, however, has an additional version: the "lite" version, which allows only 50
transforms to save memory.
When I try to load flames/parameters I get a error message saying "Error: no colours in palette". How can I
fix that?
Your flame is likely corrupted. Apophysis saves a backup whenever it adds or removes a fractal flame into or
from a flamepack. Restore the last backup named "(your flame file name).bak".
Apophysis did not save my flame file (without an error message) - what happened?
Most likely, you have illegal characters in the save path. Please double-check the file name you want to save
the flame to and also check the flame title for these chars: / : " ? * |
Scripts
How do I run a script?
In Apophysis, click "Script" in the main menu, then "Open...". Select the script file you have downloaded
or saved and click "Open" in the dialog. Then just hit "F9" on your keyboard. There is no script support in the 64 bit version at the moment.
Is there a tutorial about writing scripts?
There is a scripting reference manual
written by the community. Also, datagram wrote an excellent
scripting tutorial.
Rendering
How can I render my flame?
By just hitting Ctrl+R in Apophysis. When you have done that, a window opens where you can adjust settings
like image size, render quality and target file. Click "Start" when you are ready and then be patient!
Why do I get a transparent background?
You have chosen PNG as the output format. If you do not want transparent backgrounds, click "Options" in the
main menu, then "Options" again. On the "General"-tab at "PNG Transparency", check "Disabled" and click OK.
Alternatively, you can just render as BMP or JPEG (which do not support transparency)
Which are the optimal settings for a render? How can I get rid of the grain?
Usually, setting "Quality" to 4000, "Filter Radius" to 0.7 and "Oversample" to 2 is okay. If you want to
render prints, however, consider higher settings. An image size of 1024 in width is okay for web images.
For prints, calculate the size the following way:
print_size = web_size * desired_dpi / 96
So for example, if you want to render a 3000x2000 image at 300 DPI, calculate as following:
width = 3000 * 300 / 96, height = 2000 * 300 / 96
Please also consider high oversamples and qualities for prints. If your image still contains grain, increase
the quality again.
Can I continue using Apophysis while running a render?
Yes, if you got a relatively modern PC.
How many renders can I run in the same time?
This depends on your processor (CPU) power. It is not recommended to start three or more render processes at
once, however.
Can I only render to PNG format?
No. The format is decided by the file extensions you give in the "target" field. Allthough, only PNG supports
transparency.
What effect does oversampling actually have on the quality of the image?
Oversampling effectively smoothes out jagged edges. For example, if you render at oversample = 3, the image is
rendered three times the given size, smoothed and then scaled down to the given size.
When I try to render there is an error message "List index out of bounds -1". How can I fix that?
Usually, it is sufficient to restart Apophysis. If that doesn't fix the problem, delete your settings as
described above.