I created another domain for Apophysis 7X. But before you panic: the old domain (apophysis.xyrus-worx.org) is still reachable and will be reachable
The new location is http://apophysis-7x.org
; you can see the main page there. Downloads, history, etc.
Then there is http://code.apophysis-7x.org
; 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 http://code.apophysis-7x.org
; this is the new main bug tracker
for Apophysis 7X.
The bug tracker lives on SourceForge.net as does the source code. The alternative URLS are:
for the tracker and
If apophysis-7x.org 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 code.apophysis-7x.org
. 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
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!