Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Fallout 4 VR with Script Extender and FRIK crashes on black screen regardless of Proton Version #498

Closed
6ooflames opened this issue Feb 20, 2022 · 3 comments
Labels

Comments

@6ooflames
Copy link

6ooflames commented Feb 20, 2022

I'm trying to use Fallout 4 VR with Script Extender and FRIK, but it crashes on the initial black screen regardless of which Proton Version im using. I've tried 6.3-8, 7.0-1 and Proton 7.1 and 7.2 GE.

Steps to reproduce the behavior:

  1. Install F4SEVR and FRIK and dependencies
  2. Rename Fallout4VR.exe to Fallout4.exe and f4se_loader.exe to Fallout4VR.exe and add [Loader] RuntimeName=Fallout4.exe to Data/f4sevr.ini
  3. Launch SteamVR & Fallout 4 VR
  4. See error

On Windows, people have gotten it working...

System Information:

@kisak-valve
Copy link
Member

Hello @6ooflames, we're tracking issues with games run with Proton in the Proton issue tracker, and this issue has already been reported at ValveSoftware/Proton#1069, so I've gone ahead and transferred this issue report to ValveSoftware/Proton#1069 (comment).

@6ooflames
Copy link
Author

This is not a duplicate of ValveSoftware/Proton#1069, as F4SE initialises successfully and even loads FRIK.dll and FO4VRTools.dll correctly. Should I open a new Proton issue report instead?

@kisak-valve
Copy link
Member

In general, we're also using one issue per unofficially supported game title on the Proton issue tracker, but in this specific case Skyrim VR and Fallout 4 VR got mashed together. If the older feedback is simply outdated, then it's probably fine where it is, but worth adding a note there, otherwise it'd make sense to split those two games apart if there's different behavior between them. It's also preferred to discuss mods in the same compatibility report as the unaltered game release.

Not the clearest advice given that you're focused on game modding instead of the game by itself, but that's the general intent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants