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 has been archived by the owner on Mar 28, 2024. It is now read-only.
When uploading a mesh model, the mesh uploader checks the directory for models with special postfixes, and autofills the rest of the form.
For example, in a folder containing the following files:
Lampost.dae
Lampost_LOD0.dae,
Lampost_LOD1.dae,
Lampost_LOD2.dae,
Lampost_PHYS.dae
If I went to Build > Upload Model and select Lampost.dae, the fields for medium, low, lowest and physics would automatically be populated as 'from file' with the respective files in the directory because they have the appropriate _postfixes
Why is this feature important to you? How would it benefit the community?
As a creator, I am uploading many mesh creations practically daily throughout the year. For larger items such as trees, I am even splitting my models up into sub models so as to reduce bounding box volume so LOD's can drop at lower distances and reduce land impact.
The bottom line is people like me upload a lot of models
One of the things that slows me down is the uploader, as I need to change the drop down for each item, medium, low, lowest, browse for the file, find the file, which can get tiring going back and forth between so many dialogs and lists and has proven itself prone to frustrating mistakes/reuploads etc.
Having a way to only have to select one model and have the rest of the form autofill would greatly streamline this aspect of creating and would make a world of difference for people like me.
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'Date of First Response': '2020-05-07T07:01:27.568-0500',
'How would you like the feature to work?': "When uploading a mesh model, the mesh uploader checks the directory for models with special postfixes, and autofills the rest of the form.\r\n\r\nFor example, in a folder containing the following files:\r\n\r\n* Lampost.dae\r\n* Lampost_LOD0.dae,\r\n* Lampost_LOD1.dae,\r\n* Lampost_LOD2.dae,\r\n* Lampost_PHYS.dae\r\n\r\nIf I went to Build > Upload Model and select Lampost.dae, the fields for medium, low, lowest and physics would automatically be populated as 'from file' with the respective files in the directory because they have the appropriate _postfixes",
'Original Reporter': 'Extrude Ragu (extrude.ragu)',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'Target Viewer Version': 'viewer-development',
'Why is this feature important to you? How would it benefit the community?': "As a creator, I am uploading many mesh creations practically daily throughout the year. For larger items such as trees, I am even splitting my models up into sub models so as to reduce bounding box volume so LOD's can drop at lower distances and reduce land impact. \r\n\r\nThe bottom line is people like me upload a *lot* of models\r\n\r\nOne of the things that slows me down is the uploader, as I need to change the drop down for each item, medium, low, lowest, browse for the file, find the file, which can get tiring going back and forth between so many dialogs and lists and has proven itself prone to frustrating mistakes/reuploads etc.\r\n\r\nHaving a way to only have to select one model and have the rest of the form autofill would greatly streamline this aspect of creating and would make a world of difference for people like me.\r\n\r\nPS. There is an article here:-\r\nhttps://community.secondlife.com/knowledgebase/english/uploading-a-mesh-model-r274/\r\nWhich under section 2 mentions these postfixes, which suggests this was originally intended to be a thing?",
}
The text was updated successfully, but these errors were encountered:
+1 for this idea. I spoke about this at the CCUG meeting a few weeks ago and there was a general agreement that the current mechanism is very clunky and in need of love.
The page in the knowledge base is wrong and has been for many years sadly. It was once proposed to be that way and then it got changed, the _LODn suffix is now expected to be in the mesh name within the DAE. The DAE itself can be named however you wish, but I agree most of us who work in this way follow a convention such as the one above to manage the various LOD model files.
I have a revised text for that page that I've prepared (Jira coming soon) that will correct the statements in the link.
I have also started to look at an auto-fill function (in Firestorm) as part of a second round of uploader changes. The plan is to support both LODn suffixes and _MED/_LOW type suffixes too.
I plan to contribute these to the LL viewer as well once I get them in place, unless the lab beat me to it :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How would you like the feature to work?
When uploading a mesh model, the mesh uploader checks the directory for models with special postfixes, and autofills the rest of the form.
For example, in a folder containing the following files:
Lampost.dae
Lampost_LOD0.dae,
Lampost_LOD1.dae,
Lampost_LOD2.dae,
Lampost_PHYS.dae
If I went to Build > Upload Model and select Lampost.dae, the fields for medium, low, lowest and physics would automatically be populated as 'from file' with the respective files in the directory because they have the appropriate _postfixes
Why is this feature important to you? How would it benefit the community?
As a creator, I am uploading many mesh creations practically daily throughout the year. For larger items such as trees, I am even splitting my models up into sub models so as to reduce bounding box volume so LOD's can drop at lower distances and reduce land impact.
The bottom line is people like me upload a lot of models
One of the things that slows me down is the uploader, as I need to change the drop down for each item, medium, low, lowest, browse for the file, find the file, which can get tiring going back and forth between so many dialogs and lists and has proven itself prone to frustrating mistakes/reuploads etc.
Having a way to only have to select one model and have the rest of the form autofill would greatly streamline this aspect of creating and would make a world of difference for people like me.
PS. There is an article here:-
https://community.secondlife.com/knowledgebase/english/uploading-a-mesh-model-r274/
Which under section 2 mentions these postfixes, which suggests this was originally intended to be a thing?
Original Jira Fields
The text was updated successfully, but these errors were encountered: