| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
=Content Processing= | =Content Processing= | ||
| − | When you upload a piece of content to our servers, we run a variety of processes on it before building the final export packages. We build one package per platform (e.g. one for WebGL, one for standalone, one for each mobile OS, one for each console.) | + | When you upload a piece of content to our servers, we run a variety of processes on it before building the final export packages. We build one package per platform (e.g. one for WebGL, one for standalone, one for each mobile OS, one for each console.) This processing does take some time to perform depending on the content type. Regions typically take around 15 minutes to process depending on their size (a large multi-gigabyte region can take up to an hour), whereas virtual goods (such as [[Clothing]], [[Gestures]] or [[Vehicles]]) less than 5mb will process usually within 20 seconds. |
| + | |||
| + | =Content Queue= | ||
| + | When you upload content for processing it, we will process it in the order it is received, with a handful of exceptions. Virtual Goods less than 10mb in size will always process on a separate priority queue regardless of account status (this is to ensure you can quickly preview content that does not take long to process). | ||
| + | |||
| + | Other content will process on the larger region queue. We have a separate priority region queue for customers subscribing to a large region plan. Generally speaking we do aim for content to process quickly; during periods of large user growth, we may need to add additional processing servers | ||
| + | =What happens to your content= | ||
==Textures== | ==Textures== | ||
| − | Depending on the platform your textures are likely to be re-compressed into a native format for that platform, e.g. DXT1/5 on Standalone, JPEG for WebGL, etc. | + | Depending on the platform your textures are likely to be re-compressed into a native format for that platform, e.g. DXT1/5 on Standalone, JPEG for WebGL, etc. you can configure these settings prior to upload |
When you upload a piece of content to our servers, we run a variety of processes on it before building the final export packages. We build one package per platform (e.g. one for WebGL, one for standalone, one for each mobile OS, one for each console.) This processing does take some time to perform depending on the content type. Regions typically take around 15 minutes to process depending on their size (a large multi-gigabyte region can take up to an hour), whereas virtual goods (such as Clothing, Gestures or Vehicles) less than 5mb will process usually within 20 seconds.
When you upload content for processing it, we will process it in the order it is received, with a handful of exceptions. Virtual Goods less than 10mb in size will always process on a separate priority queue regardless of account status (this is to ensure you can quickly preview content that does not take long to process).
Other content will process on the larger region queue. We have a separate priority region queue for customers subscribing to a large region plan. Generally speaking we do aim for content to process quickly; during periods of large user growth, we may need to add additional processing servers
Depending on the platform your textures are likely to be re-compressed into a native format for that platform, e.g. DXT1/5 on Standalone, JPEG for WebGL, etc. you can configure these settings prior to upload