Bemis, Suzie CEI-TACCSF (suzie++at++TACCSF.KIRTLAND.AF.MIL)
Mon, 13 Apr 1998 08:32:24 -0600
I'm getting a Warning from Perfly:
PF Warning/Usage(12): pfMemory::new() Unable to allocate 32516 bytes
from the heap.
PF Warning/Resource: pfCalloc() error.
PF Notice/Assert: combineLODs() unable to process group (null).
This happens when I load a .flt model with loader 14.2 on an R10000 O2
with a 6.3 OS. The file itself was saved as a MultiGen 14.2 model, too.
My first thought was that it was too large to run (9.4MB), so I cut out
some polygons to get the size to about 7.5MB. It still gave me the
warning, and dumped a core when I tried to run it. I have another v14.0
.flt file that's 7.8MB, but I get no warnings or problems when I load
it. So, I tried saving the problem .flt as a v14.0, but that didn't
help. Then, I took all the subfaces out of the problem .flt file
thinking still that it's a size issue, but that didn't help either.
This is a third party database so I don't know exactly how it was built.
I'm thinking there's something in the file that's not built right, or
not compatible with the version of the loader I'm using.
I'm going to upgrade to Performer 2.2 with loader 15.4 this morning and
see if that helps. But, until then, has anybody else seen this problem
and have a solution?
Thanks,
Suzie
Hello,
I'm getting a Warning from Perfly:
PF Warning/Usage(12): pfMemory::new() Unable to allocate 32516 bytes from the heap.
PF Warning/Resource: pfCalloc() error.
PF Notice/Assert: combineLODs() unable to process group (null).
This happens when I load a .flt model with loader 14.2 on an R10000 O2 with a 6.3 OS. The file itself was saved as a MultiGen 14.2 model, too. My first thought was that it was too large to run (9.4MB), so I cut out some polygons to get the size to about 7.5MB. It still gave me the warning, and dumped a core when I tried to run it. I have another v14.0 .flt file that's 7.8MB, but I get no warnings or problems when I load it. So, I tried saving the problem .flt as a v14.0, but that didn't help. Then, I took all the subfaces out of the problem .flt file thinking still that it's a size issue, but that didn't help either. This is a third party database so I don't know exactly how it was built. I'm thinking there's something in the file that's not built right, or not compatible with the version of the loader I'm using.
I'm going to upgrade to Performer 2.2 with loader 15.4 this morning and see if that helps. But, until then, has anybody else seen this problem and have a solution?
Thanks,
Suzie
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:57:14 PDT