AL|EN

@UmeChaI'm on Windows 11 and can't reproduce. Can you do clean installation of Win11 x64 inside Virtual Machine and test SCS there?

@subtledoctor The reason why Quester was able to install component 1203 despite using BG2EE engine and EET is because PI is using is using "--force-install DESIGNATED" and at the same time, PI is unable to parse tp2 file and extract any logic conditions due to complexity of such task. Even the "parsing" part require significant amount of work (GLR parser) so it's not something that I can do in nearest future. Maybe someday there will be tp3 that could solve such problems.

@Quester Can you post weidu-pi-global.log ?

All recent PR's reviewed and merged, thanks for all contributions.

@Luke Well, you should remove submodule from you git mod repo, clone an repo with the required files into some other folder (eg: IELib) and then create 'directory junction' from that repo into you 'modRepo/modFolder/libs/' directory. So every time when you update the lib repo (previously as submodule) you local mod folder will have those updates. You could even have copies of "IELib" repo with different version for different mods. This require some brainpower and remembering what have you done but is doable.

@Luke That's limitation of the submodules. Generalny I would recommend to use "directory junction" if you want to keep some 'libs' folder in sync locally. Then, when you pull or "download master" all those junction directories are normal directories with files.

Typos, typos everywhere ... thanks, I've fixed those 

@JohnBob Hey, please redownload and try again. As for other languages, support for those may be added later. In the meantime, you could provide those:

    <system:String x:Key="BG2EENotDetected">Please put EETLanucher.exe inside BG2EE directory</system:String>
    <system:String x:Key="EETGUIUnknown">Cannot evaluate aviable GUI list from:</system:String>
    <system:String x:Key="EETNotDetected">EET installation not detected</system:String>
    <system:String x:Key="EETRequireFirstRun">Please start EET once to create Baldur.lua</system:String>

along with translated button names.

@JohnBobHey, nice idea, I haven't touch this app for a long time but I was able to do quick update so now if the EEEx is installed, EEEx.exe will be used to launch the game. You can redownload the app from the Download link in the first post but I have to warn you that you will face 'false positive' as this is just a new .exe.

@Nathan82

Hey,

For 3, you can deselect all mod components by clicking 'X' in the bottom-left corner of the main window. Or did you mean to deselect all components of single, selected mod?

As for 1 it's not a bug, it's a feature: the install sequence uses labels so if the 'component numbers' will change inside tp2 it won't destroy the install sequence.

Unfortunately, as you noticed, the sorting order feature is not adjusted to the above change, since it would delay releasing the new version even further.

This is is next thing that I will work but it will take a while.

The System.Object[] thing could definitely happen but it should go away whit upcoming changes.

@Kitanna The eet_modconverter is part of the EET and it only analyze basic EET things. In order to correctly add support for EET you need to follow EET\Docs\Modder's Notes.html.

This is now fixed with 0.10.5.

On 7/21/2022 at 2:54 AM, Guest Advocate said:

@AL|EN Got stuck with similar generic Weidu error on Iwdification as others have posted on the main Project Infinity thread.

This is now fixed with 0.10.5.

Sweet!

@Bartimaeus Well, you do have prehistoric (before 2018) version of the tool, it contains older WeiDU without fixed --change-log function. If you redownload the tool it should work.

BTW: The music in the video is fabulous, care to share the tool that you using in order to record such nice demonstration of the bug reports?

@Axatax Removal of 32-bit binary was made for a reason. If you install many mods, EET_End will fail with 'Out of memory' error and other mods like SCS might not install at all.

@Bartimaeus The output file with changelog is placed inside GameDir\WeiDU-FileChangelog\ folder. If you remember the setup where it didn't provide changelog, I'm happy to investigate.

@subtledoctor The  .gitattributes and .gitignore files are fine, they don't have effect. You have wrong repository structure, it lacks top-level folder. To keep 'convenient setup', make top-level folder and use symlinks for mod data folder into game folder.

@Nurn  I will need your 'install sequence' data and zipped 'Logs' folder in order to check what is going on.

The '[]' bug should be fixed, PI version 0.10.3 is released.

@Morgoth Someday, sure. But it's not an easy task.

@Oloriniel Since version 0.10, PI finds first mod in file system structure then skip and report all duplicates. It seems that the older version was detected first.

Then remove "ProjectInfinity-Labels-Global.txt" file from main app directory.

@Adocate

Importing weidu.log only checks mod checkboxes, it doesn't re-arrange mod at the mod list. You have to do this by yourself or use an alternative solution: after importing weidu.log, you need to copy/export the install sequence, and uncheck all mods using 'X' button at the left-bottom, then import the install sequence again and immediately start the installation.

No, you don't need DLC Merger if you SoD is from BeamDog.