Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0a5
2018.1.0b4
Issue ID
999038
Regression
Yes
ScriptableObject values are not present after compilation
Steps to reproduce:
1. Open user attached project
2. Create Scriptable Object script
3. Create an asset of SO
4. Change some code in IDE to force compile
Expected result: ScriptableObject values should be present after compilation
Reproduced in: 2018.1.0b7, 2018.1.0a7, 2018.1.0a5
Does not reproduce in: 2018.1.0a4, 2017.3.1p1, 2017.2.1p4
Regression since: 2018.1.0a5
Fixed in: 2018.2.0a3, 2018.1.0b10
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
Add comment