SGI: Computer Graphics

Pixie for IRIX - Page 2

competentcompton
Who joined Aug. 2, 2006, 2:06 a.m.
and authored 240 notes

Wrote the following at April 15, 2010, 4:31 a.m...

Well,

It seems that this has become a discussion about BMRT. While I agree that BMRT is a fine tool I wanted to give some simple stats.

I am rendering a simple surface of 1000x1000 points using a fresnel shader on a 600Mhz fuel. The results are as follows

using BMRT it took 660 seconds to render using rendrib.

With pixie using rndr it too 59 seconds. Neither was multi-threaded (no point single cpu fuel in both cases) but pixie was 10x faster for this example.

I know that metrivs are a dung hill. But facts speak for themselves.

Cheers

competentcompton
Who joined Aug. 2, 2006, 2:06 a.m.
and authored 240 notes

Wrote the following at April 15, 2010, 4:43 a.m...

I think that 59s versus 660s is a very nice metric which demonstrates that a more modern tool such a pixie is good for us old SGI die hards. Lets face it we do not have oodles of spare CPU bandwidth to splash around. For this reason I would think that this pixie port is interesting. If nothing else it is a good replacement for BMRT. I was somewhat overwhelmed by the BMRT resistance as everyone on the thread started to talk about BMRT as opposed to pixie.

I think that this port seems to be working well and it certaintly has some pretty impressive performance so far.

Good pedigree I would say.

Cheers

rschultz
Who joined June 8, 2009, 11:49 p.m.
and authored 5 notes

Wrote the following at April 21, 2010, 10:39 p.m...

Greetings,

I have successfully built a new sdr shader parsing plugin for Ayam
with the provided Pixie port. So, you can feed Pixie from Ayam now:
http://ayam.sourceforge.net/download.html

kind regards,
Randolf

GeneratriX
Who joined Oct. 21, 2003, 1:07 a.m.
and authored 4224 notes

Wrote the following at April 23, 2010, 7:56 a.m...

rschultz wrote:

Very interesting! I'll try both very soon! Thanks for the nice work!

_________________
Oh!, let me write that!

Octane / Dual Head

http://twitter.com/GeekTronixShop

paulfred
Who joined May 22, 2008, 4:01 a.m.
and authored 85 notes

Wrote the following at May 2, 2010, 12:33 a.m...

Could someone please re-up the download link.
It doesn't seem to work anymore.

_________________
:Fuel:

Apple iMac, IBM p275, IBM p285, IBM 43p140, HP 2133, Sun Fire 280R, Sun Ultra1 clone (300Mhz), Sun Ultra2 (2x400 MHz), HP C8000, Fujitsu Primepower 250, HP rx4640

competentcompton
Who joined Aug. 2, 2006, 2:06 a.m.
and authored 240 notes

Wrote the following at May 19, 2010, 1:19 a.m...

paulfred

check you pm

Cheers

Sacrifist
Who joined March 18, 2005, 3:42 a.m.
and authored 88 notes

Wrote the following at July 3, 2010, 9:04 p.m...

Hi compcomp, do you have a tardist handy? Is there any chance for me to grab a copy? I'm on study break and just got my O2 and Octane working!

Simon.

sgienthu
Who joined Jan. 15, 2011, 2:24 p.m.
and authored 12 notes

Wrote the following at Feb. 25, 2012, 2:26 p.m...

Hello Nekochaners!

I'm a spanish fan of Silicon Graphics computers and my hobby is generate computer graphics with these amazing machines.

I'm trying to find an IRIX implementation of Pixar's Pixie on the inet, but I can't find it.

I found this Nekochan topic (ucp.php?i=pm&mode=view&f=0&p=10874165), but when I try to download the file "pixie.tar.gz" I get next error:

"The selected attachment does not exist anymore.

The file ./../files/1653_9dfb5dee83351f1975a503a8f2776472 does not exist."

Can anybody tell me where I can find it or give me another link with Pixie binary?

Thank you,
sgienthu

_________________
:Indy:

vishnu
Who joined March 18, 2007, 2:25 p.m.
and authored 1159 notes

Wrote the following at Feb. 25, 2012, 11:31 p.m...

Nobody's picked up the ball on this evidently...

_________________
Project:
Movin' on up, toooo the east side
Plan:
World domination! Or something...

Oskar45
Who joined Dec. 5, 2005, 2:35 a.m.
and authored 1949 notes

Wrote the following at Feb. 26, 2012, 10:52 a.m...

Hmm, sources for several versions are available at http://sourceforge.net/projects/pixie/files/pixie/ . But I've no idea about whether one of them compiles properly...

_________________
For aliens we're aliens.

hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8704 notes

Wrote the following at Feb. 26, 2012, 10:57 p.m...

Oskar45 wrote:

But I've no idea about whether one of them compiles properly...

competent, what did you do to fix this ?

Code:

cc-1020 CC: ERROR File = algebra.h, Line = 88

The identifier "uint32_t" is undefined.

uint32_t        i;

^

cc-1020 CC: ERROR File = algebra.h, Line = 91

The identifier "uint32_t" is undefined.

union { float f; uint32_t i; } u;

^

cc-1020 CC: ERROR File = algebra.h, Line = 110

The identifier "uint32_t" is undefined.

union { float f; uint32_t i; } u;

^

3 errors detected in the compilation of "algebra.cpp".

Adding

Code:

#include <stdint.h>

did not do the trick. Apparently this has been a problem for a while ...

http://sourceforge.net/tracker/?func=de ... tid=491092

a thousand eyes, a thousand hands but still no solution ....

Oskar45
Who joined Dec. 5, 2005, 2:35 a.m.
and authored 1949 notes

Wrote the following at Feb. 27, 2012, 2:08 a.m...

@hamei: might not be the solution, but I'd try to do a grep over /usr/include [and subdirs] to see whether uint32_t is defined somewhere else as well. Sorry, can't check that now as I don't have access to my boxes.

_________________
For aliens we're aliens.

hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8704 notes

Wrote the following at Feb. 27, 2012, 2:20 a.m...

Oskar45 wrote:

Thanks, but actually I don't care about Pixie. I just thought I'd run it through quickly and if it built easy, what the heck. But the one set of bugs noted above was from foetz, who is about ten thousand times smarter than me, and he didn't solve the problem. Plus I have since found several other non-productive discussions between the Pixie guys and Randolf Schultz, who does Ayam. It also (apparently) crashes later on when you try to use it, even if you get it to build. I wonder how competent got it going ? CC, where's you at, boy ?

Anyway, I'm back to something I hope will be more useful but thanks for the pointer ....

Oskar45
Who joined Dec. 5, 2005, 2:35 a.m.
and authored 1949 notes

Wrote the following at Feb. 27, 2012, 3:06 a.m...

@hamei: sorry for bothering you again. Can you try once more but replace <uint32_t i;> by <unsigned long int i;>? Thanks.

_________________
For aliens we're aliens.

hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8704 notes

Wrote the following at Feb. 27, 2012, 4:53 a.m...

Oskar45 wrote:

@hamei: sorry for bothering you again. Can you try once more but replace <uint32_t i;> by <unsigned long int i;>? Thanks.

Ees no problem, senor. Nice work, we got past the first three errors ! My one question about that is these are apparently routines for "faster" math but they seem to be integer-centric. I bet they aren't really "faster" on MIPS processors ...

Anyway, now we get

Code:

cc-3700 CC: WARNING File = ../ri/atomic.h, Line = 144

#warning directive: Atomic Instructions are not supported on this platform,

defaulting to generic implementation

#warning Atomic Instructions are not supported on this platform, defaulting to generic implementation

^

cc-3168 CC: ERROR File = ../ri/atomic.h, Line = 149

A name followed by "::" must be a class or namespace name.

osLock(CRenderer::atomicMutex);

^

cc-3168 CC: ERROR File = ../ri/atomic.h, Line = 151

A name followed by "::" must be a class or namespace name.

osUnlock(CRenderer::atomicMutex);

^

cc-3168 CC: ERROR File = ../ri/atomic.h, Line = 157

A name followed by "::" must be a class or namespace name.

osLock(CRenderer::atomicMutex);

^

cc-3168 CC: ERROR File = ../ri/atomic.h, Line = 159

A name followed by "::" must be a class or namespace name.

osUnlock(CRenderer::atomicMutex);

^

4 errors detected in the compilation of "precomp.cpp".

If you have any ideas I'll be happy to plug them in. Even if this isn't something I want, seems like someone might be happy to have it.

Oskar45
Who joined Dec. 5, 2005, 2:35 a.m.
and authored 1949 notes

Wrote the following at Feb. 27, 2012, 6:53 a.m...

@hamei: Actually, to get over the first three errors is trivial as uint32_t is simply a synonym. Try to do c99 instead of cc.

_________________
For aliens we're aliens.

sgienthu
Who joined Jan. 15, 2011, 2:24 p.m.
and authored 12 notes

Wrote the following at Feb. 27, 2012, 10:04 a.m...

Thank you hamei and Oskar45 for you effort!

Hope at last we get a Pixie binary to render with.

Regards,
sgienthu

_________________
:Indy:

bplaa.yai
Who joined March 26, 2008, 11:04 a.m.
and authored 302 notes

Wrote the following at Feb. 27, 2012, 12:25 p.m...

hamei wrote:

Anyway, now we get

Code:

cc-3700 CC: WARNING File = ../ri/atomic.h, Line = 144

#warning directive: Atomic Instructions are not supported on this platform,

defaulting to generic implementation

#warning Atomic Instructions are not supported on this platform, defaulting to generic implementation

^

cc-3168 CC: ERROR File = ../ri/atomic.h, Line = 149

A name followed by "::" must be a class or namespace name.

osLock(CRenderer::atomicMutex);

^

If you have any ideas I'll be happy to plug them in. Even if this isn't something I want, seems like someone might be happy to have it.

This is where "porting" comes into play (read : rather than #ifdefing and #including

). I didn't have a look at the sources, but I guess atomic.h contains some OS specific code (osLock, osUnlock, ...) that have to be implemented for Irix. If you're lucky, maybe you can reuse another OS implementation. If you're not, you may have to write some Irix specific code, and/or use compiler intrinsics for atomic operations.

Edit : attached a patch to make pixie 2.2.6 build, but I don't have any knowledge about it to test the result...

_________________
:Onyx2:

canavan
Who joined July 21, 2003, 5:19 a.m.
and authored 687 notes

Wrote the following at Feb. 27, 2012, 4:27 p.m...

You patch is way better than mine, but how do you configure/compile the whole thing without CC complaining

Code:

cc-1035 CC: ERROR File = /usr/include/stdint.h, Line = 5

#error directive:  This header file is to be used only for c99 mode

compilations

#error This header file is to be used only for c99 mode compilations

^

My inelegant but working neko_pixie tardist is in incoming, just help yourself to the dist files etc. if you want to make a better .tardist.

hamei
Who joined Feb. 24, 2004, 4:10 p.m.
and authored 8703 notes

Wrote the following at Feb. 27, 2012, 11:03 p.m...

bplaa.yai wrote:

This is where "porting" comes into play (read : rather than #ifdefing and #including

)

I'd be happy if I could do #including and #ifdeffing

Youse guys are okay .... grazie, grazie from all of us non-programmers.