Any known problems with Performer on RE IIs?

New Message Reply Date view Thread view Subject view Author view

Cory Tsang (ch-tsang++at++uiuc.edu)
Thu, 12 Jun 1997 16:45:26 -0500 (CDT)


Hi,

I've been having a problem with Performer when running on Onyx RE^2s.

Basically I can compile my program on a machine which is a 4 processor
(R4400 150MHZ IP19 processors) Onyx RE^2 running IRIX 5.3 and run it fine
on an IMPACT system, but if I run it on the Onyx, itself, it doesn't
display. This is the strangest instance since the binary was compiled on
the Onyx and only works on an IMPACT. Both of these systems have version
2.0 of performer_eoe and performer_dev as specified in the FAQ.

I am experiencing the same problems on two 8 processor (R10k 194MHZ IP25
processors) Onyx IRs running 6.2. These machines, have performer version
2.1 for eoe and dev as specified by the FAQ, too. These aren't good tests
since the program had to be recompiled.

To clarify, a bit, the "program" is actually an AVS module and I'm trying
to display into a CAVE.

The one case where things work is in the CAVE simulator, but since the
IMPACT can't drive the CAVE, I haven't seen a successful run. The module
also fails for the ImmersaDesk and Infinity Wall. According to the
various debug output statements in the code, it is successfully loading
the geometry data, but nothing ever happens in the CAVE.

If anyone knows if this is a known bug with Performer or if they have the
same problem, let me know. Especially if you found a way to fix it.

Perhaps in Performer 2.2?

Cory Tsang
Virtual Environments Group
NCSA

=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com
   SGI DevForum 97 info: http://www.sgi.com/Forum97/


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:26 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.