Can't run Destiny 2 over steam in-home streaming

[eternicode]

Hello, I can't seem to get this to work with Destiny 2 and steam in-home streaming. I've got the exe in the D2 program files folder, my steam shortcut is pointed to the exe with "dst2" as a parameter. It seems to launch the game correctly on the host, but on the client it sits on the battle.net launcher (though this becomes non-responsive, in the sense that I can't click anything and mousing over the battlenet UI doesn't do any of the animations one would expect) for a bit, then closes altogether (furthermore, I can hear the D2 audio until the steam window closes). After this, the host is still running D2, it just seems that steam is losing the streaming connection for some reason.

Is bnetlauncher known to work well with steam in-home streaming? Is there something I've missed? I enabled the debug logs, and didn't notice anything amiss there -- it gets to "Closing battle.net child game process and starting it under bnetlauncher" and "Waiting for destiny 2 to exit", and nothing else until "Exiting".

[2017-10-25 02:59:24.4486]: Battle.net Launcher for Steam version 1.18.6465.31319 started
[2017-10-25 02:59:24.4557]: Environment: Microsoft Windows NT 10.0.14393.0 (4.0.30319.42000), 64bit
[2017-10-25 02:59:24.4577]: Getting Machine details:
[2017-10-25 02:59:24.6870]: OS: Microsoft Windows 10 Home Single Language (10.0.14393, 64-bit, 1033)
[2017-10-25 02:59:24.6900]: CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz; RAM: 16384MB
[2017-10-25 02:59:24.6930]: GPU: NVIDIA GeForce GTX 980 Ti (4095MB, 23.21.13.8800)
[2017-10-25 02:59:24.6950]: HDD: ST4000LM024-2AN17V, Samsung SSD 850 EVO M.2 500GB
[2017-10-25 02:59:24.6990]: battlenet URI handler appears to present and correct
[2017-10-25 02:59:24.7020]: Checking for other bnetlauncher processes
[2017-10-25 02:59:24.7040]: No other bnetlauncher detected
[2017-10-25 02:59:24.7070]: Given parameter: dst2
[2017-10-25 02:59:24.7091]: Known key for game 'Destiny 2'
[2017-10-25 02:59:24.7369]: battle.net client not running, trying to start it
[2017-10-25 02:59:33.4791]: battle.net client is fully running with pid = 9756
[2017-10-25 02:59:33.4826]: Issuing game launch command 'DST2' at '02:59:33.4821'
[2017-10-25 02:59:33.5212]: Searching for new battle.net child processes for the game
[2017-10-25 02:59:33.5829]: No child process found.
[2017-10-25 02:59:34.1406]: Found battle.net child process started at '02:59:33.7253' with pid = 11544
[2017-10-25 02:59:34.1436]: Selecting battle.net child started at '02:59:33.7253' with pid = 11544
[2017-10-25 02:59:34.6480]: Attempt 1 to find start parameters
[2017-10-25 02:59:34.7794]: Filename = C:\Program Files (x86)\Destiny 2\destiny2.exe
[2017-10-25 02:59:34.7823]: Arguments =  -uid destiny2 DST2://
[2017-10-25 02:59:34.7849]: Closing battle.net child game process and starting it under bnetlauncher
[2017-10-25 02:59:34.8269]: Closing battle.net client.
[2017-10-25 02:59:34.8991]: Waiting for destiny 2 to exit
[2017-10-25 03:00:21.7298]: Exiting

Any help would be greatly appreciated! :)

[dafzor]

bnetlauncher is working correctly, it's just destiny blocking Steam from doing it's magic. Please refer to issue #10 for additional details.