sl-service-account
commented
9 years ago Drongle McMahon commented at 2015-03-09T02:22:55Z
megatri_thingy.zip contains the collada file megatri_thingy.dae that is a mesh object illustrating the random fragmentation effect in the eighth material.
How would you like the feature to work?
Currently, with release or Project-Importer viewer, the uploader starts a new material when the triangle count reaches 21844 (details in BUG-1001). This can cause the material count to be greater than specified in the dae file. In the release viewer, this can lead to texturing artefacts, and to holes in the mesh if more than 8 materials results. In the Project-Importer viewer, exceeding 8 materials now leads to the geometry carrying the secretly created materials being added to a new object. Given the arbitrary order of triangles encountered by the uploader, this can lead to absurd fragmentation of the object (see http://community.secondlife.com/t5/Mesh/Normals-not-flipped-but-still-showing-in-the-wrong-form-on/m-p/2911672#M30870 message 12). This is a more serious manifestation of overlooking this error than the holes that appeared with the release viewer.
When the uploader encounters a triangle list that exceeds the limit 21844 triangles, instead of creating a new material, it should abort the upload with an informative error message, so that this fragmentation problem cannot happen.
Why is this feature important to you? How would it benefit the community?
It is explained in BUG-1001 that this limit arose from a mistake in the code, where a limit on the length of the triangle list pre-empted the intended 64k vertex limit. The latter would have blocking upload. Since the error has not been repaired, it seems to be sensible to replace the 64k limit with the de-facto triangle limit, This is more urgent now that the effects will soon include the arbitrary fragmentation of objects in a way dependent on triangle-ordering idiosyncracies of collada exporters. The user community should be protected from such effects.
Attachments
Links
Duplicates
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-8720 | | Summary | [Project-Importer] Please make upload of mesh materials with > 21844 triangles an error that blocks upload. | | Type | New Feature Request | | Priority | Unset | | Status | Closed | | Resolution | Duplicate | | Reporter | Drongle McMahon (drongle.mcmahon) | | Created at | 2015-03-08T23:40:10Z | | Updated at | 2022-03-30T23:56:31Z | ``` { 'Business Unit': ['Platform'], 'How would you like the feature to work?': 'Currently, with release or Project-Importer viewer, the uploader starts a new material when the triangle count reaches 21844 (details in BUG-1001). This can cause the material count to be greater than specified in the dae file. In the release viewer, this can lead to texturing artefacts, and to holes in the mesh if more than 8 materials results. In the Project-Importer viewer, exceeding 8 materials now leads to the geometry carrying the secretly created materials being added to a new object. Given the arbitrary order of triangles encountered by the uploader, this can lead to absurd fragmentation of the object (see http://community.secondlife.com/t5/Mesh/Normals-not-flipped-but-still-showing-in-the-wrong-form-on/m-p/2911672#M30870 message 12). This is a more serious manifestation of overlooking this error than the holes that appeared with the release viewer.\r\n\r\nWhen the uploader encounters a triangle list that exceeds the limit 21844 triangles, instead of creating a new material, it should abort the upload with an informative error message, so that this fragmentation problem cannot happen.\r\n\r\n', 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': 'It is explained in BUG-1001 that this limit arose from a mistake in the code, where a limit on the length of the triangle list pre-empted the intended 64k vertex limit. The latter would have blocking upload. Since the error has not been repaired, it seems to be sensible to replace the 64k limit with the de-facto triangle limit, This is more urgent now that the effects will soon include the arbitrary fragmentation of objects in a way dependent on triangle-ordering idiosyncracies of collada exporters. The user community should be protected from such effects.', } ```