Search Issue Tracker
Fixed
Fixed in 1.8.20
Votes
1
Found in [Package]
1.8.18
Issue ID
BUR-2801
Regression
No
“Exception: Unable to resolve the method” error is thrown when directly compiling a Burst-compiled method
Reproduction steps:
1. Open the attached “Burst Inline Bug.zip” project
2. Navigate to Jobs > Burst > Open Inspector…
3. Click on the "NoiseTest(float32&, float32&, float32&, AddNoise`2[CheckerboardNoise,SpheresNoise]&)" method in the Burst Inspector window
4. Observe the Burst Inspector and Console window
Expected result: The method details are loaded and no errors are thrown
Actual result: The method fails to load and the “Exception: Unable to resolve the method” error is thrown
Reproducible with: 2022.3.55f1, 6000.0.35f1, 6000.1.0b3
Reproducible on: Windows 11
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Add comment