|
From: SourceForge.net <no...@so...> - 2004-06-15 23:10:04
|
Bugs item #907879, was opened at 2004-03-01 21:41 Message generated for change (Comment added) made by grantd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442052&aid=907879&group_id=45158 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Dair Grant (grantd) Assigned to: Nobody/Anonymous (nobody) >Summary: Table of contents not parsed in text 3DMFs Initial Comment: Frank Cox wrote: Quesa is having problems loading 3DMFs with multiple trimeshes that use shader references. Here's a simplified example model: http://webhome.idirect.com/~frankco/ test_3dm.sit It's a simple cube, with each face saved as a separate trimesh, but all faces reference the first texture shader. QD3D handles these files just fine. A second issue that popped up with 1.6d18 involves specular highlighting. I'm getting specular highlights on trimeshes that shouldn't be receiving them (i.e. meshes using a null shader). This only happens when at least one object in the scene has specular highlighting enabled, which leads me to suspect that the GL state may be left dangling between vertex flushes. ----- James Walker wrote: The bug appears to be in reading text 3DMF files. After I converted the test file to binary form with Anatas, a Quesa app was able to read all 6 textured TriMeshes. ---------------------------------------------------------------------- >Comment By: Dair Grant (grantd) Date: 2004-06-15 23:10 Message: Logged In: YES user_id=439944 Renaming to reflect underlying problem. ---------------------------------------------------------------------- Comment By: James W. Walker (jwwalker) Date: 2004-06-05 16:56 Message: Logged In: YES user_id=433183 The underlying problem is that Quesa does not read the table of contents in text 3DMF. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442052&aid=907879&group_id=45158 |