Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.2
2019.3
2019.3.0f6
Issue ID
1214262
Regression
Yes
[HDRP][D3D12] "generating mipmaps for array textures is not yet supported" error thrown on switching graphics API to D3D12
On creating a new project with HDRP template and switching graphics API to D3D12, "generating mipmaps for array textures is not yet supported" is thrown in console. Refer the attached screenshot
Steps to reproduce:
1) Create a new project with HDRP template
2) Switch Graphics API to D3D12
3) Observe the console
Actual result: "generating mipmaps for array textures is not yet supported" is thrown in console
Occurring on: 2019.3.0f6, 2019.3.0a1, 2019.2.11f1, 2019.2.0a1
Working fine on: 2020.1.0a21, 2019.1.14f1
Stack trace: d3d12: generating mipmaps for array textures is not yet supported.
Environment: Only on Windows
Comments (7)
-
Havie
Feb 12, 2022 21:22
Sooo on 2019.4.0 LTS does that mean we can't enable raytracing (requires DirectX12) ?
Do we just ignore the error being printed to the console constantly?
-
JusticarJohn
Dec 02, 2021 10:15
It fixed my issues with Unity version 2019.3.12f1. I just remove the Direct3D12 and now I'm working with 11.
-
YaroslavSm
May 11, 2021 17:45
Delete Direct X12 in Player Settings to fix this
-
denedi2004
Feb 16, 2021 02:41
2019.4 LTS. I still have this error. Fix please.
-
GameRickster
Jan 20, 2021 01:59
Has there been a fixed? Do you turn of DX12 and work with DX 11?
-
Magasenakwa
Jul 31, 2020 06:07
We are locked into 2019 LTS and simply cannot upgrade to 2020 yet. Is this just a meaningless and annoying message we are going to see forever or does this error actually indicate that RayTracing simply won't work without DX12?
The docs say that Raytracing is supported in DX11but the wizard sees it as an error if you don't use DX12 so not sure if I should trust Unity's documentation or Unity's configuration wizard (since they clearly don't agree) but we are starting out with Raytracing now and the first thing we see is "Error! Error! Error!" so... what do we do? :(
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2020.1):
There will be no fix for this bug for 2019.3
Verified fix in,
Version: 2020.1.0a21.2690
Revision: trunk 4ea9a24ebde1
Built: Thu, 23 Jan 2020 03:51:25 GMT