Deviant Login Shop  Join deviantART for FREE Take the Tour
Hey guys :)

I know it's been some time but I'm having hell of a release going on here. So I just didn't came to check on what's wrong with the saving of final transforms. I finally made it so that I'm not there 7am to 10pm every day. This means: it's fixing time.

To provide you with an acceptable solution, I just reverted the behavior of FXes to the one of 15C. So that you at least get to use 64 bit plugins / scripts AND final xforms :lmao:

Here it is:…
It's a patch so just replace the EXE files in your installation. If you didn't update yet, you can with this. In this case, you also just replace the EXE files. Remember the release notes from the original 15D package, though. It contains valuable information on how to use 64 bit plugins and compile multi-architecture plugins (32/64) from existing and new plugin code.

See you soon :)
You might or might not know that I've been fiddling around with Turing McCabe-patterns in the past. Well the good news is: in the present too! For those of you who don't know what this is: it's an algorithm producing nice images like this one:

I've created an explorer utility for myself. Well, I created one for you too but it's old. I'm constantly changing mine and see what you can do with the algorithm. And I've come to a major progress I wanted to share with you.

One thing is a thing you might already know. The original algorithm initializes with a noise field. This means, the first frame is just noise and then the pattern develops. I had one thought which changed that concept a bit: why noise? The Jonathan McCabe seemed to need a field of unstructured data from where a pattern evolves through convolution. My idea was to replace that with something else. To the mathematical idea, an image is sort of unstructured too. It's man-made. Most of the time. So technically, you could use an image to ignite the algorithm. And I did.

The below video shows how that looks like:

Now imagine what it could do to a fractal (flame) rendered into an image file and loaded into the algorithm...!

The second thing was sort of not my idea. I want to say that right away because I was victim to a mistake. When I started to implement this thing, I wasn't aware of that somebody did that before me. I discovered when I was done. But through the fact that there are two independent implementations now, my version and the other author's version are unique in their own ways now. I'm talking about painting into the algorithm's data field using your mouse. Something which provided me HOURS of fun!

My way was to "reset" the areas I was painting on. So basically, wherever your brush strokes the field, there will be noise. It's sort of like you're "stirring" that reactive soup the algorithm paints on your screen. Effectively, you're agitating the algorithm in a limited area.

See how that looks like in the below video:


This gives the whole thing some more interactivity than just dragging sliders and pushing in images. I sort of want to experiment with more ways to influence the algorithm.

I'll keep you up-to-date!
I created another domain for Apophysis 7X. But before you panic: the old domain ( is still reachable and will be reachable :)

The new location is; you can see the main page there. Downloads, history, etc.
Then there is; you can read the current source code online at this location. Live. As I commit it (for example when I fixed a single bug)
And finally (for now) there is; this is the new main bug tracker for Apophysis 7X.

The bug tracker lives on as does the source code. The alternative URLS are:
- for the tracker and

If is not reachable in the next hours, this is because it's still being setup by the provider.

Now that we cleared that up, here comes some very important information! READ UP CAREFULLY!

Since I clearly have less time now but still want to care for and continue Apophysis 7X, we need to make up some rules concerning bug reports. I don't have the time anymore to run between my e-mail inbox, deviantART and Facebook or whatnot to gather all the reports. I need it at a central place. This is said bug tracker!

Only reports in that tracker are being taken care of. It's not that I strictly ignore any report anywhere else but I will oversee them naturally. Don't complain if I didn't read your note or your message on Facebook. I didn't see it. I'm looking into my e-mail inbox like once a day. Apophysis bug reports have a folder there which gets filled by SourceForge. The e-mails you send me directly are drowning in whatever things I get daily. So don't wonder if I don't see them. So please stick to this act of centralization if you want to have your problem fixed or fix it yourself (the source is online)

We need to be prepared for that another developer will either join or take over the project. Thus the outsourcing. Whoever might join or overtake in future will certainly not gain access to my e-mail inbox or deviantART account to see all the bugs you are reporting in your habit. Better switch now :)

The bug tracker acts as my to-do list. It takes too much time to formulate a clear to-do item for every 1000 words-story you sent me via note. Not that I don't appreciate detailed reports but sometimes I just don't need to know that you have X gigabytes of RAM and a spaceship of a GPU (not to speak of that Apo itself gives a crap on your GPU because it's a pure CPU application)

I don't need to announce known problems anymore. You can just check if your problem already exists in the tracker. I won't answer duplicates.

You can observe the bug processing in the source code browser on When I commit a bugfix, I will write the username you wrote your bug report with into the commit comments as a reference. Commits are visible as they are done. If there have been enough commits, a release will be published. Of course, you can always checkout the source code yourself via SVN and build your own release if it's THAT important :lmao:

There are also some simple submission rules which I put in a paste bin and linked on the top of the submission form on the bug tracker page.

Please make sure you include the following information in your artifact:
1) What happens NOW (is-status) and what SHOULD happen (should-status)?
2) How can the I reproduce/provoke the problem you have?
Before you submit a new artifact, make sure:
1) that you have the newest version of Apophysis 7X / 7X64 (remember Hotfix releases)
2) that you are working on Windows XP or higher; Linux or Mac versions are available using WINE but can act strangely
3) that your computer is clean of viruses (of course) and you are not using any desktop enhancement or shell replacement software such as Aston, NextStep or WindowFX
4) that your font size is set to normal in the Windows appearance settings (only for interface related problems)
Bug or feature? An artifact without a should-status can't be processed as I won't know what program behavior you wish for. Maybe you are reporting an error message and it should appear because of another problem in your configuration?

My USB-crystal ball is in the laundry. An artifact without reproduction steps can't be processed as I won't know what you did before the problem occured. What steps were you following in the program before the problem occured?
Avoid unneccessary information. Save me some time by double-checking your settings and making sure that I can see it on my machine! This way, your artifacts will be processed efficiently and fast. If Ineed to know your CPU type, how much RAM and operating system you got and what graphics card you are using, I'll let you know. I don't care if you are an animator, a print artist or a casual playing around. During the bug processing, you are a user. You don't need to tell me that. Be clear and focused. :)

Use english language. I don't care if your grammar is not the best and you misspell words. If I can understand it somehow, it's fine. Google translate is okay too - as long as it's not TOO wild. But avoid writing in french, german, spanish, zulu or whatnot. If you don't speak english then I can't help you. Sorry.

Don't abuse for feature- and change requests. This tracker is about BUGS. You are seeing a bug when the program clearly behaves in another way than it's intented to behave. Sometimes, error messages pop up for a good reason. Your wish that the editor background should be hot pink is a change request, not a bug. So is your wish that you can render exotic image format XYZ with Apophysis is a feature request. But your wish that Apophysis should not open your CD/DVD-drive every time you click on "Render" is a bug report because that is a clear misbehavior.

Don't abuse anonymous reports. You can report bugs without logging into SourceForge (even though you can do so with OpenID, a Google account and whatnot. If I get fishy shit in the tracker, the anonymous reports will be turned off immediately and indiscutably and you will have to log into SourceForge and potentially make an account to be able to report bugs.
Thanks for acknowledging!
To excuse myself from the artificial hoax from earlier, I have a hotfix release for 15C for you ;) Here the changes:

+ Fixed two strings regarding the Chaotica integration. They were always english. The language files have been adjusted accordingly.
+ Fixed the "dot"-bug with the waves2-, noise- and crop-variations (and possibly more) occuring when you use multithreaded rendering. The origin was a structural misconception with the opacity handling. It now works smooth & fine! No corrupted renders in my own tests. If you have some after this release, please report!
+ Added file type registration scripts in the portable (ZIP)-package

Installer (32 bit)

Installer (64 bit)

Portable package (32 & 64 bit)

Source code

A few weeks ago, I quickly coded a small localization helper utility. This to more comfortably edit and merge localizations (language files) for Apophysis 7X. With this utility, you can:

+ Create new localizations from the Apophysis 7X-source code (reads "Core/Translation.pas" from the source code-ZIP)
+ Comfortably edit existing localizations (XML-files)
+ Update existing localizations to the latest Apophysis 7X-source code (more below)
+ Merge a partial localization into an existing localization or save partial localizations (more below)

Here is the download:

Binaries + Source (.NET 3.5 required)

How to...:
  • Create a new localization from the source code?
    1. Download the Apophysis 7x-source code ( or one of the release journals)
    3. Start the localization utility and click File/Create from source code...
    5. Locate the Translation.pas source code file and confirm
    7. Start translating
  • Update an existing localization with the newest source code?
    1. Open the translation in the utility (File/Open language file...)
    3. Click File/Refresh with newest source code...
    5. You will see the untranslated strings in the list on the right. You can either save them as a partial localization (File/Save currently shown strings...) or translate them right away and then save the entire file (File/Save language file)
  • Merge a partial localization into an existing localization
    1. Open the translation file which you want to merge strings into
    3. Click File/Insert partial language file... and locate the partial localization
    5. Confirm. The strings in the main localization will be updated with the strings in the partial localization

Please note: I do not give any guarantee on that this utility works for you. Neither do I give support in any way. Use at your own risk!
The source code as well as the utility is shared under a creative commons-noncommercial license. Look at it, use it, change it, reshare it (under the same terms) but do not make money out of it ;) Simple!
I have made an installer for Apophysis 7X 15C available at

Please be aware that this installer is for Microsoft Windows only. It comes in two versions: for the 32 bit and the 64 bit version of Apophysis 7X 15C. The two versions can be installed side-by-side. Even in a single folder (but be careful - you might not want to uninstall the 32 bit version if you have the 64 bit version in the same folder so I recommend keeping the folders separate)

Unlike for the ZIP-package, 32- and 64 bit version do not come in a single file!

Currently, the german, italian and chinese language packs are shipped with the installer. The other language packs are outdated and for the vanilla version 7x15 only.

The 32 bit-installer offers you to install a collection of DC-plugins as well as two sample scripts. Please mind that upon uninstallation, these plugin .DLL-files will be removed even if they were there before. This also applies to scripts and other files. That's why you should not install Apophysis 7x over an existing version in the same folder. Choose a new folder or backup the old version first.

The installer includes the hotfix release #7 but future hotfix releases will not be included with the installer. A new installer is uploaded only on major releases (15D? 16?) so that a hotfix release is more like a "patch" and needs to be installed manually. The approach is the same as for 2.02 as the major release and 2.09 as the minor release:

1) Install Apophysis with the latest installer
2) Download the latest hotfix/patch if available and copy Apophysis7X.exe or Apophysis7X64.exe into the install folder

Installer (32 bit)

Installer (64 bit)

PS: A hotfix #8 seems likely because there is one bug remaining; apart from that, no other patch releases are planned. You are safe to consider this installer version the "final" 7x15C with a minor bug in the multithreaded renderer (known problem with "noise" and "crop"-variations)
I recently raised the poll "Installer or ZIP-package?" here. Now it's time to take a summary out of the answers!

I noticed that some of you wanted to answer "both" but that was not the question ;) I was asking what you were using to install 7x on your hard disk. That's why "both" was not in the clickable range of answers :nod:  The results were kind of equal. 52% of you are using an installer, the rest is using the ZIP-package. So my conclusion here is that the installer needs to come back.

And it will.

However, plugins will not be installed on your system with the installer anymore. That out of three reasons:
+ Apophysis 7x64 doesn't support them
+ The plugin path is customizable
+ The amount plugins being integrated in the installer before is now integrated in Apophysis itself

Now you need to give me some time to get the installer creation software back up and then I'll compose an installer for you :)
Oops! Something went wrong with uploading the files when I added this hotfix. The download links pointed to Hotfix #6 still. Please re-download Hotfix #7 if you downloaded it already. It's now pointing to the correct version.
Thanks, fengda2870 for pointing it out.

I added two rather critical fixes to Apophysis 7x15c:

+ Fixed post_curl variation by doing the following on Zueuk's suggestion (more below)
+ Fixed a bug which created a spiral (why so ever) on the blur variation when using multithreading

post_curl_c3 got removed and post_curl was made a simple, 3D aware variation (Z-passthrough)
The functionality of the former, built-in post_curl was renamed to post_curl3D which essentially a post'ified curl3D where the latest post_curl behaves like the plugin (except for the Z-passthrough)
This fix was done as a result of the recent CDA.

The problem that the blur-variations as well as the crop-variations might malfunction if you use MT and render anything non-transparent PNG is known and subject to fix in a later release, still. The fix for the spiral problem is kind of rough and has a (very very tiny) impact on the performance. Most likely, you won't notice it. But I want a better fix in there too :)

Download binaries (32 and 64 bit)

Download source code

Okay. A few more TINY problems were addressed here:

+ Fixed author/language name loading code. Was still trying to read ANSI-characters which scrambled the display in non-ANSI languages (actually a not-so-tiny problem)
+ Added chinese localization contributed by fengda2870 - available from
+ Fixed a few strings which were not localized

I really hope this is the last hotfix release and it's perfect now :) Enjoy!

And again, the downloads are here:

Download binaries (32 and 64 bit)

Download source code

Aaaand another hotfix release. This time, these problems were addressed:

+ Fixed bwraps, pre_bwraps and post_bwraps (potential division by zero) - thanks again, Fred!
+ Added localization support for the curves panel
+ Changed the flame and translation loading/saving code to support and use UTF8 encoding
+ Updated german localization
+ Updated italian localization (with the help of the great lindelokse - thanks!)

You can get the updated localizations from The binary/source downloads are here (and also on the homepage):

Download binaries (32 and 64 bit)

Download source code

To be honest, the localization of Apophysis didn't run very well. People have indeed sent me their translations but some of them are outdated with 15C (new strings added) and some of them were even outdated with 15A/B. I apologize for the chaos there but this is a quite complex project and I think the core problem is that the translation release frequency is notably lower than the Apophysis release frequency.

Whoever sent me their translation - the latest I got via mail is czech - has my dearest thanks :)

Now let's get this chaos into order and put some serious work into it. What are the problems?

1) Lack of information on how to create a translation file
2) Translation files outdated very fast
3) Lack of utilities to create translation files (have to use Editor)
4) Encoding confusion (UTF8 not natively supported by Apo, special chars look wrong)
5) Wide character or non-western languages like chinese, japanese, arabic, hebrew, russian ... extemely problematic

I am asking for your suggestions here. How can we fix all these issues?

I put some work into loading proper UTF8-files today. The Apophysis code itself is very incosistent when it comes to encodings and such. My first attempt would be to fix that and generally load UTF8 language files. It's possible since Delphi XE2 supports Unicode properly now. That should fix 4) and perhaps 5) if I can bring the XML parser to load wide strings.

Then I created a very small and rough tool to load the source code file "Translation.pas" (which contains the default strings) and edit the strings within the program. Then you can save an XML file. Whether it works for non-western languages...well I don't know. It should but I can't test it. Should fix 1), 3), 4) and potentially 5)

Now only 2) remains. To fix that, there needs to be an active community creating translation files as a new version of Apophysis is out. Suggestions? Somebody who is willing to get on that?

Help me out here :)
Oh mai, it seems that Apophysis 7X jumped on some kind of rapid-release schedule :lmao:

You kept reporting problems which I of course want to straighten out. This time, mostly about the newly introduced curves feature. I'm pushing updates on a daily basis - when possible - until they are kind of sorted out. At least the critical ones. Here is hotfix #4!

+ Changed color curves feature to use regular cubic béziér splines. They are weighted internally still but you can't change it from the GUI (which is not really necessary anyway...) ... it's kind of a hack, though, to bring you back the original coloring (not so vibrant and glary) but keep the possibility to adjust the color curves. I want to keep the weights - this is why I didn't remove them but it gives me a bit of time to fixing the maths!
+ Moved the curves window into the adjust window
+ Fixed the plugin loader code AGAIN to have the original list item coloring in the 32 bit version (white for basic built-in, blue for built-in plugin variations and yellow for external plugin variations)
+ Fixed the flame updating code so that changing the preset doesn't get reverted when you click on the curves panel

As always, download here:

Download binaries (32 and 64 bit)

Download source code

Two things changed:

+ Added color curves dialog
+ Fixed plugin recognition routines. Variations, which were already built-in were loaded anyway which lead to an "Access Violation" storm in the editor. Thanks again morphapoph for tracking the origin of the problem in such a masterful way!

The color curves dialog is very simple and straight forward. Works like the one in Photoshop. Or Chaotica. Or GIMP...and it's not perfect. It's a new feature and maybe a bit bugged. But we'll see how much better it gets over time ;)

As always:

Download binaries (32 and 64 bit)

Download source code

Check out this intro video for 15C :) All the new features explained!

An updated version of Apophysis 7X15C is hitting the servers right now. The changes are:

+ Added possibility to specify a custom plugin path for the 32 bit version
+ Fixed bipolar variation (wrong constant used in preparation routine - M_2_PI is not 2 * PI. Thanks, Fred!)
+ Fixed "X"-button next to the search field
+ Fixed a memory leak in the renderer
+ Changed the 32 bit version to use 32 bit-floats (instead of double precision = 64 bit floats) which results in less memory use in the 32 bit version and higher image quality in the 64 bit version
+ Changed Chaotica integration so that 64 bit Chaotica is enforced if 64 bit Apophysis is running

I'm sorry for the update frequency but that's how it is in the first days after a new major release! People are actively tracking bugs and report the results to me. And I fix them and release hotfixes :) Once we - as a community - tracked down all the (not so hidden) bugs, the update frequency will drop to normal again :nod:

As usual, the download links for the latest files:

Download binaries (32 and 64 bit)

Download source code

Attention: I strongly suggest that anyone who updates to 15C uses the script "Reset settings.cmd" by just double clicking it in the Windows Explorer. This will ensure that you have no incompatible settings from old versions of 7X. There a lot of problems including Access Violation rages if something is wrong in your settings. PLEASE PLEASE PLEASE reset them using the script BEFORE you come to me and report bugs. Kay? :)
I have compiled a few hotfixes for the recent 15C release:

+ Fixed the MT renderer - was not properly reading transform opacity values
+ Fixed render log - was showing "32 bit integer" still
+ Changed the default settings so they comply with UAC-enabled systems
+ Fixed loonie variation code - had potential division by zero
+ Added scripting back in 32 bit-version - waiting for TMS to deliver 64 bit-support
+ Added a few one-click helper scripts to simplify things like settings reset and running 7X lite

Download binaries (32 and 64 bit)

Download source code

I get an error about Apophysis7X.rand and/or Apophysis.undo when I start Apophysis
It's a Vista/7-issue which spawned after using Delphi XE2 as the main compiler (since 15C) You have multiple possibilities:
1. Right click the Apophysis shortcut or EXE-file and select "Properties". Go to the "Compatibility" tab and check "Run as administrator". Try again.
2. Copy your Apophysis folder to the desktop (or "My Documents") and try running it from that location.
3. Go to the control panel and disable UAC ("User account control")
A permanent fix is on the way.

I get a crap ton of access violations when I open Apophysis and/or the Editor window
My assumption is that there is an incompatibility in your settings. Reset them the following way:
1. Exit Apo, hold the Windows-Key and hit "R" on your keyboard. Enter "regedit" and hit return.
2. On the left side, browse to "HKEY_CURRENT_USER\Software" and find the folder "Apophysis 7X".
3. Right click that folder and click "Delete".
4. Try again.

My 3D flames look wrong
3D-Flames need tweaking if their particular case slipped through the stack of automatic conversion routines I added to the loading routines. Please manually tweak your flames with the following information:
1. All (!) variations which are built-in are 3D-aware since 15C. That means, they create OR preserve the Z-component of the 3D point (X, Y, Z); so let's say you used spherical on transform 1 and julia3D on transform 2. Before 15C, spherical was not 3D aware. But now it is and your flame will look different because julia3D creates a Z-component and spherical preserves it.  To fix this, add "flatten" to transform 1 (the one with spherical) to delete the Z-component again and restore the old behavior.
2. Linear3D doesn't exist anymore. The community expressed, that two linears were silly and unnecessary. I first removed the old "linear"-variation (the one which was 2D) and renamed the old "linear3D"-variation to "linear". So linear3D is gone AND linear is now 3D by default. If you want the old 2D-linear back, add "flatten" on the same transform to make it 2D.

Okay. But my flame is 2D and it still looks wrong. I used a plugin which got built-in.
I am a human and I might have made an error while porting the plugin. Please send me examples (in picture AND parameter form) to my e-mail at xyrus01(at) and tell me what variations you assume are buggy. I will then try to help you and fix the problem.

While using multithreading (MT set to anything else than "Off"), my flames which have a transform opacity between 0 and 1 look like the opacity was 1.
morphapoph reported to me about this problem and I indeed found a bug in the multithreaded renderer where the opacity is not properly implemented. Unfortunately, you can't do anything about that but it was a problem in previous versions of 7X too. I am fixing that right at the moment, though!

Using non-latin characters or special characters like backslashes, quotation marks et cetera in flame names or file names make Apophysis hang or crash.
With Delphi XE2, Apophysis internally supports Unicode. But the code was not fully updated yet (and it will take some longer) - I wanted to give you a release so you can play with it right now and not let you wait until I finished the entire transistion. Please be patient with me while I update the code to use proper unicode characters. I do not wish to force you to use latin characters. The Apophysis code does that until it got updated.

Apophysis crashes natively ("Do you want to send this problem to Microsoft?") or with a lot of "Access Violations" upon start or during the execution and/or the installer (only available up to 15B as of now) doesn't start ("Not implemented")
Apophysis and a few other programs are incompatible with a product called LiteStep. MindsEye69 pointed out that a similar product called BlackBox causes problems too. Based on this information, I can safely assume that shell replacements or enhancers (such as the Stardock-products WindowBlinds, DesktopX, WindowFX, ObjectDock as well as Aston, Samurize and Cairo) are incompatible with Apophysis. Please check for any of those and try to run Apophysis without those software products before reporting a problem of crash-nature. An exception from this rule would be RainMeter which has been proven to work just fine with Apophysis. But try to disable this as well before contacting me about a crash-related problem.

Anything else? Did I forget a problem you reported? Please let me know and I will add it here!
I have here a preliminary release of Apophysis 7X 15C. The following changes have been made:

+ Added log (from logn - included the variable log(n)_base)
+ Added polar2
+ Added cross
+ Added wedge
+ Added epispiral
+ Added (pre-/post-)bwraps
+ Added blur_circle
+ Added blur_zoom
+ Added blur_pixelize
+ Added (pre-/post-)falloff2
+ Added splits
+ Added separation
+ Added bipolar
+ Added loonie
+ Added escher
+ Added scry
+ Added ngon
+ Added foci
+ Added lazysusan
+ Added mobius (the one with Re_A, Im_A... - variables)
+ Added (pre-/post-)crop
+ Added elliptic
+ Added waves2
+ Added auger
+ Added pre_spherical
+ Added pre_sinusoidal
+ Added pre_disc
+ Added post_curl
+ Removed linear3D (the 3D-linear is now simply called "linear")
+ 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
+ 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 64 bit floating point to improve numeric accurancy and speed (less conversion); MichaelFaber pointed out that this will require more memory for rendering, though. I will consider adding a 32 bit floating point mode for low-end computers.
+ Removed the EXIF-writing for JPEG-renders (couldn't find up-to-date and free library)
+ Temporarily removed scripting support. More info here. It will come back with a hotfix once I got enough donations for the component. I'm at 71 of 95 euros right now.
+ Introduced an experimental 64 bit version with no plugin support (which is why I added so many variations)
+ Fixed the editor toolbar glitch

As you can see from the changelog, one or two hotfixes will appear which bring back scripting and add a few more variations (glynnsim2, flux and circlecrop are in the works)

PLEASE MAKE SURE TO REMOVE ALL OF THE PLUGIN VARIATIONS WHICH ARE IN THE LIST ABOVE! Or you will get a lot of "variation already exists" errors!

Note that the variations (pre-/post-)bwraps2/7, Epispiral (capital E), cross2 and logn automatically translate to their corresponding new built-ins once you load or paste parameters. Note that 3D flames might break and need tweaking.

Important notice about the flatten-variation: the flatten-variation restores the old behavior of non-3D/built-in variations. It zeroes out the z-position so the pattern looks "flat" (like with a variation with no 3D support); use this to restore old flames :)

But for now - you can get Apophysis 7X 15C here:

32 bit Windows (with plugin support)

64 bit Windows (no plugin support)

Source code

You should use the 64 bit version if:
- You don't need plugins and / or can work with the built-in variations
- You want to render very large images (for printing)
- You have 4 GB of RAM or more

Do you have a problem or bug to report? Please read this journal before you do so!

There is more animation work done now. This time, I took care of "Breach" and tried to improve
the intro/outro-works and audio syncing. Neither of that is perfect but I think it's starting to evolve.
I really like AfterEffects now. Great tool to use. And Premiere is the perfect dubbing tool to create
the video out of it in conjunction with SoundBooth to cut the audio and add special FX :)

Here is the artwork I animated:

Breach by Xyrus-02

The often requested browse functionality is now implemented as well. You can reach all of the four selection types from the main page:
  • Recent shares: obviously all flames recently shared sorted descending by time. Theoretically, you can load more and more on the browsing page until you are down to the very first share.
  • Similar flames: clicking the red "similar"-tag shows flames which have one or more of the same tags (not owner-tags, "tags" as in "keywords") - the more tags are equal, the higher the result is in order
  • By tag: lists flames with the same keyword
  • By owner: lists flame with the same owner - you can not list flame with no owner (anonymous shares) using this selector

I hope you like this addition. Now go and build a nice flame database for the community to use :)