Skip to content

Commit

Permalink
fix: Smart wearables limit size (#257)
Browse files Browse the repository at this point in the history
* fix: Update SW limitations to 3MB

Signed-off-by: Gabriel Diaz <[email protected]>

* fix: Remove empty spaces

Signed-off-by: Gabriel Diaz <[email protected]>

---------

Signed-off-by: Gabriel Diaz <[email protected]>
  • Loading branch information
cyaiox authored Sep 26, 2023
1 parent d157f01 commit e8b5250
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 7 deletions.
8 changes: 2 additions & 6 deletions content/creator/sdk7/projects/scene-files.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,16 +27,15 @@ This is the entry point to your scene's code. You could fit your entire scene's

In most cases, you'll only need to edit this and other .ts files to create your scene. It contains the code that generates the [entities, components]({{< ref "/content/creator/sdk7/architecture/entities-components.md" >}}) and [systems]({{< ref "/content/creator/sdk7/architecture/systems.md" >}}) of your scene.

When running the scene, the contents of your `.ts` files are compiled to a single minified `.js` file, `bin/scene.js`.
When running the scene, the contents of your `.ts` files are compiled to a single minified `.js` file, `bin/scene.js`.

{{< hint warning >}}
**📔 Note**: You can use another tool or language instead of TypeScript, so long as your scripts are contained within a single Javascript file (bin/scene.js). All provided type declarations are made in TypeScript, and other languages and transpilers are not officially supported.
{{< /hint >}}


### scene.json

The _scene.json_ file is a JSON formatted manifest for a scene in the world. A scene can span a single or multiple LAND parcels. The _scene.json_ manifest describes what objects exist in the scene, a list of any assets needed to render it, contact information for the parcel owner, and security settings.
The _scene.json_ file is a JSON formatted manifest for a scene in the world. A scene can span a single or multiple LAND parcels. The _scene.json_ manifest describes what objects exist in the scene, a list of any assets needed to render it, contact information for the parcel owner, and security settings.

For more information see [scene metadata]({{< ref "/content/creator/sdk7/projects/scene-metadata.md#metadata">}}). You can also read the original [specification proposal](https://github.com/decentraland/proposals/blob/master/dsp/0020.mediawiki) for this metadata.

Expand All @@ -62,7 +61,6 @@ Directories containing a _tsconfig.json_ file are root directories for TypeScrip

When installing any additional libraries to your scene, an entry should be added automatically to this file. For installing Decentraland utils libraries, it shouldn't be necessary to manually do any changes to this file.


## Recommended file locations

Keep in mind that when you deploy your scene to Decentraland, any assets or external libraries that are needed to use your scene must be either packaged inside the scene folder or available via a remote server.
Expand All @@ -82,12 +80,10 @@ We suggest using these folder names consistently for storing the different types
**📔 Note**: Supporting files for glTF models, like their texture image files or _.bin_ files, should always be placed in the same folder as the model's _.gltf_ or _.glb_ file.
{{< /hint >}}


{{< hint warning >}}
**📔 Note**: We recommend using always lower case names for all folders and file names, to avoid possible issues.
{{< /hint >}}


## The dclignore file

All scenes include a _.dclignore_ file, this file specifies what files in the scene folder to ignore when deploying a scene to Decentraland.
Expand Down
2 changes: 1 addition & 1 deletion content/creator/sdk7/projects/smart-wearables.md
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,7 @@ See [Required permissions]({{< ref "/content/creator/sdk7/projects/scene-metadat

## Limitations

> IMPORTANT: The entire smart wearable needs to fit within 2 MB. This includes the 3D model, thumbnail, code, libraries, sound files, additional 3D models, UI images, etc. This limit is for the uncompressed folder. The builder will not let you upload larger wearables than this.
> IMPORTANT: The entire smart wearable needs to fit within 3MB. This includes the 3D model, thumbnail, code, libraries, sound files, additional 3D models, UI images, etc. This limit is for the uncompressed folder. The builder will not let you upload larger wearables than this.
> To check the size of your portable experience, run `npm run pack`, the project size is specified in the output text of the command. You can also verify this by uncompressing the generated `smart-wearable.zip` file and checking the size of the folder.
Smart wearables only run the portable experience for the player wearing the wearable. Other players don't see the effects. For example, if the portable experience renders a pet that follows the player, other players around won't see this pet. However, other players will see avatars perform animations that run as part of the wearable's scene, even [custom avatar animations]({{< ref "/content/creator/sdk7/interactivity/trigger-emotes.md#custom-animations">}}) uploaded as part of the smart wearable's files.
Expand Down

0 comments on commit e8b5250

Please sign in to comment.