Virtual cliptexture problems

New Message Reply Date view Thread view Subject view Author view

Jonas Andersson (jonasa++at++cs.umu.se)
Mon, 4 May 1998 10:08:18 +0200 (MDT)


I am using the pfdloader to load a geometry which geostate I then switch
to a new one containing a cliptexture. This works fine.

Problem 1:
Is it possible to save scene-graphs containing cliptextures to any format?
My attempts to save the created scenegraph fails; the .pfb
file is created but it do not contain neither geometry or cliptexture.
When saving I get the following warning:

PF Warning: pfdStoreFile_pfb: Found unregistered pfImageTile read
function 0x588f3c5c.
PF This function will not be saved.
PF To have user callback functions saved,
PF register them with pfdRegisterUserFunc.

Problem 2:
How can I get rid of the following effect?
When using cliptextures larger then 32768*32768, e.g. virtual
cliptextures, the cliptexture gets distorted. It looks like only a fourth
of the cliptexture (centered around the clipcenter as it changes) can
be displayed correctly. The rest of the cliptexture looks like when
trying to repeat a texture with CLAMPING OFF.

The same cliptexture looks OK when viewed using the .ct-loader.

Problem 3: Are there anyting I can do enable processor sorting? When
using cliptextures I get the following message:

PF Info(2): Queue proc(8366) started
PF Notice(3): MUSTRUN of PFPROC_QUEUE_SORT process -1 on CPU 0 failed.
PF Warning: pfQueue::setSortMode; couldn't sproc sortProc, sort mode failed

Thanks in advance for any help!

/Jonas
________________________________________________________________________________
Jonas Andersson jonasa++at++cs.umu.se, http://www.cs.umu.se/~jonasa

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


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:57:21 PDT

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