search

WombatFromHell / OriginSteamOverlayLauncher

An executable wrapper for Steam to make third-party launchers more convenient to use with a Steam Controller
MIT License
411 stars 25 forks source link

Detroit: Become Human -- Steam Link Black Screen #54

Closed Irastris closed 3 years ago

Irastris commented 4 years ago

After struggling to get D:BH to recognize my game controller, I stumbled across this project. After a little bit of troubleshooting, mostly involving moving OSOL outside of the game dir, it launches with full controller support.

Now, however, I'm getting a black screen when also trying to remote play. Could this have anything to do with the game being a Vulkan title? I know it's a little bit outside of this project's scope, but I wanted ask just in case.

Thanks.

WombatFromHell commented 4 years ago

You may need to try using GloSC if the Steam overlay on its own doesn't work properly with the game in question.

Fortunately, you can still use OSOL's launcher management with GloSC. Just add the path of your OSOL launcher to a GloSC target and then use the GloSC-created shortcut from Steam.

Irastris commented 4 years ago

The Steam overlay works fine, it's the streaming portion that dies. I forgot to mention that I have an AMD GPU, but I've already disabled the external events service.

If I look at my monitor, the game is rendering perfectly plus overlay, full controller support. If I look at my TV with the Steam Link, it's either frozen on a black screen or a single frame of the game.

GloSC is outside of my scope as I'm attempting to use a standard Xbox controller.

WombatFromHell commented 4 years ago

I don't personally own a Steam Link but I have used the Remote Play function a few times and generally if the Steam overlay functions then the host should be able to stream the game as well.

I'll ask around and get back to you.

Irastris commented 4 years ago

It definitely seems like an issue with OSOL rather than the Steam Link as a whole. If I just launch Detroit with Steam, which causes the controller and overlay to not function, it will display Detroit just fine after alt-tabbing to it.

Irastris commented 4 years ago

I believe the issue may be with the Steam Overlay entirely. It appears to maybe not support however Quantic Dream is doing fullscreen/borderless. A workaround is to set the game to a maximized window at the cost of a lower capture quality. Between video compression and sitting couch distance away, however, it will suffice.

My mistake.

michaelphagen commented 4 years ago

GloSC is outside of my scope as I'm attempting to use a standard Xbox controller.

GloSC was created to allow the steam controller to work in any non-steam title, but it allows steam input (which is what your Xbox controller is using when you launch games with the overlay enabled) in any game, regardless of controller type.

Definitely give it a shot if you haven't already

Irastris commented 4 years ago

GloSC ... allows steam input ... in any game, regardless of controller type.

Ah, interesting. They certainly don't make that clear on their page.

Either way, after settling for my workaround, the game was a stuttering mess despite meeting system requirements, go figure. Getting real sick of things like that happening as a paying customer.

michaelphagen commented 4 years ago

Is the game a "stuttering mess" regardless of whether or not you are streaming?

Irastris commented 4 years ago

Is the game a "stuttering mess" regardless of whether or not you are streaming?

Indeed, though interestingly enough the demo was perfect.

MartySouth commented 4 years ago

After struggling to get D:BH to recognize my game controller, I stumbled across this project. After a little bit of troubleshooting, mostly involving moving OSOL outside of the game dir, it launches with full controller support.

Now, however, I'm getting a black screen when also trying to remote play. Could this have anything to do with the game being a Vulkan title? I know it's a little bit outside of this project's scope, but I wanted ask just in case.

Thanks.

I'm struggling to get D:BH run via Steam. Could you elaborate on what you did to get it done beside "moving OSOL outside of the game dir"? Are there special arguments I should enter into "OriginSteamOverlayLauncher.ini"?

Irastris commented 4 years ago

Could you elaborate on what you did to get it done beside "moving OSOL outside of the game dir"? Are there special arguments I should enter into "OriginSteamOverlayLauncher.ini"?

Simply follow https://github.com/WombatFromHell/OriginSteamOverlayLauncher/wiki/Epic-Games-Launcher

MartySouth commented 4 years ago

Could you elaborate on what you did to get it done beside "moving OSOL outside of the game dir"? Are there special arguments I should enter into "OriginSteamOverlayLauncher.ini"?

Simply follow https://github.com/WombatFromHell/OriginSteamOverlayLauncher/wiki/Epic-Games-Launcher

Nope, doesn't work. I tried multiple times, but every time the game fails with a dump-file in the "F:\Epic Games\DetroitBecomeHuman\"-folder.

This is in my ini-file which is located in the "F:\SteamLibrary\steamapps\common\DetroitBecomeHuman"-folder:

[Paths] LauncherPath=C:\Program Files (x86)\Epic Games\Launcher\Portal\Binaries\Win64\EpicGamesLauncher.exe GamePath=F:\Epic Games\DetroitBecomeHuman\DetroitBecomeHuman.exe LauncherArgs= LauncherURI=com.epicgames.launcher://apps/Columbine?action=launch&silent=true GameArgs= MonitorPath= PreLaunchExecPath= PreLaunchExecArgs= PostGameExecPath= PostGameExecArgs= [Options] ReLaunch=True SkipLauncher=False CloseLauncher=True AutoGameLaunch=True MinimizeLauncher=False ElevateExternals=False ForceKillExternals=False PreGameLauncherWaitTime=15 PreGameWaitTime=0 PostGameWaitTime=0 ProcessAcquisitionTimeout=120 InterProcessAcquisitionTimeout=15 GameProcessAffinity= GameProcessPriority=Normal [Info] ReleaseVersion=1.0.9.9

Irastris commented 4 years ago

I don't know what to tell you, that's all I had to do. Initially, I overlooked the suggestion of removing OSOL from the game dir, which caused EGL to say the game was already running. Pushing OSOL to my portable software directory solved launching for me.

WombatFromHell commented 4 years ago

Like I said the other day, if OSOL by itself doesn't work to solve the issue then you might try combining OSOL with GloSC; OSOL for launcher management, and GloSC as an overlay workaround so Steam's BPM overlay doesn't cause the game itself to crash. This is also sometimes necessary for Origin/UPlay games, as the launcher's overlay conflicts with Steam's and either one will refuse to function. GloSC sort of solves that problem by letting Steam's overlay hook into a separate window instead.

MartySouth commented 4 years ago

This all is too much hassle for a game I don't even need an overlay. I added iexplorer.exe as a non-steam game and the game url as arguments to get it run. I also disabled the Steam overlay via BPM to avoid it conflicting with the EGL.