8000 SFEdit looks for FO4 registry key, fails to launch · Issue #1366 · TES5Edit/TES5Edit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

SFEdit looks for FO4 registry key, fails to launch #1366

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.

Sign up for GitHub

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

Jump to bottom
Open
mhkul opened this issue Jul 25, 2024 · 3 comments
Open

SFEdit looks for FO4 registry key, fails to launch #1366

mhkul opened this issue Jul 25, 2024 · 3 comments

Comments

@mhkul
Copy link
mhkul commented Jul 25, 2024

What is the version of xEdit you are using?
FO4Edit 4.1.5f x64 (C0DCE642) starting session 2024-07-25 09:52:27

Describe the bug
When attempting to launch xSFEdit, it displays error: "Fatal: Could not open registry key: \SOFTWARE\Bethesda Softworks\Fallout4\ This can happen after Steam updates, run the game's launcher to restore registry settings" When dismissing the message FO4Edit launches and shows in the messages window:

Using Fallout4 Data Path:
Using Scripts Path: C:\xEdit\Edit Scripts
Using Cache Path:
Using ini:
Fatal: Could not find ini

No functionality is available at this point.

To reproduce
Steps to reproduce the behavior:

  1. Launch xSFEdit64.exe or xSFEdit.exe
  2. See error message
  3. Proceed to non-functional FO4Edit instance.

Expected behavior
SFEdit launches instead of FO4Edit and does not check for non-existent FO4 installs.

Screenshots
xedit error
wrong game

Additional context
This machine has never had FO4 installed on it.
@taosecurity
Copy link
taosecurity commented Jul 25, 2024 •
edited
Loading

Run the g version, not f. And you’re missing 1 in the name. I launch the default binary with the -sf1 argument.

@jbostrus
Copy link
Contributor

Either rename the EXE to have SF1 in the filename, or specify -SF1 as a command line argument.

@mhkul
Copy link
Author
mhkul commented Jul 25, 2024

-SF1 argument indeed fixes it, thanks. I'm guessing from what @taosecurity says the fix is already in g and this can be closed right way when that releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@taosecurity @jbostrus @mhkul
0