Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.27f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
2023.3.0a3
6000.0.0b11
7000.0.0a1
Issue ID
UUM-37717
Regression
No
[DX12] "Remove texture only valid for surface data" error message in the Console when exiting Play mode
Reproduction steps:
1. Open user attached project "2023-beta-test.zip"
2. Enter Play mode
3. Activate Headset
4. Exit Play mode
Expected result: No error messages in the Console
Actual result: 3 error messages "Remove texture only valid for surface data" in the Console
Reproduced with: 1.6.0 (2023.2.0a6), 1.7.0 (2021.3.26f1, 2022.3.0f1, 2023.1.0b19, 2023.2.0a17)
Reproducible on: Windows 10
Reproducible with this device: Oculus Quest
Not reproducible with this device: Oculus Rift S
Note: Can’t test on Player, because the build fails
Customer states this can be reproduced without an XR Headset, it is just easier to do so with one:
"I was able to also reproduce this without XR, although it took more times entering play mode + exiting again (around 10 times); I also got Editor crashes when I tried to enter play mode more often. Seems some sort of memory leak, but the error message posted above “Remove texture only valid for surface data” is not very helpful I guess, as there ain’t no stacktrace."
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
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
- Scene View Camera overlay preview goes out of Scene View bounds when the Scene View is resized vertically
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.