Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.16f1
Issue ID
UUM-29463
Regression
No
Shaders in Xbox occupy significantly more RAM than on PC
Bug observed on Xbox series S.
Customer (Harebrained Schemes in this case) built their project for PC and Xbox, and the shader size in memory on Xbox is significantly that it is on PC.
Some shaders are almost twice the size, some are just slightly bigger.
Examples here in MB (see screenshot for more):
- HDRP/Lit - 84.1 to 178.4
- HDRP/LayerLit - 18 to 28
- Hidden/HDRP/FinalPass - 11 to 18
- HDRP/ Decal - 1.2 to 2.3
- some other Shader Graph shaders at least 10 of them are almost twice bigger according to screenshot
Other than that the render texture is also a lot larger on Xbox than on PC.
They opened this ticket
And we tried to reproduce it in an almost empty HDRP project(only with some game objects so the shaders are in use), and also observed the shader size difference.
The engineer (Roberto Ardia) working on this seems to more concern about render texture size difference – 196 MB on PC, 2.02 GB on XBox. (Side A is on PC, Side B is on XBOX) !Memory Profiler snaptshot compare_Side A PC_Side B Xbox.png!
Also the profiling is done on both Unity Profiler and PIX, results are similar.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
After looking into GPU captures, we could not see the issue that was described.
Resolution Note (2021.3.X):
After looking into GPU captures, we could not see the issue that was described.