EET v13.4 released

[maus]

Installation Bug:  (edit: well, my fault obviously...)

Including SOA compatibility patches
Appending to files ...
[EET/tbl/map_eet_areas.tbl] loaded, 10942 bytes
EET/tbl/map_eet_areas.tbl copied to EET/backup/0/map_eet_areas.tbl, 10942 bytes
Appended text to [EET/tbl/map_eet_areas.tbl]
[EET/temp/WeiDU.log] loaded, 1502 bytes
ERROR: cannot convert %col2% or %%col2%% to an integer
ERROR: [EET/tbl/compatibility.tbl] -> [EET/tbl/compatibility.tbl] Patching Failed (COPY) (Failure("Int32.of_string"))
Stopping installation because of error.
Stopping installation because of error.

Debug can't be attached due to size limit. 

Another interessting thing after the installation stopped:

ERROR Installing [EET core (resource importation)], rolling back to previous state
Unable to Unlink [EET/backup/0/OTHER.0]: Unix.Unix_error(1, "unlink", "EET/backup/0/OTHER.0")
WARNING: Cannot uninstall STRING_SET #270672, out of range 0 -- 103584
WARNING: Cannot uninstall STRING_SET #270671, out of range 0 -- 103584

(and many more warnings of the same type)

I used 13.4 on 2.6.6. But I used WeiDU 2.47 and not the one provided with the EET. Maybe that is the reason for the problem. I'll check for that. But anyhow I guess the error is interessting by itself as it happened for the SoA compatibility part... 

edit: used the provided setup-EET.exe which says it is a 2.47 too but has a smaller size. same problem, no changes.

next edit: was my fault: I modified the compatibility.tbl but in a wrong way (missed a "0"):

WALAHNAN 0           //Walahnan NPC
BRISTLELICK            //Bristlelick NPC

Edited August 15, 2021 by maus
update

[maus]

Error message when using EET_end (2.6.6 and 13.4)

ERROR: [PDIALOG.2da] -> [override/PDIALOG.2da] Patching Failed (COPY) (Failure("ERROR: READ_2DA_ENTRY_FORMER failed on variable %pdialog_45_5%"))
Stopping installation because of error.
ERROR: [CAMPAIGN.2DA] -> [.../CAMPAIGN.2DA] Patching Failed (COPY) (Failure("ERROR: READ_2DA_ENTRY_FORMER failed on variable %pdialog_45_5%"))
Stopping installation because of error.

ERROR Installing [EET end (last mod in install order) -> Standard installation], rolling back to previous state
Will uninstall   1 files for [EET_END/EET_END.TP2] component 0.
Uninstalled      1 files for [EET_END/EET_END.TP2] component 0.
ERROR: Failure("ERROR: READ_2DA_ENTRY_FORMER failed on variable %pdialog_45_5%")
PLEASE email the file SETUP-EET_END.DEBUG to K4thos (swit)
Using Language [English]

 

For a second try the error messages are:

Preparing ALORAJ.dlg source file (38 states starting from 0)
Copying and patching 1 file ...
ERROR: cannot convert num_states_MINSCJ or %num_states_MINSCJ% to an integer
ERROR: [MINSCJ_.dlg] -> [EET/temp/append/dlg/MINSCJ_.d] Patching Failed (COPY) (Not_found)
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.

ERROR Installing [EET end (last mod in install order) -> Standard installation], rolling back to previous state
Will uninstall   9 files for [EET_END/EET_END.TP2] component 0.
Uninstalled      9 files for [EET_END/EET_END.TP2] component 0.
ERROR: Not_found
PLEASE email the file SETUP-EET_END.DEBUG to K4thos (swit)
Using Language [English]

This is strange. Third run without changing anything passed with SUCCESSFUL, no Warnings.

 

[maus]

For the installation mentioned above: that was crap, Kits totally destroyed and very strange. 

For the next try I got the same first error message about the pdialog.2DA (attached). I eliminated all entries from BG1 Mods which are only providing a DV but no dialog-files (glam and thalan). That helped to avoid this first error message which was reproducable in the second installation. 

PDIALOG.2DA

[Graion Dilach]

Could you share a mod list and installation order instead of randomly throwing errors on obviously custom-edited files? Why do you need to edit the compatibility list? What are you actually trying to do?

Edited August 18, 2021 by Graion Dilach

[maus]

Well, the idea is to make an EET installation. In detail: I have been doing several of EET installations (more than 20, about 10 successful). This time I'm trying to make 2.6.x version for the first time (and with WeiDU 2.47). In the end it is trying to check what works and whar does not. For example: with former installations sometimes I had problems when I was using GlamPack (which has not been updated since), sometimes not. A full stop like this time was somehow new. So in the end the mod is not really compatible with EET while adding DVs without dialogfile in the pdialog.2DA 

To edit the compatibility list is necessary if you install Mods in BG1 not listed yet, otherwise EET won't start... 

WeiDU logs for the first attempt are attached below. 

The second installation crashed during a reinstall of EET_End. But that was due to hardware issues. The mods have been more or less the same (HTaM 3.4 instead of 3.3 and small changes in the order of installation). 

WeiDU.txt WeiDU-BGEE.txt

[Graion Dilach]

Oh, I completely overlooked Lava's new NPCs lacking EET compatibility (and yet I looked at them when I started campaigning for mod NPCs having correct voicesets in BGEE). I'm not sure what his plans are regarding that - this wasn't brought up in Walahnan's topic s atleast. I'd skip those myself for now. I've never played with Glam's NPCs myself.

Edited August 19, 2021 by Graion Dilach

[jastey]

6 hours ago, Graion Dilach said:

I'm not sure what his plans are regarding that

As far as I know, @Lava will make his mods EET compatible when they are done and tested, just not while they are still in development.

[Cahir]

10 minutes ago, jastey said:

As far as I know, @Lava will make his mods EET compatible when they are done and tested, just not while they are still in development.

Yeah, and this does also include traification. I can imagine, with all the mods he created during these years, reaching to each of the translators to update translation every time he adds/changes something would be a pain. Besides, some translators can be already unavailable by now.

[Lava]

I will be looking for someone to help with making some of my mods available for EET, but Walahnan is not on that list just yet. I'm not even sure if more than 3-4 people played the mod from OC to the end of SoD.

I think it would be ok to have Verr BG1, White and Bristle to get newest EET compatibility, but as I do not use EET myself, that would need to be handled by someone familiar with such matters, but as always - always send me PM first: I can tell you which are in my opinion ready and are not getting any major content-oriented updates. I know it requires delicate work and people that help always get included in the readme.

[guyudennis]

On 6/29/2021 at 5:35 AM, grodrigues said:

The install of EET_end does not fail, but it spits this at the end:

chmod: cannot access './EET/bin/unix/weidu': No such file or directory
/bin/sh: line 1: ./eet/bin/unix/weidu: No such file or directory

This is on linux. The error is that the weidu executable is located in the subdir x86_64; have to alter lines 701 and 702 of EET_end.tp2 to point to the correct location (or move the weidu executable).

Ran into the same issue on Linux.

Looking at the code, MacOS should have the same problem.

[Guest fakename]

In linux you shouldn't use a full path to executable files imo, since that's the purpose of the $PATH variable. Oh well.

[Zorutar]

Hello, I'm getting this error during EET installation (see complete log). Where could be a problem? Thank you for feedback and tips.

Copying and patching 1 file ...
Copying and patching 1 file ...
Creating 1 directory
Problem Unix.Unix_error(1, "mkdir", "C:") on C:: util.ml
Copying and patching 1 file ...
Copying and patching 1 file ...
Copying and patching 1 file ...

ProjectInfinity-WeiDU-Debug-EET-0.zip

[jastey]

@Zorutar looks like a permission problem on your computer. Do not mod the original game folder in C:Programs. Copy the game folder elsewhere and mod the copy.

[Zorutar]

13 hours ago, jastey said:

@Zorutar looks like a permission problem on your computer. Do not mod the original game folder in C:Programs. Copy the game folder elsewhere and mod the copy.

Fixed after reading this article and specifically Argent77 post. I installed game and mods to same drive (C:) and error in log disappeared.

Edited March 6 by Zorutar