Search Issue Tracker
Fixed in 2.0.11
Votes
3
Found in [Package]
2021.1.0a5
Issue ID
1336648
Regression
Yes
DomainReloadTests performance tests have regressed due to removal of built-in support for Visual Studio as a code editor
Tests affected:
DomainReloadTests.WhenEmptySceneWith100Assemblies_With1000MethodsEach
DomainReloadTests.WithAllEditorWindowsOpen
DomainReloadTests.EmptyScene
Platforms affected:
WindowsEditor
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Kitesurf
Aug 17, 2021 04:34
Why did Unity remove "Built-In Support" for Visual Studio as a code editor? please advise as this makes no sense.