» Blender 2.71 (Fedora 20)
Updated 02:20 June 18th, 2014
21
(1029)  9,468

Update: For some reason graphicall will not allow me to update this build, so I've made a new one here: http://graphicall.org/1127

 

This is the Blender master branch, compiled on Fedora 20 64bit.

Leave a comment if this build doesn't work on your system :)

 
 
21 Comments so far. Leave yours.
14:49 February 23rd, 2014
21 . JamesNZ (builder)
@billrey, Hi, sorry I didn't get back to you quicker. Anyway, it appears that this is now enabled in master :)
04:26 January 23rd, 2014
BTW, here's what to change to build with SSS for the GPU. Would be great if you could do that! :)

http://lists.blender.org/pipermail/bf-cycles/2013-October/001645.html
04:20 January 23rd, 2014
Hi, thaks for the build. Could you build a version with GPU support for subsurface scattering?

Thankyou in advance!

Cheers

William
12:40 January 7th, 2013
@JamesNZ - Thanks for all your help anyway. If you ever need someone to test a Blender build on Fedora just let me know (mike dot laughton at gmail dot com).
20:19 January 6th, 2013
17 . JamesNZ (builder)
@mblaughton, Hrrrrm that's odd. I'm actually unable to test out CUDA rendering on my system because my card is too old, but I can see the option for it: http://i46.tinypic.com/fmmha8.png

The problem here may be that you have to compile the CUDA kernel for your card. You see, my machine runs out of RAM when it compiles the CUDA kernels for Blender. It'll just hang, with the CUDA compilation service taking all of my RAM and using around 10% of my CPU :( The reason I've still marked this build with CUDA is that even if I don't enable compiling CUDA binaries, the option to use it is still coming up in my user prefs. And if I try to render something with the GPU, it appears that Blender will start compiling the CUDA binaries. So I thought that the users could just compile the kernels for their specific compute capability the first time they rendered something, just like it did on my system.

Evidently I was wrong :| When I first enabled CUDA I did ask the users to tell me if it worked/didn't work, but no one ever responded so I assumed that it did work. Will remove the CUDA label......

Sorry for confusing you :(
19:02 January 6th, 2013
@JamesNZ: Thanks, that gets me much closer. The program launches successfully now, and spits out the following message at startup:

found bundled python: /home/mike/Downloads/blender_53617/2.65/python

...which makes sense given your comments. However when I go to File|User Preferences|System|Compute Device, it says "None" and only offers "CPU" in the drop-down.

My system has a new GeForce GT 610 card, which is on the list of supported chipsets, and I even downloaded a Windows build from graphicall.org to confirm that the GPU is listed in the dropdown there (it is).

I also have the latest proprietary NVIDIA drivers installed and running, and can see libcuda.so.304.64 sitting in my /usr/lib64/nvidia directory. However, the blender binary doesn't link to libcuda (listing below). But it does link to libnvidia-tls.so.304.64 and libnvidia-glcore.so.304.64. I suppose it's possible the CUDA library was statically linked? Have you been able to select the GPU with this build on your system?

Incidentally, I have /not/ installed any of the CUDA-specific stuff from NVIDIA because I thought that's just for people who want to build against their SDK. But if you think it's necessary for regular users too, please let me know and I'll give it a try. Thanks!

[mike@tabby blender_53617]$ ldd blender
linux-vdso.so.1 => (0x00007fff7e3ff000)
libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x000000329c200000)
libGLU.so.1 => /lib64/libGLU.so.1 (0x0000003299a00000)
libpng15.so.15 => /lib64/libpng15.so.15 (0x00000036e5a00000)
libz.so.1 => /lib64/libz.so.1 (0x00000036e1a00000)
libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00000036e5200000)
libGLEW.so.1.6 => /lib64/libGLEW.so.1.6 (0x0000003299600000)
libopenal.so.1 => /lib64/libopenal.so.1 (0x00000036e5600000)
libfftw3.so.3 => /lib64/libfftw3.so.3 (0x0000003299200000)
libSDL-1.2.so.0 => /lib64/libSDL-1.2.so.0 (0x00000036e2e00000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000036e0e00000)
libtiff.so.3 => /lib64/libtiff.so.3 (0x0000003553400000)
libjpeg.so.62 => /lib64/libjpeg.so.62 (0x00000036ed600000)
libHalf.so.6 => /lib64/libHalf.so.6 (0x00000036ef800000)
libIex.so.6 => /lib64/libIex.so.6 (0x00000036e8c00000)
libIlmImf.so.6 => /lib64/libIlmImf.so.6 (0x00000036eb400000)
libIlmThread.so.6 => /lib64/libIlmThread.so.6 (0x00000036ea400000)
libImath.so.6 => /lib64/libImath.so.6 (0x00000036ea800000)
libOpenColorIO.so.1 => /lib64/libOpenColorIO.so.1 (0x0000003371000000)
libopenjpeg.so.3 => /lib64/libopenjpeg.so.3 (0x00000036ee200000)
libasound.so.2 => /lib64/libasound.so.2 (0x00000036e9e00000)
libspnav.so.0 => /lib64/libspnav.so.0 (0x00000036e7600000)
libutil.so.1 => /lib64/libutil.so.1 (0x00000036f5200000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00000036e4600000)
libX11.so.6 => /lib64/libX11.so.6 (0x00000036e3600000)
libXi.so.6 => /lib64/libXi.so.6 (0x00000036e6a00000)
libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x00000036f2e00000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000036e1200000)
libc.so.6 => /lib64/libc.so.6 (0x00000036e0600000)
/lib64/ld-linux-x86-64.so.2 (0x00000036e0200000)
libm.so.6 => /lib64/libm.so.6 (0x00000036e0a00000)
libgomp.so.1 => /lib64/libgomp.so.1 (0x00000036f0600000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000036e2200000)
libnvidia-tls.so.304.64 => /usr/lib64/nvidia/tls/libnvidia-tls.so.304.64 (0x000000329c600000)
libnvidia-glcore.so.304.64 => /usr/lib64/nvidia/libnvidia-glcore.so.304.64 (0x0000003299e00000)
libXext.so.6 => /lib64/libXext.so.6 (0x00000036e4a00000)
librt.so.1 => /lib64/librt.so.1 (0x00000036e1600000)
libtinyxml.so.0 => /lib64/libtinyxml.so.0 (0x00000036e4200000)
libyaml-cpp.so.0.3 => /lib64/libyaml-cpp.so.0.3 (0x00000036eb000000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x00000036e3e00000)
libXau.so.6 => /lib64/libXau.so.6 (0x00000036e3a00000)
17:08 January 6th, 2013
15 . JamesNZ (builder)
@mblaughton, re-uploaded with bundled python. Let me know if it works :)
14:23 January 6th, 2013
@JamesNZ, thanks for the fast response!

Here's some python3 info from my system:

[mike@tabby ~]$ python3 --version
Python 3.2.3

[mike@tabby ~]$ which python3
/usr/bin/python3

[mike@tabby ~]$ ldd /usr/bin/python3
linux-vdso.so.1 => (0x00007fffa8506000)
libpython3.2mu.so.1.0 => /lib64/libpython3.2mu.so.1.0 (0x00000036e5e00000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000036e0e00000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000036e1200000)
libutil.so.1 => /lib64/libutil.so.1 (0x00000036f5200000)
libm.so.6 => /lib64/libm.so.6 (0x00000036e0a00000)
libc.so.6 => /lib64/libc.so.6 (0x00000036e0600000)
/lib64/ld-linux-x86-64.so.2 (0x00000036e0200000)

I also tried messing around by setting BLENDER_SYSTEM_PYTHON and PYTHONHOME earlier couldn't get any behavioral changes (for better or worse).
13:21 January 6th, 2013
13 . JamesNZ (builder)
@mblaughton, Yes it is a python issue. Not sure why you're getting that error though, could you post the output of 'python3 --version'? That will tell me if your system can find the python3 installation (it should). If you get something like 'Python 3.2.3' (that means your system can find the installtion) then I can just reupload the build with bundled python :)
12:58 January 6th, 2013
Thanks for the build! This is the exact combination I need (Fedora 17 + 64bit + CUDA).

Unfortunately I haven't gotten it to run yet in spite of having the necessary dependencies (I hope) and having a recent NVidia card with the proprietary drivers. Here's the error I get:

[mike@tabby blender_53595]$ ./blender
ndof: unknown Logitech product 0809
ndof: unknown Logitech product c043

Note: No (valid) "startup.blend" found, fall back to built-in default.

Fatal Python error: Py_Initialize: Unable to get the locale encoding
ImportError: No module named 'encodings'
Aborted (core dumped)

------------
Could this possibly be a python version issue? Because although I have python3 and libpython3 installed, they are not used by default:

[mike@tabby blender_53595]$ rpm -qa | grep python3
python3-3.2.3-7.fc17.x86_64
python3-devel-3.2.3-7.fc17.x86_64
python3-libs-3.2.3-7.fc17.x86_64

[mike@tabby blender_53595]$ python --version
Python 2.7.3

Any ideas about what I should try next?
15:26 November 11th, 2012
11 . JamesNZ (builder)
@lokhorn, sorry that's the only one I've got on my system. I guess you'll have to manually change the paths, it shouldn't take more than 15 mins.
13:21 November 8th, 2012
Until now I'm noticing that my CUDA does not work, thanks for the advice :)

I think you sent the same mist patch as the original patch.
Error: Rejected patch for kernel_passes.h and kernel_types.h

if you can find the updated patch so upload it please
thanks:)
11:58 November 8th, 2012
9 . JamesNZ (builder)
Hi lokhorn, there isn't any automatic way to compile the mist patch because it won't be included in the trunk. Brecht reviewed it recently and decided not to commit it in favour of waiting for true volumetric support to be added to cycles.

The original patch can be downloaded from here: https://projects.blender.org/tracker/index.php?func=detail&aid=31860&group_id=9&atid=127
The file is under the attachments tab. However cycles has changed some file paths since the patch was updated so I had to change a lot of the paths within the patch.
I think this is the patch I made with the modified paths: http://www.pasteall.org/37028/cpp
I'm not completely sure though, I've reinstalled Fedora since then ;)

To compile Blender with CUDA I just installed the nvidia toolkit and the official drivers for my GPU. You don't need any special SDK to compile the mist patch.

HTH :D
01:04 November 8th, 2012
JamesNZ: I finaly compile my blender win build. Is any automate way use Agus3D's mist patch? What sdk do you use? thanks

sorry for my previous empty post
00:53 November 8th, 2012
16:38 October 28th, 2012
6 . JamesNZ (builder)
@ohsnapitsjoel, I got the mist patch from here: projects.blender.org/tracker/index.php?func=detail&aid=31860&group_id=9&atid=127, you can download the patch itself from under the 'Attachments' tab underneath the description.

BTW Brecht has said that he won't be committing the patch to trunk because it will make the code harder to maintain when volumetrics are added.
19:25 October 26th, 2012
since you're on Fedora, it looks like you're compiling with libraries that aren't readily available in some other distros. :( i've had the same problems with libs.

blendermad - you'll just have to install the libraries yourself or patch the source and compile it yourself. JamesNZ, which version of the patch did you use to compile this? where did you find it? i'd like to try building with this patch for Ubuntu/Mint users.
16:05 July 27th, 2012
4 . JamesNZ (builder)
@ blendermad: Did you install those deps? If you run this command in the terminal it should install those packages: apt-get install libopenjpeg-dev libtiff4-dev

If you have further problems please let me know :)
05:49 July 27th, 2012
is there any differences in the shared libraries used for blender from PPA and from graphicall.org. I have installed blender from PPA for Ubuntu12.04. and I have downloaded this build and it doesn't seem to work. why is it so?. libtiff, libopenjpeg3, why are not required by blender from PPA but by this build??
14:47 July 11th, 2012
2 . JamesNZ (builder)
Actually, I believe all of my builds are optimized since they use the OpenMP and SIMD flags :) If you want to build it yourself the Blender wiki has a good tutorial: http://wiki.blender.org/index.php/Dev:2.5/Doc/Building_Blender/Linux
08:40 July 11th, 2012
Why linux builds aren't always incomplete. It is hard to see a "optimized" build in "trunk". can any body help me to build on my own??
Feeling talkative?
Log in to leave a comment.