Debug in production

When running a scene that’s already deployed to land in Decentraland, there are a number of things you can try out to debug it.

Before deploying #

Preview #

Before you deploy your scene to Decentraland, make sure the scene runs well in preview using the latest version of the Decentraland SDK. See debug in preview .

Although there should always be backwards compatibility of content built with older SDK versions, some platform-level aspects are subject to change over time. For example, lighting, avatar animations, skybox textures, global UIs, etc. By running a preview with the latest SDK version, you’re using a newer version of the engine, which should render your scene in a way that’s closer to what’s used in production.

The test server #

You can deploy scenes to a test server as a staging environment, before publishing them to the live content servers. This server is not frequented by any players that visit Decentraland normally. To enter this server you must manually write its URL, but keep in mind that it’s not a private environment.

See The test server for details.

Quick reload #

If you need to reload the scene you’re standing on, write the following into the chat and push enter:

/reload

## About the publishing pipeline

Keep in mind that after each publish, an internal process optimizes all 3D models before they can be rendered. This takes around 15 minutes. If you visit the scene before this is done, the scene may appear broken. This process runs even if the 3D models were all previously published.

You can check the current state of this process for your scene using this tool . If the conversion is complete, all three variations of the assets should have green lights.

Report a bug #

If you encounter a problem that is not with your scene, but instead with the Decentraland SDK in general, please see Report a bug .