Help?

[M Benesi]

ehh.. So... I have to fiddle with Detail as I up or lower the # of iterations.  Not really used to this DE thing....


  The regular Mandelbulb seems to work best with a specific Detail setting, but this one you need to fiddle with... so.. any ideas?

[Crist-JRoger]

I will try to apply the "No Auto Run" feature in preferences to the tab switching, but it should only be applying the last valid settings when returning to a tab ie: putting it where you left it so that settings from previous tab don't interfere with current tab.

Yes, it is. But I use progressive mode and set 40-50 subframes in preview sometimes. Just long wait and i don't need to save options from every tab )

can you elaborate on this a little bit?

There is sliders in parameters(uniforms). It could be regulated by keyboard(very conveniently and accurately). Sometimes when you regulate slider by keyboard, current value may go beyond the out of max/min slider values. And it's cool! Because  min/max valeus are conditional.
For example use specular more than 2, or power in mandelbulb more than 16. It gives diversity  
So, in latest versions this feature don't works and frag files with crazy values opens incorrectly.
This is just my observation and I absolutely do not need a new version. Unless you force the program to render twice as fast ...

[3dickulus]

@Crist-JRoger I understand that on slower machines or very complicated frags this might be a good thing so I enabled "No Auto Run" globally, you have to "Build" and apply settings when switching tabs when "No Auto Run" is enabled in the preferences dialog.
The sliders were "fixed" so they only use the range specified when the uniform is created, you can just locate the slider in the frag files and adjust the min/max to whatever you like.
 2x as fast? how about 10x I need help with this implementation from some of the larger math brains but I'm convinced this will be worth the effort... http://www.fractalforums.com/fragmentarium/ray-histogram-fusion/

edit: I have posted v1.0.14 source code with a few bug fixes and "No Auto Run" patch

[M Benesi]

  Sweet build 3dickulus!  Runs smoother.. and faster on my archaic 8600m...    So much smoother.  

 I don't know if I dare to use some of the new raytracers on it though.  I want to...but I'm scared.  Really scared.  Ok.. going to do it.  


  So.. what raytracer is the best?  I switched to fast... and it seems faster... but maybe it's just because my mind is working slower. 

[3dickulus]

tnx

in the file DisplayWidget.h you will see in the first few lines...

Code:

#define NVIDIAGL4PLUS

comment this line out then clean and build again, this should help a bit for older cards, if your card supports GLv4+ or has no complaints then leaving it is ok.

DE-Kn2.frag is my preferred tracer but I always start with the default DE-Raytracer and then migrate if everything is working right.

RE: v1.0.14 includes

Depth to alpha is enabled via #define DEPTH_TO_ALPHA in the frag in the editor, by adding this line a checkbox will be added to the "Post" group, selecting this sends depth value to alpha channel in exr images only.

Auto focus is enabled via #define AUTO_FOCUS in the frag in the editor, by adding this line a checkbox will be added to the "Raytracer" group, selecting this will bind the focal plane to the target distance. Thinking about adding a bind target to surface so the target coord is truncated to the nearest surface intersection perpendicular to eye plane center.

edit: Look under the menu Edit->Insert Command->Host Preprocessor Commands

[M Benesi]

  Binaries man.  Binaries. 

[3dickulus]

@M Benesi very strange your frag doesn't accumulate frames in progressive mode unless Aperture has a non-zero value
B1 Aperture = 0.0      600 subframes
B2 Aperture = 0.001  600 subframes

wow, it's really fast btw.

edit: atm I can not provide win binaries 

[M Benesi]

k..  suppose I should read the thread on building it to find a freeware compiler to use.. 

   I'd switch to fast raytracer.  Phenomenally fast, compared to what I'm used to, even on my 8600m (8 year old mobile GPU).  The other Raytracers are commented out in this file. 

  Aperature 0 works for me.. but I'm still on build .13, so... dunno.  I'd seriously switch to fast raytracer (it's in the frag below.. but you can edit it yourself, obviously). 

[M Benesi]

So, i use old software too, or not "old" - i just don't update without necessary   

heh.... make sure you change to the fast-raytracer version, or if you have a good GPU, put in Knighty's. 

 It's at the top of the new frag, commented:


  The new one is set up for Fast...  to change to DE-Kn2.frag, put // in front of the Fast-Raytracer.frag include statement, and remove it from Knighty's (DE-Kn2).
 

Code:

#define providesInside
#define providesInit
//#include "DE-Raytracer.frag"
#include "Fast-Raytracer.frag"
//#include "DE-Kn2.frag"

[3dickulus]

k..  suppose I should read the thread on building it to find a freeware compiler to use..  
....
  Aperature 0 works for me.. but I'm still on build .13, so... dunno.

just tested my v1.0.13 and it is the same, no accumulation   edit: aha! GaussianWeight and AntiAliasScale were at 0.0

MinGW on Win7 is what I used for v1.0.13

Qt site provides Qt v5.5.1 not sure if there are any code adjustments required, the dev kit is here http://download.qt.io/official_releases/online_installers/qt-unified-windows-x86-online.exe I think it will install MinGW and QtCreator + Designer but I haven't updated since v5.3.2. With a little luck the installer will provide version and tool chain options. Once it is installed, open the MinGW command prompt, basically it's a dos window with all the paths and environment variables setup for running the compiler, change directory (cd) to Fragmentarium-1.0.14-3Dickulus folder and type ./mkmingw <enter> , this should build OpenEXR and Fragmentarium folders, you may have to adjust the paths in the mkmingw.bat file, they are set to C:\Fragmentarium-1.0.14-3Dickulus.

After OpenEXR is built you can also load the Fragmentarium.pro file with QtCreator to compile the Fragmentarium project.

[M Benesi]

Cool.  I'll give it a try tomorrow and let you know how it turns out.

[3dickulus]

ooops! forgot to mention you need to install CMake tool for the bat file to work  you can get it at https://cmake.org/download/

[Crist-JRoger]

The sliders were "fixed" so they only use the range specified when the uniform is created, you can just locate the slider in the frag files and adjust the min/max to whatever you like.
 2x as fast? how about 10x I need help with this implementation from some of the larger math brains but I'm convinced this will be worth the effort... http://www.fractalforums.com/fragmentarium/ray-histogram-fusion/

I know that ) but when i create the scene, there is no time to go to frag files and change default min/max values ) Just more free to use parameters(uniforms) tab.
10x?        Where are this glsl monsters who can do it? )))

So.. what raytracer is the best?  I switched to fast... and it seems faster... but maybe it's just because my mind is working slower.  

See this topic to see what DE-kn2 can do    http://www.fractalforums.com/fragmentarium/updating-of-de-raytracer/

upd.: 3dickulus, can you create pause button in final rendering window? 

[3dickulus]

10x?        Where are this glsl monsters who can do it? )))

if this ... http://www.fractalforums.com/fragmentarium/ray-histogram-fusion/ ... can be implemented then 200 iteration quality from 20 iterations.

upd.: 3dickulus, can you create pause button in final rendering window? 

how about "Really quit?" when "Abort" is selected so you have the option to continue.

[Patryk Kizny]

RE: v1.0.14 includes

Depth to alpha is enabled via #define DEPTH_TO_ALPHA in the frag in the editor, by adding this line a checkbox will be added to the "Post" group, selecting this sends depth value to alpha channel in exr images only.

Auto focus is enabled via #define AUTO_FOCUS in the frag in the editor, by adding this line a checkbox will be added to the "Raytracer" group, selecting this will bind the focal plane to the target distance. Thinking about adding a bind target to surface so the target coord is truncated to the nearest surface intersection perpendicular to eye plane center.

Does it mean that Frag already honors #ifdef statements also for uniforms?
From my experience it did not in the past and I wanted to push you to implement it.
I think that it makes sense to leave optional code behind ifdefs instead of runtime uniform bools. That's what I do but found that not that code-savvy users had issues with these complaining the unifroms UI were here and there but did not do anything (cause no #define... were used).