Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b1
Issue ID
903756
Regression
No
Unity can not be launched after downgrading from .NET 4.6 to .NET 3.5
Unity can not be launched after downgrading from .NET 4.6 to .NET 3.5
Reproduction steps:
1. Create new project.
2. Download asset "Chronos - Time Control"
3. Change Scripting Runtime Version to .NET 4.6
4. Restart project.
5. Change Scripting Runtime Version to .NET 3.5
6. Restart project.
Expected result: Unity launches.
Actual result: Unity does not launch.
Workaround: Launch project on other version.
Reproduced on: 2017.1.0b1
Comments (1)
-
woondal
May 10, 2017 07:23
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
This is a duplicate of issue #903078