Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I think I will start digging more into the properties of the games that work and the ones that don't to compare.
A trigger that seems to make it occur more frequently for me is using downsampled higher resolutions with the game. Not using them doesn't guarantee it won't happen however (Metro 2033 Redux for example refuses to maintain focus when launched from BP mode regardless of resolution, has to be run from desktop to be usable at all), but happens with somewhat less frequency if the res of the game is the same 1080p as my monitor.
Specs: Pentium G4560
Mem: 8 GB DDR4-400
GPU: Radeon RX 560 4GB
Mitigation Attempts:
- Steam beta and non-beta clients
- All running tasks killed as much as possible
- Latest Beta Crimson drivers, as well as default drivers installed with Windows 10 April Update
It might help the developers troubleshoot this problem... So Post back with the results...
Cheers and Good Luck
MartyWF
To do this:
• Right click on Steam's executable (Default location is: C:\Program Files (x86)\Steam)
• Under the Compatibility tab, ensure the "Disable fullscreen optimizations" option is checked.
Once this is done, restart the computer and check if the issue persists.
Please let me know if this solves your issue.
Whoo-hoo! Indeed it does! Tested Metro Redux, Arkham Knight, Zombi, Bioshock - 4 games previously that either wouldn't start at all or required you to alt-tab after doing so when launched from BP. Now all launch perfectly and stay in full screen.
I was actually testing that for the games .exe's themslves as I'm aware of the full-screen 'optimizations' Win10 made, never thought to try it with Steam's own .exe which makes sense in retrospect.
Thanks for the quick reply.
I'm the OP. This fixes it, both on Stable and Beta, for both BPM locally with overlay and also for BPM Streaming.
Thanks very much for your help. :)
Julie
x
Saves me of going through deinstallation.
So happy right now :)
Thanks for the help...
After quite some research, I nailed the culprit to the "Fullscreen Optimizations" feature on WIndows 10. As I understand it, the main benefit from this feature is to enable fullscreen games to behave as if they were windowed applications for overlay purposes and quick/smooth alt+tabbing transitions between the game and other applications. Many have suggested to disable FSO for every individual game application. I tried this and it indeed fixed the problem for me. However, not being satisfied with this patchwork solution, I decided to dig a little deeper and figured out that Windows 10 is also applying "FSO to the Steam application itself. I then enabled back FSO for all the Steam games I had disabled it and instead just diabled it for the Steam application. The result was the same, all my games launched as they normally would.
My suspicion is that there is a concfict between Steam and the games themselves when both are launched as fullscreen applications, specially when Steam is in Big Picture Mode. The way Steam is currently coded might trigger Windows to recognize it as the main application and place it in the foreground by default, thus auto-minimizing all/most games into the taskbar, rather than treat it as an overlay as it should. This suspcion is reinforced by the fact that when this began to happen to me, I also lost the ability to show the Steam FPS Counter on all of my games. Something I have yet to solve.
I'm glad I found this thread with official Valve confirmation that my efforts were well placed. Even if I happened to find this after arriving to the same solution on my own. Hopefully, we can get more feedback as to the nature of this problem and whether a more elegant solution can be achieved.
For reference purposes: I'm running the latest Windows 10, 1803 (KB4103721); Radeon Adrenaline 18.5.1 Graphics Driver; Steam Client May 18, 2018 Build; Mouse/Keyboard/DS4 Controller, Launching games in Desktop mode with "Use the Big Picture Overlay when using a Steam Input enabled controller from the desktop" enabled.
+1