Mandelbulber 1.19 - OpenCL - user defined formulas management

[Buddhi]

I have tried all possible methods to avoid this problem (double quotes, put files into program folder...). This is known bug in OpenCL compiler. Till yesterday I knew that it was only for nVidia driver. But now I see that it also happens for AMD. The worst is that I can't reproduce this problem on my machine (it uses double quotes properly - AMD under Vista). I also took into consideration to load mandelbulber_cl_data.h file in the same way like other files. Unfortunately this method will make difficult debugging the code (numbers of code lines will be wrong when compile error occurs). I also can't hardcode path in #include command, because under different systems this path can be different.
Only idea what I can change is location of includes. What will be the best folder under Windows instead of "Program files" which has no spaces in path?

[R-TEAM]

Hi,

have the exactly same problem on my second workstation (IBM QuadCore) with Win7Pro64SP1 too...
(GFX Card here an AMD HD4850 - so an different driver)
Maybe Win7 related ? (or the German version ? )

Regards
R-TEAM

[R-TEAM]

Hi,

......What will be the best folder under Windows instead of "Program files" which has no spaces in path?

Simply - create an folder (like OpenCL directly on C:\ -> C:\OpenCL ) - if the known problem is gone with the compiler, the folder can be deleted/moved back to the programm folder ...

Regards
R-TEAM

[JohnVV]

Not just "no blank spaces" but under win7 people have been having all kinds of major problems with MS's " Program Files" and windows royally messed up UAC ( read as FUBAR'ed UAC )

non "Administrator" accounts sometimes can not write to the program folder if it is in "Program Files"

a good option might be
C:\\Mandelbulber
or
C:\\MandelbulberOpenCL
or ( if you do not want to type a long name into "cmd.exe"  or did not turn on "Open CMD here" in win7 )
C:\\MCL

[Buddhi]

I have developed some nice workaround for this problem. I read in many forums that there is not possible to pass any parameter with spaces for OpenCL compiler (e.g. -I include path, -D define....). I started to look for alternative way to put something directly but dynamically into code. I use following method:

- in OpenCL kernel instead of #include "mandelbulber_cl_data.h" I use macro #include INCLUDE_PATH_CL_DATA
- in C++ code I stitch following header before first file with the code: #define INCLUDE_PATH_CL_DATA "/usr/share/mandelbulber/cl/mandelbulber_cl_data.h" (or some other, depends on OS and program folder path)
- additionally first line of the kernel code is modified to stat with double slash (//*********************). Then "#define..." will be in the first line of kernel code and don't make any additional line. So when there will be any compiler error I will still have proper line numbers.

This method passed first trials, so it looks promising

[mclarekin]

Buddhi. Cant wait to try it out as I too have been stopped by error -43 on AMD A10-5800GHz Radeon HD 7660D, plus my crappy laptop AMD. I had wondered why in GPU Caps Viewer the Open CL demos worked but Mandelbulber wouldn't compile.

[R-TEAM]

Hi,

yea - an nice running OpenCL part would be nice - for next year an GFX Card upgrade to S10000 is planed ... and the beast need numbers to crunch

Regards
R-TEAM

[Buddhi]

This method to fix the problem with include path works well (tested under Linux with AMD and nVidia and under Win Vista with AMD). I think it is good information for all nVidia users (some AMD also). Today I released version 1.20 which should work properly with OpenCL under Windows.
Visit and comment in new thread: http://www.fractalforums.com/releases-b233/re-mandelbulber-1-20/msg69690/#new