glTF Mesh Import: Improve usefulness and correlation of information put in Mesh Uploader Log Tab and SecondLife.log

[aiaustin]

Improve usefulness and correlation of information put in Mesh Uploader Log Tab and SecondLife,log

It would be helpful if the "Log" tab of the mesh uploader gave more useful user orientated error messages that were directed at how to identify the issues involved to allow the creator to change the model to come within spec. And then more detailed information may be placed in SecondLife.log using the same mesh names, and Log tab error message so that the user can quickly find the relevant part of the log for the detail.

As an example I may see a pop up message

 "Test Mesh Parts 1 failed to upload MAV_BLOCK_MISSING"
 See SecondLife.log for details.

But the log file has no reference at all to either "Test Mesh Parts 1" or "MAV" anywhere.

The following SL Forums Discussion does give some helpful advice on MAV Blocks and their meaning, but this does not seem relevant to examples I am seeing of mesh uploader failures...

https://community.secondlife.com/forums/topic/88636-specifications-for-sl-compatible-dae-format/#comment-742343

More user orientated log messaging and use of the same model names and visible error message in both the Mesh Uploader Log tab and in SecondLife.log would be helpful.

Test Plan

Try various mesh uploads for failing meshes to check user is given helpful and corelated information.

[aiaustin]

I found that SecondLife.log was updated but it seems like a long time after the event and well after a user would look at the log file for an explanation. Perhaps this issue could be addressed by a force push of log file information if any popup mentioning SecondLife.log is given to the user. Although the detail actually was no more than the UI popup, so was not actually giving the further details promised.

2025-05-22T08:17:04Z WARNING #Mesh# newview/llmeshrepository.cpp(843) log_upload_error : mesh upload failed, stage 'fee', error '', message 'MAV_BLOCK_MISSING', id 'Upload_InvalidAsset'
2025-05-22T08:17:04Z WARNING # newview/llfloatermodelpreview.cpp(1876) LLFloaterModelPreview::setModelPhysicsFeeErrorStatus : LLFloaterModelPreview::setModelPhysicsFeeErrorStatus(13107200 : )
2025-05-22T08:17:04Z WARNING # newview/lltoastalertpanel.cpp(197) LLToastAlertPanel::LLToastAlertPanel : Alert: Pipework-Top-Right failed to upload: MAV_BLOCK_MISSING\n\nSee SecondLife.log for details

Also, I found that if I left the mesh uploader panel open and attempted to upload a second differently named mesh the name of that mesh was not shown (or searchable) in SecondLife.log, though the MAV_BLOCK_MISSING error that also showed was reported.

A little love and care to the user shown mesh uploader error and log messages for obscure errors would be good.

[aiaustin]

Trying to debug and track down the possible cause of "LOD3 Bad element" shown in the mesh uploader Log tab, I was looking for any detail in SecondLife.com. But "Bad element", "LOD3 Bad" or even "LOD3" does not show any entry when searching in the log. With default logging levels the message shown to the user should appear in SecondLife.log to allow the location of further details to be found easily and some extra information added there.

Update: LOD3 is not there but "lod 3" is! This needs to be made identical. But interestingly it seems to have no errors for anything mentioning the mesh part listed in the user facign mesh uploader Log tab.

[aiaustin]

It would be very helpful if the message about 16 bit limits being exceeded could list the mesh part name that this was found on.

This is generally true for this and other messages to make the log tab and SecondLife.log could be made more helpful to the creator/uploader.

[marchcat]

I've added some messages to the log. Please let me know if there's anything else you'd like to see there.