You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 4, 2025. It is now read-only.
When uploading mesh with custom LODs, containing an object with the same object name in two LODs, the following error message appears: "Error: Material of model is not a subset of reference model." (It makes no difference whether there are materials defined or not)
Steps to Reproduce
test.dae contains two objects: Cube3 and Sphere3.
test_LOD2.dae contains two objects: Cube3 and Sphere2.
When uploading this, the error message is thrown.
Expected Behavior
It should be able to handle such LODs with same object names.
Other information
Oddity 1:
When both files contain only Cube3, there is no error message.
Oddity 2:
According to the SecondLife.log, all objects within the LODs get renamed to have unique names, as soon the .dae-files got selected from the upload window.
Background:
When modeling complex buildings with several dozen of objects, it is very helpful to organize them with Layers or Groups (for example in Blender). One can assign an object to multiple Layers/Groups, if it is used unchanged in all of them. This reduces the possibility of mistakes and the working time drastically. But as a result after exporting, one has some object names in multiple use.
Most of my mesh project files (+100) are broken now. Of course I could work-around by creating copies with unique names of all those objects used for multiple LODs, but that would cause so much work, that it makes no sense.
Uploading Mesh with same object names in LODs throws error
Type
Bug
Priority
Unset
Status
Closed
Resolution
Unactionable
Reporter
Ravelli Ormstein (ravelli.ormstein)
Created at
2015-11-07T16:49:19Z
Updated at
2017-05-08T23:29:31Z
{
'Business Unit': ['Platform'],
'Date of First Response': '2015-11-09T11:46:49.517-0600',
"Is there anything you'd like to add?": 'Oddity 1:\r\nWhen both files contain only Cube3, there is no error message.\r\n\r\nOddity 2:\r\nRegarding to the SecondLife.log, all objects within the LODs get renamed to have unique names, as soon the .dae-files got selected from the upload window.\r\n\r\nBackground:\r\nWhen modeling complex buildings with several dozen of objects, it is very helpful to organize them with Layers or Groups (for example in Blender). One can assign an object to multiple Layers/Groups, if it is used unchanged in all of them. This reduces the possibility of mistakes and the working time drastically. But as a result after exporting, one has some object names in multiple use.',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Viewer',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'When uploading mesh with custom LODs, containing an object with the same object name in two LODs, the following error message appears: "Error: Material of model is not a subset of reference model."',
'What were you doing when it happened?': 'test.dae contains two objects: Cube3 and Sphere3.\r\ntest_LOD2 contains two objects: Cube3 and Sphere2.\r\nWhen uploading this, the error message is thrown.',
'What were you expecting to happen instead?': 'It should be able to handle such LODs with same object names.',
'Where': 'It happens in Agni and Aditi (and even OpenSimulator).',
}
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Actual Behavior
When uploading mesh with custom LODs, containing an object with the same object name in two LODs, the following error message appears: "Error: Material of model is not a subset of reference model." (It makes no difference whether there are materials defined or not)
Steps to Reproduce
test.dae contains two objects: Cube3 and Sphere3.
test_LOD2.dae contains two objects: Cube3 and Sphere2.
When uploading this, the error message is thrown.
Expected Behavior
It should be able to handle such LODs with same object names.
Other information
Oddity 1:
When both files contain only Cube3, there is no error message.
Oddity 2:
According to the SecondLife.log, all objects within the LODs get renamed to have unique names, as soon the .dae-files got selected from the upload window.
Background:
When modeling complex buildings with several dozen of objects, it is very helpful to organize them with Layers or Groups (for example in Blender). One can assign an object to multiple Layers/Groups, if it is used unchanged in all of them. This reduces the possibility of mistakes and the working time drastically. But as a result after exporting, one has some object names in multiple use.
Most of my mesh project files (+100) are broken now. Of course I could work-around by creating copies with unique names of all those objects used for multiple LODs, but that would cause so much work, that it makes no sense.
Attachments
Original Jira Fields
The text was updated successfully, but these errors were encountered: