The Asset Server hosts files or assets that can either be added as-is to your domain or that are referenced by existing entities and scripts already in your domain. Your assets are 3D models, audio files for various sound effects, image files for textures and skyboxes, scripts, and more.
On This Page:
Files hosted on the Asset Server are only available in your domain, and cannot be seen in other domains. Therefore, we recommend that you do not upload avatars to the Asset Server since they will not be available in domains other than your own.
You can add, edit, and remove files from your Asset Server through the Asset Browser in your domain. To add a file from your computer to the Asset Server:
/asset_filename. By default, there is no folder created for your asset. However, we recommend that you add folders for each of your assets to help keep your assets organized.
Once files have been uploaded to your Asset Server, they can be added directly to your domain or referenced by any entities or scripts in your domain using their URLs. To get an asset's URL:
When you upload a model to your domain, you are rendering the following:
Loading models in High Fidelity involves real-time rendering (drawcalls), which means images are produced and analyzed in real time. Depending on the complexity of the models, the drawcalls can differ. You can reduce the drawcalls and optimize the rendering process using baking. Baking optimizes the rendering process by compressing the poly meshes and textures in an asset. A baked model loads the smaller meshes first, cutting down on the load time. Baked textures are often larger than the original texture because they contain textures with different resolutions.
In High Fidelity, baking improves the efficiency with which models are stored and transmitted. If you bake your domain content, you will reduce the initial load times for your visitors.
|File Type||Baking Process|
|3D models (FBX files with embedded textures)||Baked when uploaded to the Asset Server.|
|Avatars (FBX files with embedded textures)||Baked when uploaded to the Asset Server. Avatars are usually not uploaded to the Asset Server as they are used in different domains. Avatars uploaded to the Asset Server can only be baked when their FBX files are embedded with textures.|
A baked JS file will not be very easy to read as all the white spaces and comments will be removed. If you wish to read and understand any JS files that have been baked, you will need to use its unbaked version.
A baked file will have a check mark under the 'Use Baked?' column on the Asset Browser. A file will not bake when:
To bake a file again, just uncheck and check 'Use baked version'.
You can add an asset to your domain through the Asset Browser.
atp:/$FILENAME, and modify its collision and physics properties. Once you are done with these changes, click 'Add'.
You can use the Asset Browser to edit the assets in the following ways: