Performer2.0 bug list

New Message Reply Date view Thread view Subject view Author view

Sharon Clay (src++at++rose.asd.sgi.com)
Fri, 26 Apr 1996 23:02:25 -0700


Here is the Performer2.0 bug list.
Some of these were already in the release notes for Performer2.0.
src.

===========================
IRIS Performer 2.0 Bug List
===========================

Bugs fixed in the IRIX6.2 performer_eoe libraries:

o OpenGL Fog: OpenGL exponential fog in IRIS Performer 2.0 did not match
    the IRIS GL fog.

o OpenGL default MIPmapped Texture filter:
    Graphics platforms that should be using MIPMAP_TRILINEAR as the default
    minification filter (such as RealityEngine and IMPACT) were actually using
    MIPMAP_LINEAR in 2.0.

o Detail Texture Splines:\f1
    Several bugs with the specification of detail splines in IRIS Performer 2.0
    have been fixed. The default OpenGL splines now match the IRIS GL defaults.
    Specification of clamped detail splines for IRIS GL operation have
    been fixed.

o OpenGL Detail Texture on IRIX 6.2: OpenGL detail texture through
    IRIS Performer 2.0 was not functional when running under 6.2.

o OpenGL Texture Loading on RealityEngine:
    In IRIS Performer 2.0 running under OpenGL on RealityEngine graphics,
    texture had to be explicitly enabled for a texture to be successfully
    loaded. This is now handled internally by IRIS Performer.

o Video Clock Timing: video clock timing in IRIS Performer 2.0 was often slightly off.

o pfdLoadFile_flt: The FLT loader under IRIS Performer 2.0 64bit operation
    may core dump on textures.

o pfMergeBuffer core dump in clean() when creating children before parents:
    IRIS Performer 2.0 could core dump after pfMergeBuffer() if
    child nodes in the asynchronous process were created before their
    parents.

o pfDrawBin core dump: pfDrawBin() in IRIS Performer 2.0 will core dump if called on an
    empty bin.

o IRIS GL windows had no stereo buffers: pure IRIS GL windows would not be configured
    with stereo buffers with pfWinFBConfigAtrrs()
    even if the PFFB_STEREO token was present in the
    attribute array.

o IRIS GL window queries were broken: some of the window config queries for
    pfQueryWin() would always return 0 for pure IRIS GL windows.

o Resizing of pfPipeWindows when multi-processed and
    using X windows (IRIS GLX or OpenGL/X) when an alternate framebuffer configuration
    window is selected (such as the fill statistics window in OpenGL/X perfly) has
    been fixed. In IRIS Performer 2.0 this
    could channel viewports to be confused when the alternate framebuffer
    configuration window is de-selected (such as disabling the fill statistics
    in perfly when running with X windows).

o pfAlphaFunc had no effect if PFSTATE_ENLIGHTING is being overridden

o pfMatrix::getOrthoCoord\f1: Performer2.0 it gave bad roll when pitch was +-90.

o C++ perfly error\f1: In the C++ perfly and related programs, on multipipe machines,
    all windows get opened on pipe 0. The fix is swapping lines 419 and 420 in
    perf/sample/apps/C++/common/generic.C.

o Intersections with PFGS_POLYS could cause core dumps in Performer2.0

o Memory corruption by extending pfStrings by 1 character

o Bad malloc for names of pfFontss could potentially cause a core dump in Performer2.0.

o Order of pfBuffer commands executed by pfMergeBuffer() is reversed in 2.0

Problems to be fixed in later patch for 2.0:

o Asynchronous pfDelete of data of data allocated off the heap and not in shared
    memory could cause core dump.

o OpenGL textures with VIDEO and FRAMEBUFFER sources do not work in 2.0

o pfFlatten on indexed pfGeoSets may dump for in 2.0

-- 
-----{-----{---++at++   -----{----{---++at++   -----{----{---++at++   -----{----{---++at++
Sharon Rose Clay (Fischler) - Silicon Graphics, Advanced Systems Dev.
src++at++sgi.com  (415) 933 - 1002  FAX: (415) 965 - 2658  MS 8U-590
-----{-----{---++at++   -----{----{---++at++   -----{----{---++at++   -----{----{---++at++

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:52:47 PDT

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