Search Issue Tracker
Won't Fix
Votes
2
Found in
2018.2.0b4
Issue ID
1035810
Regression
No
Steam overlay artifacts appear in the Visual Studio opened from within Unity when using Steamworks
To reproduce:
1. Import the Steamworks package to an empty project
2. Add the SteamManager.cs from "Assets\Scripts\Steamworks.NET" to an empty Gameobject
3. Be online on Steam
4. Play the scene
5. Open any script from within the Editor in Visual Studio
6. Slightly move the Visual Studio window a few times
Expected result: The Visual Studio window gets all sorts of Steam overlay artifacts
Actual result: The Visual Studio window is not affected by the Steam overlay
Reproduced with: 2017.3.2f1, 2017.4.3f1, 2018.1.0f2, 2018.2.0b4
Notes:
- Does not reproduce with other code editors except Visual Code. Though they are minor and disappear after moving the window
- Only reproduces when the script is opened from within the Editor
- Artifacts disappear if the window is dragged to the other screen. Then re-appear after a few seconds
- Reproduces both in and out of playmode. When the scene has been played at least once
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.