Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a4
Issue ID
1185697
Regression
No
[Code Optimization] "Debug"/"Release" Mode not updated after Editor restart
Reproduction steps:
1. Open "optimization_tests.zip" project
2. "Preferences" -> "General" -> "Code Optimization on Startup" -> "Debug" (If it was already "Debug", switch to "Release" and back again)
3. In the Main Editor window, at the bottom right corner, press the Bug icon -> "Switch to release mode"
4. Wait for it to re-compile
5. Re-open the project
6. "Window" -> "General" -> "Test Runner"
7. Run EditMode test "IsDebugAssembly"
Expected Result: Test passes
Actual Result: Test fails as the script/assembly has not been recompiled at startup
Reproduced with: 2020.1.0a6, 2020.1.0a4
Could not reproduce on, because feature implemented only on 2020.1.0a4: 2020.1.0a3, 2020.1.0a1, 2019.3.0b4, 2019.2.7f2, 2018.4.10f1, 2017.4.32f1
Note:
To fix, a manual Reimport of the "Tests.cs" script is needed
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
Add comment