Search Issue Tracker
Fixed in 2019.2.X
Votes
4
Found in
2018.1.1f1
Issue ID
1049270
Regression
No
[Graphics] Direct3D 12: missing support for generating mipmaps on 3D render textures
[Graphics] Direct3D 12: missing support for generating mipmaps on 3D render textures
1. What happened
We use 3D (volume) render textures with runtime-generated mipmaps in our game, and while investigating a graphical corruption issue on Direct3D 12 I noticed the D3D12 backend doesn't seem to have support for GenerateMipmaps with 3D render textures (or array textures either).
Our game has dynamic volumetric clouds which are generated (and can be user-configured, if a user creates their own level) at runtime. Some of the volumetric information is calculated and stored in mipmapped 3D render textures by using a compute shader to write to the first mipmap level and then calling GenerateMips after the compute dispatch.
Comments (1)
-
soleron
Sep 15, 2019 15:22
This issue is still there in 2019.x.x versions of the engine, and 2020.1.x.
Needs to be fixed as volumetric systems become essential in newer versions of Unity. Especially when people are using DXR where DX12 is the only way forward.
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_dump_native_crash_info when changing a Particle System Renderer’s Material Shader to Standard Unlit
- VFX Prefab doesn’t have Preview icon in Project window and Preview window is empty in Inspector window
- Visual Effect Graph error message does not disappear and lasts forever until the Visual Effect Graph is reopened even when the error causing connection/node is deleted and Visual Effect Graph is saved
- “RenderSettings customReflection texture has invalid type” error keeps getting thrown even when Environment Reflections was set back to Skybox from Custom with an invalid texture
- Particle System with the custom Material breaks the Scene view when the material is using a Shader Graph with the Texture with the power of negative value
Resolution Note (fix version 2019.2):
this is a not a bug, but a feature to be implemented in the future releases.