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
Comments (1)
-
GibTreaty
Aug 27, 2018 14:59
Having the same issue here in 2017.3.0f3
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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
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.