Thanks for the nice toy Martin !Just tested it on the Onyx2 IR2E and the Onyx IP, works great on both. Just a note : it looks a bit dark (eg. I don't see anything until I hit space), I'm not sure if it's related to my gamma settings (I use gamma 1.0 on my sgis)...

I vaguely remember reading something about floating-point bugs in the 350MHz CPU's, which made them unsuitable for e.g. Maya. Since the O2 uses the main CPU for geometry transformations, it could be triggered by an OpenGL app.

ShadeOfBlue wrote:I vaguely remember reading something about floating-point bugs in the 350MHz CPU's, which made them unsuitable for e.g. Maya. Since the O2 uses the main CPU for geometry transformations, it could be triggered by an OpenGL app.

Right, that's why SGI recalled the RM7K/350MHz CPUs. Kind of interesting to see it pop up now though, and equally interesting that the faster RM7Ks aren't affected.

ShadeOfBlue wrote:I vaguely remember reading something about floating-point bugs in the 350MHz CPU's, which made them unsuitable for e.g. Maya. Since the O2 uses the main CPU for geometry transformations, it could be triggered by an OpenGL app.

Right, that's why SGI recalled the RM7K/350MHz CPUs. Kind of interesting to see it pop up now though, and equally interesting that the faster RM7Ks aren't affected.

Looks like it was a RM7000A problem. The 600MHz hobbyist upgrades use the RM7000C.

Both apps (Die Planeten, Chromawaves) make heavy use of trigonometric functions like sin() and cos(). I have sent hamei a test version of the demo program to proof it's not a software glitch. I' m still not sureif it's a hardware bug. 99.999% of all bugs are software related (that's my experience, at least).

Best regards,Martin

P.S. thank you very much for reporting about my programs on the start page!

bplaa.yai wrote:Thanks for the nice toy Martin !Just tested it on the Onyx2 IR2E and the Onyx IP, works great on both. Just a note : it looks a bit dark (eg. I don't see anything until I hit space), I'm not sure if it's related to my gamma settings (I use gamma 1.0 on my sgis)...

Run "./chromawaves -auto" if you want the see waves from the beginning.

running fixpath didn't fix itI linked /usr/lib32/libglut.so to /usr/nekoware/lib/libglut.so which was probably a terrible idea, but I'm certainly no unix expert and it worked. It works great, actually. Maybe in the new version it can look for libglut.so in /usr/nekoware/lib/? or is it supposed to do that and my system is slightly fubared?