Fatal: Could not find ini

[Crimson13]

I'm getting an error "Fatal: Could not find ini" when running the textgen.exe. I did move my Steam and MO folders to a different hard drive a few weeks ago and am just now updating my Skyrim mod list. I'm having trouble finding out how to fix this, does anyone have ideas?

[LetGoMyLegHo]

  On 1/17/2018 at 10:08 AM, sheson said:

Start the games launcher once, so the registry is updated with the correct path information.

Hey guys, don't mean to bump an older thread so high, but I've started the launcher multiple times and my DynDOLOD and TexGen both still display this error.

[sheson]

https://forum.step-project.com/topic/12479-dynamic-distant-objects-lod-dyndolod-235/?p=208857

https://forum.step-project.com/topic/13029-dyndolod-236-skyrim-se-beta-with-dynamic-lod/?p=216737

https://forum.step-project.com/topic/13152-dyndolod-error-when-starting/?p=215985

https://forum.step-project.com/topic/12011-dyndolodtexgen-se-error-could-not-open-registry-key/?p=201268

[LetGoMyLegHo]

  On 2/28/2018 at 10:22 AM, sheson said:

https://forum.step-project.com/topic/12479-dynamic-distant-objects-lod-dyndolod-235/?p=208857

https://forum.step-project.com/topic/13029-dyndolod-236-skyrim-se-beta-with-dynamic-lod/?p=216737

https://forum.step-project.com/topic/13152-dyndolod-error-when-starting/?p=215985

https://forum.step-project.com/topic/12011-dyndolodtexgen-se-error-could-not-open-registry-key/?p=201268

Even bigger news, had deleted my skyrim.ini and skyrimprefs.ini, ran the default launcher, and it doesn't generate any new .ini files in my Documents\My Games\Skyrim Special Edition.

 

I assume this is what's causing the problem lmao

[sheson]

No idea what could cause that, but if the launcher can not create the INIs it probably does not create the registry entries either.

 

Reboot.

 

Make sure Skyrim is not installed into Program Files or any other special windows folder controlled by UAC.

 

Double check that not something like antivirus is interfering.

[LetGoMyLegHo]

  On 2/28/2018 at 8:55 PM, sheson said:

No idea what could cause that, but if the launcher can not create the INIs it probably does not create the registry entries either.

 

Reboot.

 

Make sure Skyrim is not installed into Program Files or any other special windows folder controlled by UAC.

 

Double check that not something like antivirus is interfering.

Have tried rebooting, installing Skyrim on not only C:\Steam but also D:\SteamLibrary, still no luck so far. Something's really messed up with the skyrim launcher unable to add/change the registry.

 

Will go look around for registry fixes. Have tried a couple but to no avail.

[sheson]

The launcher works fine. This is something with the OS or the general setup of steam or the game.

[Piranhaha]

Hi all,

 

I'm having an issue that I first observed with the first version of 2.36 beta. I was never able to fix it and went back to the 2.30 stable. I just tried updating to Beta 10 in hopes that it would work, and I'm still having the same problem. I'd really love to try to fix it this time.

 

I'm running DynDoLOD as an executable through Mod Organizer 2, for SSE. I have "-sse" as the argument for both the TexGen64 and DynDoLod64 executables. File paths are as follows:

 

Mod Organizer: "C:\Games\Utilities\Mod Organizer for Skyrim Special Edition\modorganizer.exe"

DynDoLod: "E:\Entertainment\Games\Mods\Specific - Skyrim Special Edition\DynDOLOD 2.36 Beta\DynDOLODx64.exe"

TexGen: "E:\Entertainment\Games\Mods\Specific - Skyrim Special Edition\DynDOLOD 2.36 Beta\TexGenx64.exe"

 

When I launch TexGen 2.30, it executes and generates textures correctly.

When I launch DynDoLOD 2.30, it executes and generates LODs correctly.

When I launch TexGen 2.36, it executes and generates textures correctly.

When I launch DynDoLOD 2.36, I get the following error:

 

[00:00:00.000] DynDOLOD based on xEdit x64 starting session 2018-03-21 15:59:44

[00:00:00.005] Using Skyrim Special Edition Data Path: C:\Games\Steam\steamapps\common\Skyrim Special Edition\Data\

[00:00:00.007] Using ini: -sse\My Games\Skyrim Special Edition\Skyrim.ini

[00:00:00.009] Fatal: Could not find ini

 

Does anyone know why it's adding "-sse" to the ini path instead of taking it as an argument?

 

 

Edit: Just realized I had asked this same question a few months ago.

- I ran Skyrim through its launcher as suggested. This did not fix the issue.

- I made sure that HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Bethesda Softworks\Skyrim Special Edition "Installed path" is set to the actual installed path (C:\Games\Steam\steamapps\common\Skyrim Special Edition). It is set correctly.

 

Is there anything else that could be causing the issue?

Edited March 21, 2018 by Piranhaha

[Piranhaha]

EDIT: **** me sideways. BitDefender quietly decided to block DynDOLOD without notifying me. I whitelisted it and it launches fine now. This whole freaking time it was BitDefender....   

To add to my previous post, I tried some exploration just to see if I could provide any potentially useful info.

If I remove the "-sse" argument, I get the following:

[00:00:00.000] DynDOLOD based on xEdit x64 starting session 2018-03-21 16:17:25

[00:00:00.004] Using Skyrim Data Path: C:\Games\Steam\steamapps\common\Skyrim\Data\

[00:00:00.007] Using ini: E:\Entertainment\Games\Mods\Specific - Skyrim Special Edition\TE\My Games\Skyrim\Skyrim.ini

[00:00:00.011] Fatal: Could not find ini

 

So it looks like there's a problem parsing the ini path when launching through MO2 (that wasn't there in DynDOLOD 2.30).

 

I can launch DynDoLOD 2.36 just by running the executable outside of Mod Organizer and it starts up fine (but then throws the expected error that it can't find its resources, because the resources are installed through MO2).

 

I tried moving DynDoLOD executable to the same drive as the Skyrim data path and updating the MO2 shortcut accordingly. When launching, I get a popup window that says "Fatal: Could not determine my documents folder" followed by:

 

[00:00:00.000] DynDOLOD based on xEdit x64 starting session 2018-03-21 16:21:47

[00:00:00.003] Using Skyrim Special Edition Data Path: C:\Games\Steam\steamapps\common\Skyrim Special Edition\Data\

[00:00:00.005] Using ini: 

[00:00:00.008] Fatal: Could not find ini

This occurs regardless of if I have "-sse" as an argument.

[Ostegun]

Guys not sure where to ask this.

 

When I try to run XLODgen64 I get this message:

 

SSELODGen 3.3.8 BETA x64 (9150D5C3) starting session 2018-12-12 12:25:42
Using Skyrim Special Edition Data Path: E:\Installed Games\Skyrim\The Elder Scrolls - Skyrim - Special Edition\Data\
Using Cache Path: E:\Installed Games\Skyrim\The Elder Scrolls - Skyrim - Special Edition\Data\SSEEdit Cache\
Using ini: C:\Users\16469\Documents\My Games\Skyrim Special Edition\Skyrim.ini
Fatal: Could not find ini

 

None of these paths are correct my Ini is at E:\Installed Games\The Elder Scrolls V Skyrim Special Edition\Data

Any idea why it's creating that new folder? How can I change where the program is directing XLODgen64.

[sheson]

  On 12/12/2018 at 6:57 PM, Ostegun said:

Guys not sure where to ask this.

 

When I try to run XLODgen64 I get this message:

 

SSELODGen 3.3.8 BETA x64 (9150D5C3) starting session 2018-12-12 12:25:42

Using Skyrim Special Edition Data Path: E:\Installed Games\Skyrim\The Elder Scrolls - Skyrim - Special Edition\Data\

Using Cache Path: E:\Installed Games\Skyrim\The Elder Scrolls - Skyrim - Special Edition\Data\SSEEdit Cache\

Using ini: C:\Users\16469\Documents\My Games\Skyrim Special Edition\Skyrim.ini

Fatal: Could not find ini

 

None of these paths are correct my Ini is at E:\Installed Games\The Elder Scrolls V Skyrim Special Edition\Data

Any idea why it's creating that new folder? How can I change where the program is directing XLODgen64.

Expand  

Buy the game via Steam, start the game through Steam. It will start the games launcher which will detect the graphics card and then create the INIs in the default INI location, which is C:\Users\[username]\Documents\My Games\Skyrim Special Edition\Skyrim.ini for Skryim Special Edition.

Alternatively the INI path can be set with the -i:"c:\Path\to\game.ini" command line parameter.

[Ostegun]

  On 12/12/2018 at 10:31 PM, sheson said:

Buy the game via Steam, start the game through Steam. It will start the games launcher which will detect the graphics card and then create the INIs in the default INI location, which is C:\Users\[username]\Documents\My Games\Skyrim Special Edition\Skyrim.ini for Skryim Special Edition.

 

Alternatively the INI path can be set with the -i:"c:\Path\to\game.ini" command line parameter.

I already have the command: -sse -i:"E:\Mod Organizer 2 - Lexys LOTD SE\profiles\Vanilla Skyrim SE\Skyrrim.ini" -o:"E:\Modding Utilities\xLODGen\SSELODGen_Output"

 

Still not working. It just crashes. Did I spell anything wrong in the arguments line?

 

I'm assuming by command you meant the arguments line.

[sheson]

  On 12/13/2018 at 3:50 PM, Ostegun said:

I already have the command: -sse -i:"E:\Mod Organizer 2 - Lexys LOTD SE\profiles\Vanilla Skyrim SE\Skyrrim.ini" -o:"E:\Modding Utilities\xLODGen\SSELODGen_Output"

 

Still not working. It just crashes. Did I spell anything wrong in the arguments line?

 

I'm assuming by command you meant the arguments line.

Do not link directly into MO profiles, that is prone to cause problems. Instead let it automatically use the native/official path to the INI like everyone else does and has no problems with.

 

If MO does not map the INI from the profile to C:\Users\[username]\Documents\My Games\Skyrim Special Edition\Skyrim.ini and if programs started from MO executable drop down can not access the INI, then there is something wrong with the general setup of the game and nothing will work properly.

 

If you say crashes, is there an error message or does it just close? That probably happens trying to access files under direct control of MO instead of the virtual mapped ones.

 

What happens when you use the latest xEdit version?

Edited December 13, 2018 by sheson

[Ostegun]

Good point. There is no my games folder under users.

 

The only ini files I find are on the MO2 profiles folder.

 

I've used Zedit with no issues whatsoever. I'm at the finish line of DarkLadyLexy legacy of the dragonborn SE. All other executables have worked without any issues. 0___0 mama mia

[Shadriss]

If the My Games folder doesn't exist, you likely didn't start SSE once through Steam - it creates all of that when you do. Or should anyhow. Give that one more shot - I think I remember that being advised at least once.

[sheson]

  On 12/13/2018 at 6:12 PM, Ostegun said:

Good point. There is no my games folder under users.

 

The only ini files I find are on the MO2 profiles folder.

 

I've used Zedit with no issues whatsoever. I'm at the finish line of DarkLadyLexy legacy of the dragonborn SE. All other executables have worked without any issues. 0___0 mama mia

xLODGen is based on xEdit, not zEdit.

 

Once the games launcher is started, the folder and files in My Games are created. Unless maybe the OS or some third party software is preventing the launcher from doing that. That should trigger some kind of message. If that doesn't work, let Steam install the legal version of the game into its normal folder structure and try again.

Edited December 17, 2018 by sheson