Re: Quesa - "Most Wanted" list

[Joseph J. S. <jo...@st...>]

At 10:02 PM -0700 6/1/04, James W. Walker wrote:

>>4. Improved speed -- though this has improved recently, we still 
>>find that object performance degrades pretty quickly for scenes 
>>with lots of objects.  (Some of this may actually be in the 
>>REALbasic layer on top of Quesa, but we'd like to at least look 
>>into where the current bottlenecks are and see what can be done 
>>about them.)
>
>"degrades pretty quickly" meaning as more than a linear function of 
>the number of triangles?  Have you tried to separate out the effects 
>of lots of triangles, lots of textures, and lots of groups?

Yes; the issue is lots of objects (whether this is because it's lots 
of groups, or because it's lots of TriMeshes, is unclear), not the 
number of triangles.  A scene with 4000 triangles in one TriMesh 
renders very quickly; the same scene composed of 400 objects 
containing 10 triangles each renders poorly.

>>5. Support for writing text 3DMFs.  I looked at the code a little 
>>bit today, and it doesn't look very conducive to adding text 
>>support -- about half the code in E3FFW_3DMFBin_Writer.c should 
>>actually be shared between the bin and text writers.  But it could 
>>be refactored...
>
>By the way, reading text 3DMFs is also incomplete; the table of 
>contents is ignored.  I'm not sure if that's explicitly mentioned in 
>the bug database, but I know that at least one bug is caused by this 
>fact.

That's interesting.  What bug is caused by it?  I use text 3DMF 
almost exclusively, but then, most of the files I'm reading are 
generated with Meshwork and have a very simple structure.

Best,
- Joe

-- 
,------------------------------------------------------------------.
|    Joseph J. Strout         Check out the Mac Web Directory:     |
|    jo...@st...           http://www.macwebdir.com/            |
`------------------------------------------------------------------'