Nekochan Net

@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.

Thank you hamei and Oskar45 for you effort!

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

Regards,
sgienthu

_________________

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...

_________________

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

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.

I'd be happy if I could do #including and #ifdeffing Youse guys are okay .... grazie, grazie from all of us non-programmers.

I've rebuilt with bplaa.yai's patch in the meantime. A new neko_pixie-2.2.6.tardist is in /incoming. To test, grab an example .rib file from http://www.renderpixie.com/pixiewiki/Ex ... B_Examples and drop it on rndr in the Applications page of Icon Catalog. You may have to set PIXIEHOME=/usr/nekoware/lib/Pixie (or whatever may be the correct value...) in your environment.

Great!

I'm going to try it!

_________________

Ops!

I try to render a basic ".rib" file but I'm getting next error:



What's going on with file.so?

_________________

I didn't install the tardist - I'm not a Maya guy - but from a simple command using some of the examples canavan pointed to, the program drew a rendered scene in a window on the desktop. You might try running < rndr foofoo.rib > from a command line to see what's happening ...

Here my results:

File 1: Media:pmap_render_pass0.rib

http://flic.kr/p/bzFvYk

File 2: Media:pmap_render_pass1.rib

http://flic.kr/p/bzFw4D

File 3: Media:pmap_render_pass2.rib

http://flic.kr/p/bmLDqU

Sorry no good news...

_________________

First of all, use "snapshot" to take screenshots. Since you're apparently getting the "Atomic operations are not supported on this system, consider leaving a note in Sourceforge about your platform" message, you need to upgrade. re-download neko_pixie from beta and install that.

Here's a trick you will like : when you get a winterm like that, put your mouse cursor at the end of what you want. Depress the left mouse button and swipe to the left up to the beginning of what you want. This will highlight all the test you "selected". (Works the other way also but I am right-handed.) Release the left mouse button (aka lmb). Now drive the mouse cursor over the desktop or an open directory display-window (or even a closed one's icon). Press the middle mouse button and it will drop a text file onto your desktop. It will be named "Pasted Text" and you can then rename it.

Now you can paste that into any application you want, such as the message window on your web browser.

Beware : after you get used to this you will become addicted to it. Windows does not have this feature.

@canavan
Sorry my SGI doesn't have Inet/LAN connection because router issues... I'm working on this too. This is the reason I sent you pictures...

Ok, I updated the Pixie version with neko_pixie-2.2.6.tardist file version 02/28/2012 03:52 from nekoware.

The Atomic operations message has disappeared, but file.so implementation message error persist...

Here my environment variables and results:

http://flic.kr/p/bzUezB

Can be a X11 compatiblility problem?

@hamei
Thank you for you trick it is very useful and adictive...

_________________

At last I found it!

It was a problem with library libpng.so.3 version. I have just updated it and now Pixie runs.

Thanks to everybody for your help!

_________________

Did you update from /current or is that a new libpng from /beta ? If you'd give the neko_libpng-1.2.47.tardist in /beta a try and make a post about it in Development, that would be a help to the Nekoware Updating Program.

Thanks for reporting back, anyhow There are a few users here who could take a lesson from your good manners. And I mean the word "users" literally