Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2018.4.3f1
2019.1
2019.2
2019.3
Issue ID
1170073
Regression
No
ScalableBufferManager.ResizeBuffers doesn't resize buffers after setting camera.targetTexture to null
Repro steps:
1. Open attached project
2. Build and Run the application on a platform that supports Dynamic Resolution
3. Resize the buffers using the slider
4. Press "Set null texture" button which sets camera.targetTexture to null
5. Resize the buffers again using the slider
Actual: The GameObjects aren't scaled anymore
Reproducible with: 2018.4.5f1, 2019.1.12f1, 2019.2.0b10, 2019.3.0a11
Notes:
- Reproduced on Android with Vulkan, macOS/iOS with Metal and Windows with DX12
- No repro on Windows with Vulkan/DX11
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
- File watcher does not trigger after the AcquireFloatingLease and before the Entitlement check
- HDR Output gets disabled in the Editor when Reflection Probe is enabled during runtime
- The "Build and Run" Menu option tries to build for the selected Build Platform instead of the Active Build Platform
- Font kerning breaks at runtime when multiple UI Documents use different fonts
- MissingReferenceException occurs when entering Play mode with a locked GameObject in the Inspector
Resolution Note (2019.3.X):
when camera's targetTexture is set to null, the camera starts using the SwapChain's backbuffer which is not scalable. The camera's rendertargets (i.e. the swapchain backbuffers at this time) are not included in the ScalableBufferManager thus the resize buffers have no effect on those buffers.