Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b1
Issue ID
903675
Regression
No
[New Scripting Runtime] Errors on switching from the new runtime to the old one
1. What happened
For 'Chronos - Time Control' A$ package, when switching from New Runtime to Stable, after Editor restart and project reload, I'm getting lots of exceptions, like "TypeLoadException: Could not load type 'System.Runtime.CompilerServices.ExtensionAttribute' from assembly 'Assembly-CSharp'."
Also looks like something gets broken within Editor itself - I've tried opening 'Player Settings' and those looked as if in Debug Inspector mode, although being in Normal.
2. How we can reproduce it using the example you attached
The project is in a state after-the-issue-had-occurred.
To get a new one:
- New project
- Import 'Chronos - Time Control' A$ package
- Switch the runtime to the new one (+ restart)
- Switch the runtime to the old one (+ restart)
- See Console for errors
Comments (1)
-
woondal
May 10, 2017 07:27
This is not fixed. Still happens on 2017.1.0b3
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
- 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
This is a duplicate of issue #903078