Using blender?

[Metatronin]

Has anyone got blender to run? It installed fine using "sudo apt-get install blender". But it does not load. Can more ram be allocated to the gpu to get it running, if so how?

[SirLagz]

Blender uses OpenGL, which the Pi isn't capable of.
Unless someone recodes it for OpenGL ES, I don't think we're going to have Blender on the Pi.

[Metatronin]

Are there any 3d apps that run on raspi? Or is it just to early for such a thing to have been made/ported yet?

[Jim JKla]

I wonder if one of the archive versions of blender will work there's a massive archiveof older versions.

[Metatronin]

Did some looking around, and someone has ported the blender game engine to open GLES(for android). And already had several requests for a port to the raspi. Not the full on application, but this could be future pipeline to make 3d games and port them over to the raspi.
Better than nothing!

[Jim JKla]

There's a whole generation of 3D'ers out there that could come from making Blender a reality for the RPi.

[glframebuffer]

In principle It is possible to run blender on Raspberry pi, Since it is available on android.
Check out:
http://www.phoronix.com/scan.php?page=n ... px=MTE2OTY

Cheers

[Joel_Mckay]

Well now, I tried to get a minimal core to compile on the Pi without success.
This build issue will need more coffee beans...

###########################################
#dpkgs needed to build on wheezy
sudo apt-get install openmpi-dev openmpi-bin openmpi-common libopenmpi-dev mpich2 mpich2python python-mpi4py
sudo apt-get install zlib1g-dev libpng12-dev libjpeg-dev libjpeg-progs vlc ffmpeg libsndfile1 fftw3 openexr libopenjpeg-dev python2.7-libtiff libtiff-dev libsdl-dev libboost-dev libopenexr6 libopenexr-dev libjack-dev libsndfile-dev libfftw3-dev libavcodec-dev libavutil-dev libswscale-dev
sudo apt-get install vlc ffmpeg libsndfile libfftw libgles2-mesa liblogsys-dev
sudo apt-get install libarchive12 libaudio2 libavahi-client3 libavahi-common-data libavahi-common3 libboost-date-time1.49-dev libboost-date-time1.49.0 libboost-filesystem-dev libboost-filesystem1.49-dev libboost-filesystem1.49.0 libboost-regex-dev libboost-regex1.49-dev libboost-regex1.49.0 libboost-serialization1.49-dev libboost-serialization1.49.0 libboost-system-dev libboost-system1.49-dev libboost-system1.49.0 libboost-thread-dev libboost-thread1.49-dev libboost-thread1.49.0 libboost1.49-dev

#kinda stuck here for now....
#Pi repo does not have openimageio pkg
#and libgles2 and liblogsys does not resolve -lGLXv2 -llog compile error
git clone https://github.com/imageworks/OpenColorIO.git

#My headless build to test core (and plan to later enable the python based Game engine)
#We attempted to build both src trees with:
mkdir newbuild
cd newbuild
cmake -DWITH_ANDROID=ON -DWITH_INTERNATIONAL=OFF -DWITH_PYTHON_INSTALL_NUMPY=OFF -DPYTHON_VERSION=2.7 -DWITH_OPENMP=ON -DWITH_SYSTEM_GLEW=OFF -DWITH_CYCLES=OFF -DWITH_IMAGE_OPENJPEG=OFF -DWITH_X11_XF86VMODE=OFF -DWITH_HEADLESS=ON -DWITH_GAMEENGINE=OFF -DWITH_AUDASPACE=OFF -DWITH_FFTW3=OFF -DWITH_JACK=OFF -DWITH_SDL=OFF -DWITH_OPENAL=OFF -DWITH_CODEC_FFMPEG=OFF -DWITH_CODEC_SNDFILE=OFF -DWITH_X11_XINPUT=OFF -DWITH_INPUT_NDOF=OFF ..

###########################################
#A working mirror for blender.org's src tree
git clone https://github.com/ldo/blender-main.git
git clone https://github.com/ldo/blender-addons.git
I then moved the blender-addons src path to blender-main add-ons

#Result: This will get to around 49% of the build and fail with a dna.c memory alloc bug.
#This may be related to a struct byte alignment issue.

###########################################
#android patched tree
mkdir blender-sc
cd blender-sc
svn --non-interactive --trust-server-cert co https://svn.blender.org/svnroot/bf-blen ... iss_cheese soc-2012-swiss_cheese
svn --non-interactive --trust-server-cert co https://svn.blender.org/svnroot/bf-blen ... ib/android lib/android

#Result: This will get to around 34% of the build and fail with a gpu.c related bug.

###########################################
#Testing Pi wheezy repo dpkg build:
Blender 2.63 (sub 0)
build date: 2012-05-27
build time: 14:12:15
build revision: unknown
build platform: Linux
build type: Release
build c flags: -fopenmp -pipe -fPIC -funsigned-char -fno-strict-aliasing -Wall -Wcast-align -Werror=declaration-after-statement -Werror=implicit-function-declaration -Werror=return-type -Wstrict-prototypes -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter -Wwrite-strings -Wno-error=unused-but-set-variable
build c++ flags: -D__STDC_CONSTANT_MACROS -fopenmp -pipe -fPIC -funsigned-char -fno-strict-aliasing -Wall -Wno-invalid-offsetof -Wno-sign-compare
build link flags: -pthread
build system: CMake

#Result: Segmentation fault with test file confirmed working on host machine.
Blender 2.63 (sub 0)
Build: 2012-05-27 14:12:15 Linux Release
argv[0] = blender
argv[1] = -d
argv[2] = -nojoystick
argv[3] = -noglsl
argv[4] = -noaudio
argv[5] = --disable-autoexec
argv[6] = --factory-startup
argv[7] = --background
argv[8] = test.blend
argv[9] = -o
argv[10] = //file
argv[11] = -F
argv[12] = JPEG
argv[13] = -x
argv[14] = 1
argv[15] = -f
argv[16] = 1
disabling nojoystick
read file
Version 262 sub 4 svn r45955

ordered
OBCube
OBLamp
OBCamera
3246 Segmentation fault

[Metatronin]

Wow! At least you are try to figure it out. Maybe others will help if they can.

[Joel_Mckay]

Update: Still no magic yet...
However, we would appreciate feedback from anyone with a different build of Debian's wheezy libpython3.2.

The info below has eliminated many of the build problems, but one issue remains which I suspect is a type error someplace due to the armhf environment ( libpython3.2_3.2.3-2_armhf.deb ). This same error is exhibited by Debian wheezy "blender" source in addition to the other posted source tree versions like blender.org's svn.

>bt
#0 0x40319940 in PyErr_SetObject () from /usr/lib/libpython3.2mu.so.1.0
#1 0x40316344 in PyErr_Format () from /usr/lib/libpython3.2mu.so.1.0
#2 0x40336c7c in PyType_Ready () from /usr/lib/libpython3.2mu.so.1.0
#3 0x40345d78 in _PyExc_Init () from /usr/lib/libpython3.2mu.so.1.0
#4 0x40346438 in Py_InitializeEx () from /usr/lib/libpython3.2mu.so.1.0
#5 0x00652c30 in BPY_python_start ()
#6 0x0037b140 in WM_init ()
#7 0x003683c8 in main ()

Warning: This takes up quite a bit of space to build, and will unlikely succeed on a 4GB sdcard.

Compiled blender.org's svn source tree with header file issue resolved by Pi's XBMC wiki bug fix.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install openmpi-dev openmpi-bin openmpi-common libopenmpi-dev mpich2 mpich2python python-mpi4py zlib1g-dev libpng12-dev libjpeg-dev libjpeg-progs vlc ffmpeg libsndfile1 fftw3 openexr libopenjpeg-dev python2.7-libtiff libtiff-dev libsdl-dev libboost-dev libopenexr6 libopenexr-dev libjack-dev libsndfile-dev libfftw3-dev libavcodec-dev libavutil-dev libswscale-dev vlc ffmpeg libsndfile libfftw libgles2-mesa liblogsys-dev libarchive12 libaudio2 libavahi-client3 libavahi-common-data libavahi-common3 libboost-date-time1.49-dev libboost-date-time1.49.0 libboost-filesystem-dev libboost-filesystem1.49-dev libboost-filesystem1.49.0 libboost-regex-dev libboost-regex1.49-dev libboost-regex1.49.0 libboost-serialization1.49-dev libboost-serialization1.49.0 libboost-system-dev libboost-system1.49-dev libboost-system1.49.0 libboost-thread-dev libboost-thread1.49-dev libboost-thread1.49.0 libboost1.49-dev fonts-droid libavcodec-extra-53 libavdevice53 libavformat53 libavutil51 libc-dev libc6 libfontconfig1 libfreetype6 libgcc1 libgl1-mesa-swx11 libglew1.7 libglu1-mesa libgomp1 libilmbase6 libjack-jackd2-0 libjpeg8 libopenal1 libopenexr6 libopenjpeg2 libpng12-0 libpython3.2 libsdl1.2debian libsndfile1 libstdc++6 libswscale2 libtiff4 libx11-6 libxi6 python3.2 zlib1g yafaray libilmbase6 libgl1-mesa-glx libgl1-mesa-dri libglapi-mesa libglibide3 libglew-dev python3.2 python3 python3-dev python3-numpy libpcre3 libpcre3-dev libxml2 libxi-dev gettext llvm-dev libopenal-dev libsdl-dev

sudo apt-get install build-essential autoconf ccache gawk gperf mesa-utils zip unzip
sudo apt-get install autotools-dev comerr-dev dpkg-dev libalsaplayer-dev \
libapt-pkg-dev:armhf libasound2-dev:armhf libass-dev:armhf libatk1.0-dev \
libavahi-client-dev libavahi-common-dev libavcodec-dev libavformat-dev \
libavutil-dev libbison-dev:armhf libbluray-dev:armhf libboost1.49-dev \
libbz2-dev:armhf libc-dev-bin libc6-dev:armhf libcaca-dev libcairo2-dev \
libcdio-dev libclalsadrv-dev libcrypto++-dev libcups2-dev libcurl3-gnutls-dev \
libdbus-1-dev libdbus-glib-1-dev libdirectfb-dev libdrm-dev libegl1-mesa-dev \
libelf-dev libenca-dev libept-dev libevent-dev libexpat1-dev libflac-dev:armhf \
libfontconfig1-dev libfreetype6-dev libfribidi-dev libgconf2-dev \
libgcrypt11-dev libgdk-pixbuf2.0-dev libgl1-mesa-dev libgles2-mesa-dev \
libglew-dev:armhf libglewmx-dev:armhf libglib2.0-dev libglu1-mesa-dev \
libgnome-keyring-dev libgnutls-dev libgpg-error-dev libgtk2.0-dev libhal-dev \
libhunspell-dev:armhf libice-dev:armhf libicu-dev libidn11-dev libiso9660-dev \
libjasper-dev libjbig-dev:armhf libjconv-dev libjpeg8-dev:armhf libkrb5-dev \
libldap2-dev:armhf libltdl-dev:armhf liblzo2-dev libmad0-dev libmicrohttpd-dev \
libmodplug-dev libmp3lame-dev:armhf libmpeg2-4-dev libmysqlclient-dev \
libncurses5-dev libnspr4-dev libnss3-dev libogg-dev:armhf libopenal-dev:armhf \
libp11-kit-dev libpam0g-dev:armhf libpango1.0-dev libpcre++-dev libpcre3-dev \
libpixman-1-dev libpng12-dev libprotobuf-dev libpthread-stubs0-dev:armhf \
libpulse-dev:armhf librtmp-dev libsamplerate0-dev:armhf \
libsdl-image1.2-dev:armhf libsdl1.2-dev libslang2-dev:armhf \
libsm-dev:armhf libsmbclient-dev:armhf libspeex-dev:armhf \
libsqlite3-dev libssh-dev libssh2-1-dev libssl-dev libstdc++6-4.6-dev \
libtagcoll2-dev libtasn1-3-dev libtiff4-dev libtinfo-dev:armhf libtinyxml-dev \
libts-dev:armhf libudev-dev libv8-dev libva-dev:armhf libvdpau-dev:armhf \
libvorbis-dev:armhf libvpx-dev:armhf libwebp-dev:armhf libwibble-dev \
libx11-dev:armhf libx11-xcb-dev libxapian-dev libxau-dev:armhf \
libxcb-glx0-dev:armhf libxcb-render0-dev:armhf libxcb-shm0-dev:armhf \
libxcb1-dev:armhf libxcomposite-dev libxcursor-dev:armhf libxdamage-dev \
libxdmcp-dev:armhf libxext-dev:armhf libxfixes-dev libxft-dev libxi-dev \
libxinerama-dev:armhf libxml2-dev:armhf libxmu-dev:armhf libxrandr-dev \
libxrender-dev:armhf libxslt1-dev libxss-dev:armhf libxt-dev:armhf \
libxtst-dev:armhf libxxf86vm-dev libyajl-dev libzip-dev linux-libc-dev:armhf \
lzma-dev mesa-common-dev python-dev python2.7-dev x11proto-composite-dev \
x11proto-core-dev x11proto-damage-dev x11proto-dri2-dev x11proto-fixes-dev \
x11proto-gl-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev \
x11proto-record-dev x11proto-render-dev x11proto-scrnsaver-dev \
x11proto-xext-dev x11proto-xf86vidmode-dev x11proto-xinerama-dev xtrans-dev \
zlib1g-dev:armhf

sudo cp -R /opt/vc/include/* /usr/include
sudo cp /opt/vc/include/interface/vcos/pthreads/* /usr/include/interface/vcos

sudo ln -fs /opt/vc/lib/libEGL.so /usr/lib/libEGL.so
sudo ln -fs /opt/vc/lib/libEGL.so /usr/lib/arm-linux-gnueabihf/libEGL.so
sudo ln -fs /opt/vc/lib/libEGL.so /usr/lib/arm-linux-gnueabihf/libEGL.so.1
sudo ln -fs /opt/vc/lib/libEGL_static.a /usr/lib/libEGL_static.a
sudo ln -fs /opt/vc/lib/libEGL_static.a /usr/lib/arm-linux-gnueabihf/libEGL_static.a
sudo ln -fs /opt/vc/lib/libGLESv2.so /usr/lib/libGLESv2.so
sudo ln -fs /opt/vc/lib/libGLESv2.so /usr/lib/arm-linux-gnueabihf/libGLESv2.so
sudo ln -fs /opt/vc/lib/libGLESv2.so /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2
sudo ln -fs /opt/vc/lib/libGLESv2_static.a /usr/lib/libGLESv2_static.a
sudo ln -fs /opt/vc/lib/libGLESv2_static.a /usr/lib/arm-linux-gnueabihf/libGLESv2_static.a
sudo ln -fs /opt/vc/lib/libbcm_host.so /usr/lib/libbcm_host.so
sudo ln -fs /opt/vc/lib/libbcm_host.so /usr/lib/arm-linux-gnueabihf/libbcm_host.so
sudo ln -fs /opt/vc/lib/libvchiq_arm.a /usr/lib/libvchiq_arm.a
sudo ln -fs /opt/vc/lib/libvchiq_arm.a /usr/lib/arm-linux-gnueabihf/libvchiq_arm.a
sudo ln -fs /opt/vc/lib/libvchiq_arm.so /usr/lib/libvchiq_arm.so
sudo ln -fs /opt/vc/lib/libvchiq_arm.so /usr/lib/arm-linux-gnueabihf/libvchiq_arm.so
sudo ln -fs /opt/vc/lib/libvcos.a /usr/lib/libvcos.a
sudo ln -fs /opt/vc/lib/libvcos.a /usr/lib/arm-linux-gnueabihf/libvcos.a
sudo ln -fs /opt/vc/lib/libvcos.so /usr/lib/libvcos.so
sudo ln -fs /opt/vc/lib/libvcos.so /usr/lib/arm-linux-gnueabihf/libvcos.so

Building a headless standalone portable Blender version.
* Disabled blender's GPU accelerated rendering engine features

mkdir blender3d
cd blender3d
svn co https://svn.blender.org/svnroot/bf-blen ... nk/blender
cd blender
mkdir newbuild
cd newbuild
cmake -DWITH_MEM_JEMALLOC=OFF -DWITH_LIBMV=OFF WITH_LLVM=ON -DWITH_IK_ITASC=ON -DWITH_MOD_FLUID=ON -DPYTHON_VERSION=3.2 -DWITH_INTERNATIONAL=OFF -DWITH_PYTHON_INSTALL_NUMPY=ON -DWITH_OPENMP=ON -DWITH_SYSTEM_GLEW=OFF -DWITH_CYCLES=OFF -DWITH_IMAGE_OPENJPEG=ON -DWITH_X11_XF86VMODE=ON -DWITH_HEADLESS=ON -DWITH_GAMEENGINE=ON -DWITH_AUDASPACE=ON -DWITH_FFTW3=ON -DWITH_JACK=ON -DWITH_SDL=ON -DWITH_OPENAL=ON -DWITH_CODEC_FFMPEG=OFF -DWITH_CODEC_SNDFILE=ON -DWITH_X11_XINPUT=ON -DWITH_INPUT_NDOF=ON -DWITH_BUILTIN_GLEW=OFF -DCMAKE_C_FLAGS:STRING=" -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fopenmp -pipe -fPIC -funsigned-char -fno-strict-aliasing -Wall -Wcast-align -Werror=declaration-after-statement -Werror=implicit-function-declaration -Werror=return-type -Wstrict-prototypes -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter -Wwrite-strings -Wno-error=unused-but-set-variable " -DCMAKE_CXX_FLAGS:STRING=" -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fopenmp -pipe -fPIC -funsigned-char -fno-strict-aliasing -Wall -Wno-invalid-offsetof -Wno-sign-compare " ..
make;make install;

Takes a few hours to compile.... even if clocking 950MHz .

Testing in headless console render mode will still throw an exception.

blender -d --debug-fpe --nojoystick --noglsl --noaudio --disable-autoexec --factory-startup --background test.blend -o //file -F JPEG -x 1 -f 1

[Jim JKla]

Have you had any more sucess with this yet?

[Joel_Mckay]

Have you had any more success with this yet?

Unfortunately, I've had to focus on other projects this month, but had looked at the generic OpenGL 2.0 wrapper for OpenGL ES 2.0 to port over some games/CAD to the Pi.
http://code.google.com/p/gl-wes-v2/

However, quite some time ago a similar seg fault issue was fixed in the Ubuntu repositories version of that python package. After people finish fixing the current libpython3.2_3.2.3-ubuntu3.2 security bug, I intend to port this dpkg patch level at some point to attempt rebuilding Blender.
The armhf lib source and patch I intend to use are available with this link if someone wants to test a blender build: https://launchpad.net/~ubuntu-security/ ... ld/3916360

[MikeHalliday]

Any movement on this project?

Very interested in a headless blender node on the rPi!

Interesting take on the whole render farm scenario!

Mike.

[gregor3000]

why are porgrammes in repositories if they do not work on the computer?

The whole idea of repositories is that all programmes there are tested, safe (&stable?!), and work on the operating system.

If they do not work on Pi (as they are not compiled for arm or simply do not support Pi) why are they in the Pi's repositories?

[ghans]

Propably because they do not fail at build-time ,
but nobody has time to test 20 000 packages for their
"real world" usability. (You can get VLC to "watch" videos ,
and gnash is there too).


ghans

[Metatronin]

There is an android version that works on tablets quite well now, maybe that is a possibility for the open GLES as far as ported repositorys? Even a scaled down version that only modeled and textured would be nice, simply so 3d development for games programing or any 3d app dev. I'm working on some content already, but would have liked to make mini tuts on making models and texturing them so people could branch out and explore for themselves.

[dragonrebel]

Hello, I was wondering if anybody has tried networking rendering with the raspberry pi as master.

http://wiki.blender.org/index.php/Doc:2 ... /Netrender

The master seems to do no rendering on itself, so the Pi may be fit for this. I attempted this myself by making a blender file on my pc where I set everything up as master, save the file and then try to run it on blender as specified in the above wiki (blender -b Master.blend -a), however this caused blender to fail with "Segmentation fault" as error.
If anybody else had more succes with this, I would love to hear where I went wrong.

[JxPond]

There's quite a bit that has to be sorted if Blender will ever be able to run on the Pi. Right now we don't have an accelerated GUI in Wheezy as everything is done via the ARM.

Blender really needs a decent workstation to be useful. One that has more RAM than the Pi is able to provide.

That's not to say I don't want a 3D modeler on the Pi, but I think something more along the lines of Milkshape or Wings3D would be more appropriate and even then it's going to have to be GPU accelerated to be of use.

Something that you could build small textured objects and the incorporate them using Pi3D for example.

[spock]

i also think blender on a raspberry pi 2 would be nice.

i run blender on some very old pcs (p3, 512mb ram,...) and it runs surprisingly well.

of course it wouldn't be great for rendering complex animations but for working on somewhat simple scenes i could imagine that it would run quite ok on a rasperry pi 2.

[Jim JKla]

It would be fantastic to get the game engine to work again unlikely.

[shugs81]

it would be awesome as a little render node.... obvs not gonna be the fastest but would much rather a farm of 15 of them running for 2 days than my overpowered pc running for an hour would probably be cheaper to run too!!!

[Jim JKla]

For the cost of 15 RPi's you could buy an awsome Graphics card to use the GPU for renderering and thats not to detract from the little RaspberryPi allotment (it's not really a farm) being awsome to behold.

[marcorama]

How about starting blender in the console with $blender -b to make it run in the background.
I really don´t know wether Blender needs openGL while running in the background,if not,networkrendering is a possibilty.with a Pi.
Keep in mind that GPU-rendering isn´t available for Blender internal and some cycles materials,so building a ´rederfarm´ with PI´s is
a viable option and might be a better choice than buying a videocard.

[shugs81]

My reasoning for it is that I've just hired an art studio which is a converted office building and I don't think I'd wanna fork out loads of cash on a fancy render farm for there... I would mainly be using it as my mobile modelling machine is a surface pro... so I could use the farm to take most of the strain....

[Jim JKla]

I say go for it and let us know how you get on.