Search Issue Tracker
By Design
Votes
0
Found in [Package]
Issue ID
1127061
Regression
No
[Vulkan] LWRP shows artefact in Vulkan player
Steps:
1.Open attached project in comment
2. Switch to PC/Desktop platform
3. In PlayerSettings change to use Vulkan Editor
4. Make Vulkan Player build
Please see attached image for actual result.
Reproducible in: 2018.3.8f1, 2019.1.0b4, 2019.2.0a5
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
- Crash on mono_domain_jit_foreach when performing various Unity operations
- Error is thrown when playing audio through Timeline in a Windows Server Build
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
Resolution Note:
This is an error in the project: In TressFXRenderer.cs the code uses "_CameraColorTexture" and "_CameraDepthTexture" to set the render target to current camera's color and depth buffers, but these are not necessarily available in LWRP. You can actually see the warnings in the console about these when the TressFX system tries to call SetRenderTarget with these IDs. As those are not found, the SetRenderTargets call is ignored, and the next draw call just happens to use the previously set render target (which is the INT32 depth buffer) as an UAV binding, causing all sorts of errors. I believe this also causes the DX11 rendering problems. Closing as "By Design".