This page is dedicated to common issues surrounding rendering. If you are experiencing an issue that does not relate to rendering consider looking at one of the other pages in this section, which are also listed here.
A lot of times issues can be fixed by simply updating your plugin to the latest version, please make sure to check you are on the latest release version before looking further into this section. More info on how to do this here
If you are seeing a drop in performance when loading your playable in Safari, it is likely due to the fact that Safari has on average a lower performance rate than other browsers like Google Chrome.
This is due in part to reasons such as Safari having a less optimal JS array iteration.
- Optimise your playable further: E.g. reduce the amount of keyframes to no more than 10 per animation, reduce the vertex count on blendshapes to be as low as possible. Click here for more tips on optimisation.
If you are making use of TMP, and do not have the Resources folder marked for inclusion under Export type, this could be because the cause of the problem (As TMP settings are stored inside of the Resources folder).
- Tick the Resources option under Export type. More info on how to do this here.
This could be because shaders in WebGL are handled differently to shaders in Unity.
- For the sprite you wish to be rendered on top, change the renderer queue number in the shader settings to be higher than the shader for the sprite which is supposed to be underneath.
This could be due to having too many dense models being rendered in the scene.
- Select the model in Unity, click on the Model tab in the inspector, select Mesh Compression, and select one of the higher settings such as ‘High’. Then click ‘Apply’ at the bottom of the inspector.