Search Issue Tracker
Fixed in 4.0.0
Votes
2
Found in [Package]
1.1.2-preview
Issue ID
1022968
Regression
No
[HDRP] Console is spammed with errors when changing graphics API to Vulkan
The console is spammed with errors when changing graphics API to Vulkan
Steps to Repro:
1. Open attached project
2. Edit > Project Settings > Player
3. Other settings > disable auto graphics API for windows
4. Change graphics API to Vulkan
Actual Result:
1. The console is spammed with errors
2. Mesh disappears from the scene
Error:
1. Graphics.CopyTexture could not find destination D3D11 texture object. Maybe it is a RenderTexture that is not created yet?
2. Graphics.CopyTexture could not find source D3D11 texture object. Maybe it is a RenderTexture that is not created yet?
Occurring with
2018.2.0a8, 2018.2.0a3, 2018.1.0b13, 2018.1.0b5
Note that templates are available 2018.1.0b5 onwards
Environment:
Only on Windows
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
- Incorrect Burst Exception Control Flow in Editor due to Mono Handling of calli instruction
- [Linux] Packman options to add package from Git URL doesn't always show the window directly below the + button
- Editor redirects to a broken page when pressing question mark "?" in the Inspector window
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
- "Cyclic Prefab nesting not supported" error window is thrown when trying to nest two sibling prefab variants
syscrusher
May 19, 2019 02:31
I encountered this problem when testing with Unity 2018.1.9f2, creating a new HDRP project directly from the latest Unity Hub. Here is how I resolved it:
1. In the Project View, navigate to the Assets/Settings folder.
2. Right click and select Create...Rendering...High Definition Render Pipeline Resources to create an HDRP resources object.
3. Back in the Project View, select the HDRenderPipelineAsset object to open its inspector.
4. Drag and drop the new resources object into the Render Pipeline Resources field in the pipeline asset.
For me, this fixed the problem while remaining in Linear color space.
mflux
Jul 18, 2018 23:29
I also have this issue. Changing to HDR Render Pipeline, it complains about using Gamma color space (why not have this automatically change?). Changing it to Linear causes this console spam.