Hi Michael! In your reply to Pillemaster you said: 1) First thing i notice here is the real low hit point ratio. Your sitting at about 6.4%. If you want to render a smoothness you would normally find at a Quality of 1000, you'd have to render at about Quality = 15,000. How does one determine that by looking at a set of params? An answer for a novice would be best, if possible.
I got the hit point ratio from the extended render statistics in apophysis. To turn these statistics on, go to Tools>Settings>General and make sure 'Show Extended Render Statistics' is checked.
Now after you render, in the Output window, instead of something like this: --- Rendering "3.bmp"" --- Size: 800x600 Quality: 200 Oversample: 1, Filter: 0.4 Buffer depth: 32bit integer 6:38:53 PM : Allocating 7.85 Mb of memory... 6:38:53 PM : Rendering... 6:39:45 PM : Creating image with quality: 200.02... 6:39:46 PM : Saving image... Average speed: 1,997,669.23 iterations per second Pure rendering time: 51.48 second(s) Total time: 52.81 second(s)
Render Statistics: Max possible bits: 34.616 Max Red: 19.596 bits Max Green: 20.523 bits Max Blue: 20.742 bits Max Count: 15.592 bits Point hit ratio: 39.95% Average speed: 1,977,276.23 iterations per second Pure rendering time: 52.02 second(s) Total time: 53.28 second(s)
Thanks a lot, I will port them to JWildfire and of course give you credit. I hope one day I will find the time to create also some more of my own plugins. Must be really fun to play with them in Mathematica or whatever you are using But time is currently always too short for me...
really cool plugin - i can make these fractals insted of the bipolar/unpolar/glynnsims now which produce very similar results. the only problem i see is that there is no "bcrop" to remove the overlapping flame edges of the btransform, when using the split option to make bordering rings ... like in picture 1 and 3 ... such a plugin (option) would be great!!!
here is some first test result with only one btansform as "final"
Hmm. You've got some weird stuff going on in here.
1) First thing i notice here is the real low hit point ratio. Your sitting at about 6.4%. If you want to render a smoothness you would normally find at a Quality of 1000, you'd have to render at about Quality = 15,000. Very slow
Three layers of "final" transforms is amusing - it would be cool if the app supported it - but the effect is minimal and the cost is great. I'm not sure that you would normally do this, or if this is just a neat example of rewriting the chaos game using Xaos. (Xaos Game?)
2) The second thing i notice here is the use of Crop. I like the idea of a crop variation, but i think it really requires built in app support to handle it better. It can be used to great effect to clean things up, but i think it is over used here. If crop should be used at all, i think it should only be done at the very end if cleaning up some noise or making some lines sharper. Using Crop to crop out a large portion of the points makes the whole image less clean. Or maybe i'm obsessive compulsive and don't like any points 'lost'. That being said, i think i would sooner start coding in apophysis than make a crop variation.
Anyway, here's what i came up with. It uses Modulus instead of crop. This way you can still get some translation and rotation in these shapes - albeit taking into consideration the period of the tile. And i just have a regular final transform.
yes a admit the crop plugin was overused for the tile - (was only messing around, not watching quality loss or rendering time increase)
unfortunately, this caused some misunderstanding as well...
in the following flame only one crop is used and now for the effect i meant: to get clean borders of the stripes!
the only way i can do this so far is by using a traditional bipolar - stretch it with linears and circle it up by unpolar - this finally allows me to multiply this cirle with glynnsim3 and will produce (after a lot of xaos and time) similar flames to the ones achieved with btransforms:
as a result i was asking for a "bordercrop" of the btransforms -> which would requires to set all pixes of the initial btransform (which would be "outside" the btransform_split value of the "multiplier" btransform) to that exact border value.
...so i guess it is still difficult to program ... and i should stop bothering you here
in case there is still a chance to get that special crop -> this is an example which illustrates where i wanted to end up:
The flame pack opens correctly and I can see all three samples. However, when I try to open the editor window, I receive the message "Access violation at address 004AAC46 in module 'Apophysis7x.exe'. Read of address 00000049." You are only given the 'Accept' button but the program will continue giving additional address errors. I can only kill Apo with the task manager.
I have 116 plugins installed which usually work well. Sometimes one of them would not load but that is not preventing Apo to run. I left oly your 4 plugins and have no problems. So, there should be a rejection from some of the other plugins. Comments suggest that plugins are not developed following any pre-specified rules, so incompatibility is almost a natural result. We, users, are loosing our hair (fortunately I have only a few left) trying to determine which plugin goes wich which other. Not good.