3D Rendering on Raspberry Pi using Aqsis renderer

anoop a k:

checkout my rendering experiments using Raspberry Pi

Originally posted on Raspberryments:


The first thing I do once I buy a new computer is to put it to test to see how it performs when it comes to rendering complex 3d scene. Being a technical artist, its our job to innovate the most efficient workflow to get the best out of the available resources. So what If a 3d rendering task is thrown at the Raspberry Pi?

I decided to go with Aqsis, a 3D rendering solution adhering to RenderMan standard. Why Aqsis? Because its Open Source. So its just a matter of few hours to get Aqsis built for your distro running on Raspberry Pi (Raspbian in my case). It took approximately 4 hours for me to build Aqsis from source, including the time taken to build libTiff, one of the package dependencies for Aqsis. The rest of the dependent packages were readily available for Raspbian and it took only a…

View original 599 more words

PyQt4 for Maya2013 on Windows 7 x64

For windows users, PyQt 4.9.1 built against Qt4.7.1 and SIP4.13.2 for Maya2013 x64, can be downloaded  here . Links to the respective sources are included below.

Update: Have updated an executable to make the installation easier. You may download it here

Qt 4.7.1 source

SIP source

PyQt source

Building PyQt for Maya 2012 ( Linux x64 )

                   

SIP needs to be built prior to building PyQt.

Download SIP from here

Maya 2012 uses Qt 4.7.1.

Download it from here

Download PyQt from here

First step is to build qt from source. Extract the tarball and CD in to the directory

./configure

While running configure, if you get the following error

Basic XLib functionality test failed!

You might need to modify the include and library search paths by editing

QMAKE_INCDIR_X11 and QMAKE_LIBDIR_X11 in /home/anoop/apps/sources/qt-everywhere-opensource-src-4.7.1 /mkspecs/linux-g++-64.

install teh libXext development package. I used zypper to install the package from the web

zypper install xorg-x11-libXext-devel

executing the configure after the installation gave the following error

cannot find -lXrender

this was happening because configure couldn’t find libXrender.so. This can be fixed by creating a symlink to libXrender.so.1 in the /usr/lib64 directory

ln -s /usr/lib64/libXrender.so.1 /usr/lib64/libXrender.so

After successful configuration run the following to install Qt to /usr/local/Trolltech/Qt-4.7.1 directory

make

make install

Building SIP

Extract the SIP zip archive to /home/username/SIP

cd /home/username/SIP

After setting the variables, run the following

/usr/autodesk/maya2012/bin/mayapy configure.py

make

make install

Building PyQt

Extract the archive to /home/username/PyQt-x11-gpl-4.7.4

cd PyPyQt-x11-gpl-4.7.4

/usr/autodesk/maya2012/bin/mayapy configure.py -q /usr/local/Trolltech/Qt-4.7.1/bin/qmake

make -j4

make install

PyQt4 for Maya2012 on Windows 7 x64

For windows users, PyQt 4.8.5 built against Qt4.7.1 and SIP4.12.4 for Maya2012 x64.can be downloaded  here . And like I mentioned in the last post, links to the respective sources are included below.

Qt 4.7.1 source

SIP source

PyQt source

PyQt4 for Maya2012 on openSUSE11.4 ( Linux x64 )

 PyQt 4.8.5 built against Qt4.7.1 and SIP4.12.4 for Maya2012 x64. download it here . In case you want to build  PyQt on your own you can download the sources here.

Qt 4.7.1 source

SIP source

PyQt source

Houdini Demoreel 2011

Houdini Demoreel 2011 featuring some of the most amazing visual effects created using Houdini including the recent work done by  Rhythm and Hues in feature films Hop, Yogi Bear, Mr.Poppers Penguins, X-Men: First Class, Red Riding Hood. Enjoy!

Building OpenEXR libraries on Linux ( openSUSE 11.4 )

 

OpenEXR is a high dynamic-range (HDR) image file format developed by Industrial Light & Magic for use in computer imaging applications. In order to develop plugins and tools that can handle OpenEXR file formats, you need to have the OpenEXR libraries built for your OS.

I had been not using Maya for the past few months since I have been dealing with proprietary applications used at my workplace. So I decided to continue work on Maya whenever I get back home after the days work. And what better way to start things all over again than starting with the API.

So I made a checklist of the libraries and other tools which I need to get built to start working on the same.So here I was building OpenEXR on openSUSE 11.4 and I stumbled across few things here and there which I felt would be valuable if I share with you all.

Building OpenEXR on you OS requires the zlib and ilmbase libraries which has to be linked at the time of configuring.So the first task is to get zlib and ilmbase libraries built on your machine.
I had my libraries installed in my sandbox folder which is /usr/local/sandbox referred by environment variable $SANDBOX. In case you have installed in locations other than standard paths like(/usr/include and /usr/lib) you need to make the build aware of the same.

setting the the environment variable PKG_CONFIG_PATH to $SANDBOX/lib/pkgconfig will let OpenEXR get the package info regarding zlib and ilmbase.

./configure –prefix $SANDBOX LDFLAGS=-L$SANDBOX/lib CPPFLAGS=-I$SANDBOX/include

make

While executing make if you come across the following error

main.cpp:195:28: error: ‘strcmp’ was not declared in this scope
make[1]: *** [main.o] Error 1
make[1]: Leaving directory `/home/anoop/apps/sources/openexr-1.6.1/exrenvmap’
make: *** [all-recursive] Error 1

you can fix it by including

#include <string.h>

in the header file list of main.cpp in both exrmaketiled and exrenvmap dirs.

and then execute

make install

First glimpse of new RHYTHM AND HUES Website

www.rhythm.com

Recommended PC Configuration for CG Artists – May 2011

Back to blogging again! I had moved in to a new apartment and my ISP turned out to be too inefficient with the shifting process, making me wait for more that 20 days to get the connection shifted to my new place. And on the professional side, I was pretty much occupied with the current feature productions happening in the studio.

But in the mean time, I got a chance to dig in to the latest computer hardware out there, to help out my friend with a new configuration for home. My search stumbled across a few components which I felt would do justice to the kind of work we deal with, on a day to day basis.

Hence thought of sharing the configuration with you in case some of you find it useful. So here it goes…

Intel Core i7 2600K Sandy Bridge 3.4GHz approx 16500 INR

Asus P8P67 PRO approx 12600 INR

Gskill Sandy Bridge 16GB 1600 DDR3 approx 10000 INR

Corsair 1000HX approx 15000 INR

Cooler Master CM690 II Advanced approx 5500 INR

2 x Dell Professional 2311H 23-inch widescreen monitor 26000 INR

MSI N580GTX  Lightning approx 30000 INR

2 x WD 1TB 6Gbps SATA3 approx 9400 INR

Corsair CSSD F80GBP2 BRKT 80GB SSD force series approx 10000 INR

Total approx 1,34,700 INR

Disclaimer: Please note that the configuration suggested is based on personal experience and does not guarantee in anyways high performance for all kinds of applications available on the market. The individual user experience may vary depending on the resources demanded by various applications under different working environments. The approximate prices listed are based on market study and may vary depending on different factors and hence are not supposed to considered as final price listings.

Setting MARI_CACHE Locations outside MARI

The MARI_CACHE environment variable can be used to specify the cache location from outside Mari. This can be one or several directories. If this variable is not set Mari prompts you where to store the cache files when you first launch it

I had selected the cache location from the user interface after starting up Mari. But later I planned to use another location and hence deleted the directory. The next time I tried starting Mari, I was welcomed with a message

/usr/local/bin/mari: line 35: 13275 Aborted (core dumped) $currentPath/bin/MriBin $@ &>${mariLog}

The MariLog.txt clearly indicated the crash was happening due to the missing file path. Since the configuration was saved in the first startup instance, setting the environment variable also didn’t seemed to help me run Mari on my user account.

Debug : [ MriApplication.cpp: 352] : Cache Location ‘/mariCache’ not exist
MriBin: MriDataBlockManager.cpp:233: bool MriDataBlockManager::setup(const QStringList&, qint64, int): Assertion `false’ failed.
Cannot Create cache root at /mariCache

The workaround is to delete the CacheLocations.ini file which saved under the directory /home/user/.config/TheFoundry . Or you can even create a new folder and point the path to your new directory

[CacheRoots]
1Path=/scratch/cache
size=1

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: