Fallout 76 Public Test Server fails to stream, but production servers work

syscrusher

New Member
As noted in my previous post, aside from a minor performance issue I am successfully streaming Fallout 76 to Twitch using OBS.

Bethesda (the makers of Fallout) recently opened their former "Private Test Server" (to which I had access under NDA) to become the "Public Test Server", and they have specifically and publicly stated that the new content is no longer under embargo, and users of the PTS are free to discuss, review, and record sessions.

Initially, right after the PTS went from "private" to "public", I tried streaming it with OBS but failed with multiply-repeating errors from the game claiming that the video "hook" DLL was invalid or was not for this operating system -- but that same DLL works fine in the regular Fallout 76 servers. I assumed Bethesda must have some lingering anti-streaming system in place, and assumed they would get around to removing it eventually.

A few days ago, there was an update to the PTS, and the DLL errors are now gone, as I hoped they would be. However, OBS now simply streams or records a black screen from the PTS game -- but continues to work from the public servers.

Graphics settings are shared between the two game modes, although they do have different EXE files. The audio does stream or record from PTS, just not video.

Looking at the log, I have this message with the "anti-cheat compatibility hook" disabled:

22:14:59.475: [game-capture: 'Game Capture'] attempting to hook fullscreen process: Fallout76.exe
22:14:59.478: [game-capture: 'Game Capture'] using direct hook
22:14:59.481: [game-capture: 'Game Capture'] hook_direct: inject failed: -1

After stopping the stream and editing settings to enable that hook, the message changes to this:

22:17:27.843: [game-capture: 'Game Capture'] attempting to hook process: Fallout76.exe
22:17:27.846: [game-capture: 'Game Capture'] using helper (compatibility hook)

In both attempts, these messages repeat at intervals until I stop the stream.

I've tried running the game in full-screen mode instead of the usual borderless window mode, but that didn't help. I'm attaching my log file to this post.

I'm curious if anyone else has tried this yet, and gotten it to work, and if so, what you did to make that possible? Thanks!
 

Attachments

  • 2020-06-03 22-03-55.txt
    30.6 KB · Views: 4
Top