Search Issue Tracker
Fixed in 2017.3.X
Votes
2
Found in
2017.1.0b10
Issue ID
922577
Regression
No
Assemblies built with .NET 4.6 are not loaded on their first import
Steps to reproduce:
1. Delete 'Library' folder from the attached project (important)
2. Open attached project
3. Select "dotnet 35 scriptable object" in the project view and observe the inspector
4. Select "dotnet 46 scriptable object" in the project view and observe the inspector in comparison with "35 scriptable object"
Expected behavior: Assemblies built with .NET 4.6 are loaded on their first import (like 3.5)
Notes:
Reimporting the object doesn't fix the issue
Navigating to "Assets/Create/" doesn't show "New .NET 4.6 scriptable object"
In 2017.2.0a3 selecting "dotnet 46 scriptable object" in the project view throws null reference exception
Workaround:
Restart Unity
Reproducible with: 2017.1.0b1, 2017.1.0b10, 2017.2.0a3
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
FeastSC2
Aug 15, 2017 00:49
In which version has this been fixed? It's not fixed for me!