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?

[sam_dmitry]

Hi. If you use MO, you mast add arguments "-sse"
See my screen http://prntscr.com/n3e36y

[sheson]

  On 10/7/2017 at 7:39 PM, Crimson13 said:

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?

My hunch is that you have Skyrim SE and didn't set the -sse command line parameter and so instead of Skyrim SE Skryim.ini it is looking for the ini of Skryim which you do not have.

Edited October 7, 2017 by sheson

[Crimson13]

It's regular Skyrim actually. I ain't touching SE until I can get about nearly all my mods working with it.

[sheson]

  On 10/8/2017 at 12:23 AM, Crimson13 said:

It's regular Skyrim actually. I ain't touching SE until I can get about nearly all my mods working with it.

There should be a line right above the fatal message that says "Using ini: c:\Users\[user name]\Documents\My Games\Skyrim\Skyrim.ini" - that is where it should be.

 

Start the game through the launcher once to update all settings.

If the ini is there, then something might preventing read access or some windows function is returning a wrong result. You could also test with xEdit.exe

 

You can use a command line parameter to define where the ini is

-i:"c:\Users\[user name]\Documents\My Games\Skyrim\Skyrim.ini"

Edited October 8, 2017 by sheson

[Crimson13]

That did it. Thanks man.

[Piranhaha]

I just tried to launch TexGen via Mod Organizer 2 using the -sse argument and got the following error:

 

[00:00:00.000] TexGen based on xEdit x64 starting session 2018-01-04 02:42:19

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

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

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

 

I believe I used the exact same parameter for DynDOLOD 2.30 and it launched just fine. Did I miss something that changed between versions? Why is it appending "-sse" to the ini path?

[sheson]

  On 1/4/2018 at 10:43 AM, Piranhaha said:

 

I just tried to launch TexGen via Mod Organizer 2 using the -sse argument and got the following error:

 

[00:00:00.000] TexGen based on xEdit x64 starting session 2018-01-04 02:42:19

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

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

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

 

I believe I used the exact same parameter for DynDOLOD 2.30 and it launched just fine. Did I miss something that changed between versions? Why is it appending "-sse" to the ini path?

 

Start the game from the launcher once, so the registry settings are updated with the correct path information.

 

If that is not it, double check the command line parameter. You maybe accidentally adding a switch that can be used to define the path to the INI.

Edited January 4, 2018 by sheson

[joethemusicman]

Sorry if this has been covered previously, but a search of the forums didn't return anything particularly helpful.

 

I'm following the guide for STEP: Core, and having trouble right at the tail end when you have to install and run DynDOLOD and TexGen. I get DynDOLOD Resources installed in MO just fine, create some dummy folders as the guide instructs, but then when I go to run the TexGen executable in MO, it stalls out immediately and says "Fatal: Could not find ini". Seems like this could be a stupid simple problem, but I can't for the life of me figure out what to do. Followed the instructions on the STEP guide to a T, and running into this wall right at the end.

 

Help would be much appreciated! Thanks y'all.

[joethemusicman]

Here's what the output window shows, seems like it has something to do with file structure or something:

 

[00:00:00.000] TexGen based on xEdit starting session 2018-01-16 23:52:26

[00:00:00.016] Using Skyrim Data Path: 

[00:00:00.027] Using ini: 

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

[sheson]

See https://dyndolod.info/Messages/INI-Files

[joethemusicman]

Perfect. Thank you!

 

Maybe I missed something, but I think the STEP guide should include that little tidbit.

[sevrick]

  On 1/4/2018 at 11:04 AM, sheson said:

Start the game from the launcher once, so the registry settings are updated with the correct path information.

 

If that is not it, double check the command line parameter. You maybe accidentally adding a switch that can be used to define the path to the INI.

I have a simmilar problem, only mine says this:

[00:00:00.000] TexGen based on xEdit x64 starting session 2018-02-24 10:26:57

[00:00:00.004] Using Skyrim Data Path: C:\Program Files (x86)\Steam\steamapps\common\Skyrim\Data\

[00:00:00.007] Using ini: C:\Users\User Name\Documents\My Games\Skyrim\Skyrim.ini

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

[00:00:09.530] Saving: Settings

[00:00:09.533] Saving: Logs

 

I see the problem but don't know how to fix it. It is taking the path of Oldrim and not Special Edition. I am using MO2. I have also ran the launcher as suggested.

[sheson]

  On 2/24/2018 at 5:38 PM, sevrick said:

I have a simmilar problem, only mine says this:

[00:00:00.000] TexGen based on xEdit x64 starting session 2018-02-24 10:26:57

[00:00:00.004] Using Skyrim Data Path: C:\Program Files (x86)\Steam\steamapps\common\Skyrim\Data\

[00:00:00.007] Using ini: C:\Users\User Name\Documents\My Games\Skyrim\Skyrim.ini

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

[00:00:09.530] Saving: Settings

[00:00:09.533] Saving: Logs

 

I see the problem but don't know how to fix it. It is taking the path of Oldrim and not Special Edition. I am using MO2. I have also ran the launcher as suggested.

DynDOLOD_Manual_SSE.html

 

Installation Skyrim SE

 

..

 

Add -sse as a command line parameter to DynDOLOD.exe/DynDOLODx64.exe or TexGen.exe/TexGenx64.exe to start the tools in Skyrim SE mode. See DynDOLOD-Shortcut.txt for help.

[sevrick]

  On 2/24/2018 at 10:14 PM, sheson said:

DynDOLOD_Manual_SSE.html

 

Installation Skyrim SE

 

..

 

Add -sse as a command line parameter to DynDOLOD.exe/DynDOLODx64.exe or TexGen.exe/TexGenx64.exe to start the tools in Skyrim SE mode. See DynDOLOD-Shortcut.txt for help.

Maybe its just me but it seem unclear. I am left with questions.

 

• 1st When following DynDOLOD-Shortcut.txt to create a shortcut Do I do the same for the TexGenx64.exe. The instructions don't say. They just say create a shortcut from DynDOLODx64.exe.
• 2nd Now that that is done now what? Do I run it right there? Do I go into MO2 and use the shortcut instead of the original?

What I did was followed the instructions and ran it outside of MO2. After running I got an error that said "An error occured while loading modules. Editing is disabled. Check the message log and correct the error." So I check the log at the end it said "Fatal: <EOSError: System Error.  Code: 2. The system cannot find the file specified>"

 

So I figured I would try use it in MO2 again. Same error I started with "Fatal: Could not find ini"

 

All I seem to be left with is create a shortcut and change the end to -sse. To this point I am just guessing what I am supposed to do.

Sorry to be a pain but I don't know what I am doing wrong.

 

*Edit

Ok I just figured out all you need to do is go into MO2 Create an executable for both the DynDOLODx64.exe and the TexGenx64.exe in MO2 then add -sse in the ARGUMENTS space and it works. For anyone out there having the same issue.

Edited February 25, 2018 by sevrick

[sheson]

  On 2/25/2018 at 12:03 AM, sevrick said:

1st When following DynDOLOD-Shortcut.txt to create a shortcut Do I do the same for the TexGenx64.exe. The instructions don't say. They just say create a shortcut from DynDOLODx64.exe.

From DynDOLOD_Manual_SSE.html

 

Installation Skyrim SE

..

Add -sse as a command line parameter to DynDOLOD.exe/DynDOLODx64.exe or TexGen.exe/TexGenx64.exe to start the tools in Skyrim SE mode. See DynDOLOD-Shortcut.txt for help.

 

 

 

From DynDOLOD-Shortcut.txt

 

Add either -tes5 or -see as a command line parameter to DynDOLOD.exe/DynDOLODx64.exe or TexGen.exe/TexGenx64.exe to start the tools in the desired game mode.

 

 

 

  On 2/25/2018 at 12:03 AM, sevrick said:

What I did was followed the instructions and ran it outside of MO2.

There are no instructions that say to run the tools outside of MO2. The instructions are mod manager agnostic as much as possible. DynDOLOD-Shortcut.txt explains how to add command line parameters to the executable dropdown in MO.