The first thing to do is to try and recover the genome you where working on, by default Oxidizer saves
each genome it renders to ~/Application Support/Oxidizer/
Use finder to navigate to ~/Application Support/Oxidizer/
Here you’ll find the Genomes you’ve rendered, even if for preview thumbnails.
The file names are timestamps so 20090125204901240.xml was rendered at 2009-01-25 @ 20:49:01.240
Load the genome into Oxidizer and do your best to make it crash again. When you can make it crash repeatedly send me the following..
- The Genome.
- Your Oxidizer Environment Settings (the settings on the main window, so that’s Quality Scale, Size scale etc.)
- Instructions about any thing I have to do to make the flame you send me crash (e.g press render, select PNG, use filename fred.png, press render or change Zoom to 300 and click into the Scale text field). The more precise the better.
- Which version of OSX you’re using, including Intel or PPC
oxidizer.crash.log
flam3-render.crash.log
flam3-genome.crash.log
flam3-animate.crash.log
flam3-render.crash.log
flam3-genome.crash.log
flam3-animate.crash.log
If you’re feeling helpful, copy and paste the relevant bits from there, they’ll have a timestamp in them to help you identify the relevant report.
Zip them up and send them to me along with everything else to me at vargolsoft.
Don’t forget to post to the Rampant Mac forum too, so every one can have a look too, or suggest a work around.
Finally, If you find Oxidizer freezes when you start it up, add Oxidizer to the exclude list of any haxies, or get just get rid off the haxies all together and try again.
If Oxidizer magically works, then post the details here, so every one knows what haxies can cause issues.
There are no comments on this page. [Add comment]