Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b9
Issue ID
1008455
Regression
No
Building game with Api Compatibility set to .NET Standart 2.0 and blocks calls to CSCore.dll
How to reproduce:
1. Open given Unity project https://github.com/hallidev/UnityWASAPILoopbackAudio
2. Turn on any audio(Youtube, Spotify or any audio file)
3. Enter "Main" scene
4. Enter Play Mode
--notice that visual effects are working fine
5. Go File -> Build Settings -> Player Settings
6. Set Scripting Runtime Version to Stable(.NET 4.x Equivalent)
7. Set Api Compatibility level to (.NET Standart 2.0)
-- Enter Play mode again to see that everything is working fine
8. Press Build And Run
-- Notice that built game is not working as it should in the Editor
Expected result: Built game should be the same as we saw in the editor when entered play mode
Actual result: It seems to be not responding
Reproducible with: 2018.2.0a3, 2018.1.0b10,
Note: Everything is working fine when Api Compatibility Level is set to .Net 4.x
Note: Cannot test with 2017 versions because when Scripting Runtime Version is set to Stable(.NET 4.x Equivalent) there is no (.NET Standart 2.0)
Api Compatibility level and. And when it's set to Stable (.NET 3.5 Equivalent) it crashes.
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
- WebGL build dependencies are not refreshed until the Editor is restarted
- “Audio Random Container” allows adding unlimited number in “Audio Clips” numeric field, causing Editor to freeze
- In Deferred rendering path, mixed lights don't render when enabling "Use Rendering Layers" in the Decal renderer feature
- [Windows] Special characters in file names are sorted to the end of the alphabet in the Project window
- Information box icons are not contained within the information box bounds in Render Pipeline Converter window
Resolution Note:
The CSCore library appears to be using COM interop, which we do not support. This happens to work with the .NET 4.x profile, though, even though we do not specifically support it. The editor never uses .NET standard 2.0, it always uses the 4.x profile.