RadeonRays_SDK
RadeonRays_SDK copied to clipboard
Builds in Ubuntu 14.04.4 64 bit with proprietary N????? drivers if -lOpenCL added. Executable starts but exits immediately with message.
Still investigating but so far I found this:
In build instructions note that: There is no premake4... use premake5 Doing make ... Note config option with name "release64" as instructed in README.md i.e. "make config=release64" does not exist. Possible options seem to be make "release_x64" or "debug_x64"
I needed to add -lOpenCL to line 25 LIBS += ../Bin/Debug/x64/libCLW64D.a -lFireRays64 -lOpenCL -lOpenImageIO -lglut -lGLEW -lGL in file App/Makefile
Needed to add to LD_LIBRARY_PATH the directory /home16/robert/Code/FireRays_SDK/FireRays/lib/x64/ containing the file libFireRays64.so
Run .... robert@kalymnos:~/Code/FireRays_SDK$ ./Bin/Debug/x64/App64D Cannot read the contents of a filerobert@kalymnos:~/Code/FireRays_SDK$
robert@kalymnos:~$ dpkg -l | grep -i opencl ii clinfo 0.0.20130513-1 amd64 Query OpenCL system information rc nvidia-libopencl1-340 340.96-0ubuntu0.14.04.1 amd64 NVIDIA OpenCL Driver and ICD Loader library rc nvidia-opencl-icd-340 340.96-0ubuntu0.14.04.1 amd64 NVIDIA OpenCL ICD ii nvidia-opencl-icd-352 352.79-0ubuntu1 amd64 NVIDIA OpenCL ICD rc nvidia-opencl-icd-352-updates 352.63-0ubuntu0.14.04.1 amd64 NVIDIA OpenCL ICD ii ocl-icd-libopencl1:amd64 2.1.3-4 amd64 Generic OpenCL ICD Loader ii ocl-icd-opencl-dev:amd64 2.1.3-4 amd64 OpenCL development files ii opencl-headers 1.2-2013.10.23-1 all OpenCL (Open Computing Language) header files ii unity-scope-openclipart 0.1+13.10.20130723-0ubuntu1 all OpenClipArt scope for Unity
I have added missing HDRI file: stduio015.hdr. Make sure you are doing clean check out and try to build again. If you want to try with Mercedes assets you can download from here and put into Resources: https://drive.google.com/file/d/0B9HEaOdIangnTzNXdkdLaWZ3UDQ/view?usp=sharing
OK file is found now. Directory where code is run also matters. I now get a problem with long long type not being supported see below
git pull; make clean; ./premake/linux64/premake5 gmake; vi App/Makefile; make;
cd Bin;
robert@kalymnos:~/Code/FireRays_SDK/Bin$ Debug/x64/App64D
In file included from
In file included from
This is known issue with Nvidia runtime. Feel free to replace it in App/CL/sampling.cl with a simple int. We will fix it in the meantime.
OK removed ULL... now I get this:
robert@kalymnos:~/Code/FireRays_SDK/Bin$ Debug/x64/App64D Running on devices: 0: GeForce GTX 660 OpenGL interop mode enabled Loading complete Number of objects: 152 Number of textures: 0 Number of emissives: 0 terminate called after throwing an instance of 'FireRays::ExceptionImpl' fatbvh accelerator can't allocate enough stack memory, try using bvh insteadAborted (core dumped)
Seems like memory allocation limitation in nvidia runtime. Try replacing api_->SetOption("acc.type", "fatbvh") with api_->SetOption("acc.type", "bvh") in frrenderer.cpp
Runs now. Initially I got something suggesting a cmap problem with coloured dots filling/building the view (1st image):
Mouse event results in image going greyscale with no noticeable structures other than decreasing high spatial frequency noise over time (2nd image):
@beasterio checked on GTX 970 with 352.79 linux driver and it is working fine. One option you can try is to disable OpenGL interop with --interop 0 option. If it does not work we will try to get GTX 660 to reproduce.
Just did a git clone, ./premake/linux64/premake5 gmake, make. Had to add -lOpenCL to Makefile as before to compile , changed fatbvh to bvf in App/frrenderer.cpp to avoid run time memory issues. New ifdef deals with Apple case. Ran "../Bin/Debug/x64/App64D and "../Bin/Debug/x64/App64D --interop 0". Same behaviour i.e. I do see the "photons" building up the gray scene over time to finally yielding a nearly noise free flat gray scene like the 2nd image above. I don't seem to have cmap issues anymore (1st image). Am I supposed to get the same scene that I got with the old AMD web site version?
Will apt-get upgrade this work system/reboot (it has been a month) and also try at home where I think I have a different card..