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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment