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
Comments (1)
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
- Video preview in the Inspector freezes shortly after the first play and does not recover until paused and replayed
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
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.