Search Issue Tracker
Fixed
Won't Fix in 2021.3.X
Fixed in 2022.3.24f1
Votes
0
Found in
2021.3.34f1
2022.3.18f1
Issue ID
UUM-61560
Regression
No
The 'Read/Write' flag on Texture2DArray isn't taking effect
How to reproduce:
1. Open the attached “Repro” project
2. Make sure the ‘Read/Write' flag for ‘Assets/tex2d’ Asset is set to false
3. Build it using the 'Development Build' setting in Standalone Player
4. Open the Memory Profiler (Window > Analysis > Memory Profiler) and search for 'tex2d' in the search bar
5. Observe how much 'tex2d’ uses in 'Graphics (Estimated)' and in 'Native' categories
Expected result: tex2d will use 1.3MB in 'Graphics (Estimated)' and less than 1KB in 'Native'
Actual result: tex2d is consuming 1.3MB in both 'Graphics (Estimated)' and 'Native'.
Reproducible with: 2022.3.18f1
Not reproducible with: 2023.2.7f1, 2023.3.0b4
Reproducible on: M1 MacOS 14.2
Not reproducible on: No other environment tested
Note: Using 2021.3.34f1 the Graphics (Estimated) is not present due to the older version of the Memory Profiler, but the Native Memory is 1.3MB
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2021.3.X):
Fixing this bug properly requires us, on upgrade, to force a full re-import of all textures, regardless of whether the project is affected by this issue or not.
In the case of the 2021 LTS, we believe that a backport is thus likely to create more pain than it would remove: as such, we are opting to close this port as "Won't Fix".
UI and documentation for 2021 LTS will be updated to reflect the fact that the "Read/Write" toggle has no effect on Texture2DArrays and Texture3Ds.