Search Issue Tracker
Fixed in 2017.2.X
Votes
1
Found in
5.6.0f3
Issue ID
910302
Regression
Yes
Editor returns an Internal compilation error when using 2 or more custom operators in one statement
Steps to reproduce:
1. Download and open the attached project
2. Observe console
Expected result: compilation succeeds normally
Actual result: "Internal compiler error: Index was outside the bounds of the array."
Reproduced on 5.5.0b9, 5.5.3p1, 5.6.0p4, 2017.1.0b4
Not reproduced on 5.4.5f1
Regression introduced in 5.5
Notes:
-The compilation error does not actually appear inside a code editor(Visual Studio)
-1 operator does not cause the error
Verified FIXED 5.6.1p3
Comments (1)
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
Invertex
May 13, 2017 09:16
Seems to be related to this issue which seems to have come back in p3/p4...
https://issuetracker.unity3d.com/issues/shader-errors-appear-in-console-after-building-postprocessing-asset-on-vulkan