After updating to 3.6 I’ve noticed that if my game is fullscreen breakpoints no longer cause Visual Studio to come into the foreground. Instead the game window gets stuck in the foreground (can’t alt-tab, task manager gets stuck behind it too) with a black screen and I have to open task manager on another desktop workspace and kill vshost32.exe. This sounds like it could be something wrong with my VS configuration, but I’m pretty sure I didn’t change anything that would be related to this behavior. Anyone have a solution?
Fast ring. While I’d like to snag Pro, that’s $$ I can’t afford at the moment.
While we’re on the topic I’d like to reinforce how much of an improvement to Windows the Linux subsystem is. It’s almost like having a real dev machine lol.
While I have had a similar issue with games like BF3, this could or may not be related to the Fast Ring… try ah, can you create a second desktop in Home editions?
I’d like to point out that it wasn’t happening before upgrading to 3.6 and there hasn’t been a Windows update during this timeframe. Fullscreen debug worked normally.
AFAIK this has always been an issue. The debugger and hardware full screen don’t play nice together MonoGame also has a soft fullscreen option that just makes the window borderless and the size of the display. Maybe the default changed in 3.6? Try setting GraphicsDeviceManager.HardwareModeSwitch to false.
Fullscreen exclusive mode doesn’t like switching back to Visual Studio when something breaks, either a breakpoint or exception. I remember having fun with this all the way back in the early days of DirectX. A reason to have dual monitors (which I couldn’t live without now) and to use soft fullscreen mode.
MonoGame also has a soft fullscreen option that just makes the window borderless and the size of the display. Maybe the default changed in 3.6? Try setting GraphicsDeviceManager.HardwareModeSwitch to false.