Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0b9
2018.2.6f1
Issue ID
1075101
Regression
Yes
[HDRP] Shader property has mismatching texture dimension after switching Target Platform
How to reproduce:
1. Create new Unity project using "High-Definition RP" template
2. In the Build Window, switch the platform to UWP
Expected behavior: After switching the platform shaders are computed successfully.
Actual behavior: After switching the platform dozens of Console errors appear and objects in the scene are grey.
Reproducible with - 2018.2.0b9, 2018.2.6f1
Not reproducible with - 2018.1.9f2, 2018.2.0b8, 2018.3.0a5, 2018.3.0a11
Note: High-definition RP was introduced in 2018.1 (therefore the issue was not tested on versions prior 2018.1).
Example of the errors that are thrown:
Compute shader (Deferred): Property (_EnvCubemapTextures) at kernel index (7) has mismatching texture dimension (expected 6, got 5)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
Dieedi
Oct 24, 2019 12:34
can't edit my comment ... it was on 2019.2.0f1
Dieedi
Oct 24, 2019 12:33
Hello,
I got similar problem and solve by Just right click and choose reimport on High Definition RP package in project view/Packages
luckruns0ut
Jun 23, 2019 18:42
For the next person who runs into this problem like I just did for which this is one of the only results on google - I fixed it by just going to the package manager and removing hdrp and then re-installing it. Everything went back to normal afterwards.