From: Murray Gamble (murraygamble++at++thehfegroup.com)
Date: 11/12/2001 10:40:25
Hi Larry,
Regarding #2 - indecipherable ASD directory
".adf" is the extension for a Vega definition file (intended to be read by a
Vega application). The object, volume and region information relates to
Vega's representation of "objects", "volumes" and "regions" (regions are
specific to the Vega Large Area Database Management or LADBM module).
Regarding #1 - my guess
If the files in question form part of any demos distributed by MPI
(particularly if they're a few years old), then I believe that MPI encrypted
all .pfb and texture files such that they could not be re-used by any
adventurous developers. I'm guessing that these files are "decoded" by the
preferred application at runtime.
Cheers,
Murray
-----Original Message-----
From: ramey++at++vrtigo.com [mailto:ramey++at++vrtigo.com]On Behalf Of Larry Ramey
Sent: Monday, November 12, 2001 11:32 AM
To: info-performer++at++sgi.com
Subject: Some ASD questions:
pfPeople->helloWorld(),
2 Errors:
1) unload able pfbs
2) indecipherable ASD directory
I have a strange error. This performer program is about 10 lines of code,
yet it doesn't work. (I guess anything over 4 lines is clearly beyond my
ability!)
PF Notice: pfdLoadFile_pfb: Loading
"N38_03_12W115_35_12.pfb"
PF Warning: pfdLoadFile_pfb: "N38_03_12W115_35_12.pfb"
has a newer pfb version number.
PF Warning: It may not load correctly.
Segmentation fault (core dumped)
Bummer!! So here is my software versions...
versions -k | grep Performer
performer_eoe.sw32 03/30/2001 Performer2.2.7 N32 Execution Software
performer_eoe.sw32.ogl_performer 03/30/2001 Performer2.2.7 OpenGL DSOs
(n32)
Did the Performer pfb format change when I wasn't looking? Is there
something new in 2.4?
The REAL problem I am trying to solve is how to load this darn ASD that I
have. I have two directories, one is filled with *.flt files. (which I can
load in asdFly one at a time) they are named things such as:
N35_29_36W113_40_00.flt
N36_59_12W115_22_24.flt
N38_28_48W117_04_48.flt
N39_58_24W118_47_12.flt
N35_29_36W113_52_48.flt
Looks very similar to a clipTex, no?
then I have another directory filled with the unreadable pfb files. THIS
directory also has a file that looks a lot like a clipTexuture setup file:
/mnt/woar2/flt>more ../pfb/data.adf
object N34_00_00W113_01_36 {
file N34_00_00W113_01_36.pfb;
convt 2;
cs 0;
optim 0x3;
isclass 0xF0;
divisions 10;
upvol on;
parts off;
autorange -1;
pos 0 0 0 0 0 0;
represent 0xFFFFFFFF;
immediate 0;
useprojection 0;
temp 0;
scale 1;
complete on;
tflod_state off;
tflod_depth 1;
}
volume N34_00_00W113_01_36 {
sphere 0 0 0 50000;
position 0 0 0 0 0 0;
}
region N34_00_00W113_01_36 {
state on;
position 265050 -321507 0;
euler 0 0 0;
render off;
volume N34_00_00W113_01_36;
objname N34_00_00W113_01_36;
voloff 0 0 0;
aoicull on;
group 1;
}
ect
ect
ect
The thing is there is NO such thing as a "*.afd" loader. (at least not that
I can find)
I am sure I am missing something obvious but I have read the documentation
a few times, and just don't seem to get it.
---------------------------------
Larry E. Ramey
Software Engineer
VRCO
-----------------------------------------------------------------------
List Archives, Info, FAQ: http://www.sgi.com/software/performer/
Open Development Project: http://oss.sgi.com/projects/performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
-----------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Mon Nov 12 2001 - 10:43:27 PST