Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
Issue ID
1153361
Regression
No
Memoryless render textures do not have warning / error about being read from
Using memoryless render targets on graphics APIs that don't have support for memoryless render textures does not issue warnings or errors when using such textures for reading (e.g. setting as a sampled texture on a material or blitting from it).
Steps:
1. Download QA attached project
2. Open repro scene
Actual: The quad renders white, but no warning or error message in console.
Expected: The quad renders white, but with a warning or error message in console saying memoryless texture cannot be read or write to.
Reproducible in: 2019.3.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Add comment