EET - error on launch after re-installation

[Guest Fox Cunning]

Hello!
I have just reinstalled BG:EE + BG2:EE, followed by EET, but as soon as I launch it, I get an error saying simply "There was an error. A crash report have been saved to..." (it does create a memory dump file in my Documents folder).

I'm quite sure I have used the same installation procedure as when I installed last year, and it worked perfectly that time.

1. Installed both BG:EE and BG2:EE (Steam version, all DLCs).
2. Ran both once to make sure they work — no problem so far.
3. Ran modmerge.exe in the BG:EE folder. It finds SoD and does its thing.
4. Same in the BG2:EE folder.
5. Ran oalinstall.exe.
6. Extracted EET in the BG2:EE folder.
7. Ran setup-EET.exe. Completes without errors.
8. Ran setup-EET_end.exe. Again no errors so far.
9. Launched the game: crashes.

The WeiDU.log file only says:

// Log of Currently Installed WeiDU Mods
// The top of the file is the 'oldest' mod
// ~TP2_File~ #language_number #component_number // [Subcomponent Name -> ] Component Name [ : Version]
~EET/EET.TP2~ #0 #0 // EET core (resource importation): V13.4
~EET_END/EET_END.TP2~ #0 #0 // EET end (last mod in install order) -> Standard installation

Any help would be greatly appreciated.
 

[jastey]

4 hours ago, Guest Fox Cunning said:

Ran oalinstall.exe.

What is oalinstall.exe?

[Fox Cunning]

OpenAL, it's an audio library.

Mind you, I tried again and it doesn't matter whether I install that or not. 

[Trouveur80]

8 hours ago, Guest Fox Cunning said:

1. Ran modmerge.exe in the BG:EE folder. It finds SoD and does its thing.
2. Same in the BG2:EE folder.

What do you mean by 4 ? DLC Merger or Modmerge should only be used on BGEE, not BG2EE.

[Fox Cunning]

23 minutes ago, Trouveur80 said:

What do you mean by 4 ? DLC Merger or Modmerge should only be used on BGEE, not BG2EE.

Ah, I guess that was a mistake. Thanks for the heads-up.

Didn't seem to do anything when I ran it in the BG2:EE folder, but I'll try once again skipping that step just in case.

[jastey]

@Fox Cunning Rcommendation is to use DLC Merger instead of modmerge.

Also, after already "modmerging" a game if you want to change the mod setup etc, start from scratch by deleting the folder and download / copy over a clean game folder, because there could be remnants due to the modmerging process ( thi is also valid for DLC Merger).

[Fox Cunning]

9 minutes ago, jastey said:

@Fox Cunning Rcommendation is to use DLC Merger instead of modmerge.

Also, after already "modmerging" a game if you want to change the mod setup etc, start from scratch by deleting the folder and download / copy over a clean game folder, because there could be remnants due to the modmerging process ( thi is also valid for DLC Merger).

Thanks, I didn't know of DLC Merger. Will definitely use that next time.

 

55 minutes ago, Fox Cunning said:

Ah, I guess that was a mistake. Thanks for the heads-up.

Didn't seem to do anything when I ran it in the BG2:EE folder, but I'll try once again skipping that step just in case.

Well, would you look at that? This was actually the problem!
And all because I had found the executable in my BG2:EE folder, so I just assumed I had ran it there too when I installed it the last time.

Thanks, @Trouveur80 

[Trouveur80]

Glad it is solved, happy game time !