Armored-Dragon
commented
1 month ago There could also be a option you set somewhere that makes it to when you "upload" something, it will instead route that file to a predefined server (Nextcloud for instance). This will make it so that a server hoster won't be burdened by as many assets especially if they are otherwise not needed for long. So if I were to join a world having set a hypothetical setting to route all of my file uploads to my own server, when I upload something, my server distributes that file and stores it instead of the server. Related:
To be clear, this is referring to how files or URL's dragged onto the interface window are handled.
For most users (on desktop at least) it has to be the easiest and most intuitive way to handle assets or avatars. It actually works fairly well already, but the logic that decides how to handle the dropped item could be a lot better:
Dropping URL's only works for JSON and FST files it seems. I see no reason why it shouldn't be able to handle a direct link to a model or image, all browsers can do it.
Models (glft/fbx) are uploaded to the asset server when dropped, I think it should ask if I want to load directly, upload to asset server, or upload and load from there.
FST's are assumed to be avatars, but it could be a model with material override or something and it that it not the case it just fails. It should be fairly easy to detect if it is a model or avatar.
images work well and are uploaded to asset server (if permissions allow it) and then loaded as an image entity from there. the fact that the created image does not have the correct aspect ratio is a different issue 😄
JSON's also work pretty well with the one caveat that wearables, while correctly attached to your avatar, are not created as avatar entities so they disappear if you change domain. This actually also applies to the normal import dialog, I assume this is all using the JS API and if so, it should read the
EntityHostTypefrom the JSON and set theEntityHostTypeparameter of https://apidocs.overte.org/Clipboard.html#.pasteEntities accordingly. But also 😕 there is aavatarEntityproperty for entities and I don't understand why 🤔