Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1147394
Regression
No
QualitySettings.streamingMipmapsMemoryBudget is always clamped down to 4096 MB even on 64-bit systems
How to reproduce:
1. Open the attached project "case_1147394-TextureStreamingLimit" and scene "SampleScene"
2. Ener Play Mode
3. Observe Console Window output
Expected result: "Actual Budget" and "Target Budget" are both at 4500 MB
Actual result: "Actual Budget" is 4096 MB even though "Target Budget" is 4500 MB
Reproducible with: 2018.3.14f1, 2019.1.0f2, 2019.2.0a13
Could not test with: 2017.4.26f1 (no texture streaming)
Note: the script Component "TextureBudgetAllocation.cs" attached to "MainCamera" tries to set QualitySettings.streamingMipmapsMemoryBudget to 4500 MB but cannot go over 4096. If there is no output in the Console Window after entering Play Mode, make sure that Texture Streaming is enabled in the Quality Settings
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment