Pley does quite a bit of optimization, compression, and post-processing to increase game performance for you - automatically.
In the Pley Game Manager post-processing is automatically applied to your build (after uploading it through the SDK). This is not to be confused with Unity's visual Post Processing stack. Our post-processing targets performance optimizations; it goes through the build and tries to optimize the game's code by applying a few patches providing an extra edge when running on WebGL. Once the post-processing is done, the build undergoes a compression process. One of the things this compression does is apply Brotli compression to the whole build - including your Asset Bundles if you're using them (Read about asset management here).
Unity Build Compression
We recommend that disabling build's compression in Unity's Publishing Settings. Pley handles compression for you. The SDK will automatically offer to disable compression for you when it analyzes your game.
But the main thing to note here is that we do all of this for you, automatically without you having to worry about it.
Post-processing and compression process
Both the post-processing and compression processes take time and how long they would take depends on the size of your game and how many assets it has. However, a player (including you) can run the game during this process. Note, however, when you do that, you're running the game without optimization and the performance you experience shouldn't be used as an indicator.
Updated 3 months ago