Jump to content

Confused about BiG World Fixpack


Recommended Posts

Recommendation would be to skip installing Almateria's mod for now, given the author indicating most recent version seems to have 'broken something', until the mod is supported/fixed at some point.

 

Or substitute version 8.2.7 for 8.2.8... Or if you're feeling up to it, here's a temporary fix from the mod author:

 

http://www.shsforums.net/topic/59291-almaterias-restoration-proyect-error/

 

8.2.7 can be found here:

 

http://www.shsforums.net/files/file/1053-almaterias-restoration-project/

 

I think the safest bet is to replace 8.2.8 with 8.2.7 and patch with BWS/Big World Fixpack.

 

[edit] It looks like she may have fixed it after all.

 

http://www.shsforums.net/topic/56026-almaterias-restoration-project/page-22

Link to comment

Recommendation would be to skip installing Almateria's mod for now, given the author indicating most recent version seems to have 'broken something', until the mod is supported/fixed at some point.

 

Or substitute version 8.2.7 for 8.2.8... Or if you're feeling up to it, here's a temporary fix from the mod author:

 

http://www.shsforums.net/topic/59291-almaterias-restoration-proyect-error/

 

8.2.7 can be found here:

 

http://www.shsforums.net/files/file/1053-almaterias-restoration-project/

 

I think the safest bet is to replace 8.2.8 with 8.2.7 and patch with BWS/Big World Fixpack.

 

[edit] It looks like she may have fixed it after all.

 

http://www.shsforums.net/topic/56026-almaterias-restoration-project/page-22

 

Thanks for all the links, but the general question remains: what to do if the version of the mod is higher than the one BWS wants to patch and you do not know whether that new version includes all changes? Would it be better to apply patch or skip it?

Link to comment

Apply. If mod won't install then, reinstall without applying patch.

And tell us about the mod in question.

Sometimes it may just be EET compatibility being achieved and the patch can be removed.

Sometimes things are more difficult, when there is a mix of bug fixes and compatibilty. Some modders upgrade their mods but keep their bugs.

Link to comment

 

Apply. If mod won't install then, reinstall without applying patch.

And tell us about the mod in question.

Sometimes it may just be EET compatibility being achieved and the patch can be removed.

Sometimes things are more difficult, when there is a mix of bug fixes and compatibilty. Some modders upgrade their mods but keep their bugs.

 

 

3 mods had hiccups - Banterpack (probably because Setup-banterpack.tp2 is inside banterpack folder, not in the main directory), imoenfriendship and yoshimo - because "'VERSION ~2.1~' instead of expected 'VERSION ~2.1_Isaya". Patched them anyway.

_ApplyPatches.debug

Link to comment

 

 

Apply. If mod won't install then, reinstall without applying patch.

And tell us about the mod in question.

Sometimes it may just be EET compatibility being achieved and the patch can be removed.

Sometimes things are more difficult, when there is a mix of bug fixes and compatibilty. Some modders upgrade their mods but keep their bugs.

 

 

3 mods had hiccups - Banterpack (probably because Setup-banterpack.tp2 is inside banterpack folder, not in the main directory), imoenfriendship and yoshimo - because "'VERSION ~2.1~' instead of expected 'VERSION ~2.1_Isaya". Patched them anyway.

 

Agree with the first one - tp2 not inside mod folder, why do we still have this in 2017? ???

 

The other two are fixed now.

Link to comment

Now, that Solaufein/Kelsy conflict. Looks like it is Solaufein mod problem. For BG2EE mods are supposed to be installed in order Sola-Kelsy. If I do it in EET Kelsy refuses to install with that ERROR message:

 

 

 

Copying 1 file ...

.....

EET_NPC_TRANSITION patching for J#Kelsey: BG2 NPC without BG1 content

Patching J#KLSY25.BCS
Extending game scripts ...

Patching J#KLSY.BCS
Extending game scripts ...
Extending game scripts ...
Copying and patching 1 file ...

FATESP.DLG already has J#Kelsey references. Patching not needed.
Copying and patching 1 file ...
ERROR: cannot resolve trigger 0x40df
ERROR: [AR4000.BCS] -> [override] 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 [Kelsey], rolling back to previous state
Will uninstall 802 files for [KELSEY.TP2] component 0.
Uninstalled 802 files for [KELSEY.TP2] component 0.
ERROR: Not_found
PLEASE email the file SETUP-KELSEY.DEBUG to jcompton@pocketplane.net
Using Language [English]

 

 

 

When I uninstalled Solaufein - Kelsy installed without problem (debug files for problematic installation attached).

 

Solaufein mod was treated with EET-Convertor (options 2 and 3).

 

The question is - would it be safe to install that problematic Solaufein mod later in the file chain, or better avoid?

 

SETUP-KELSEY.DEBUG

SETUP-SOLAUFEIN.DEBUG

Link to comment

All 3 installed just fine nevertheless. Both "not _Isaya" files were downloaded anew from the links in the Mod Compatibility List. Next time (I suspect it will be another time anyway) I'll make sure to take files form BWS download folder.

Now we have confusion.

 

All you did in the three cases was correct.

 

I have removed the _Isaya from the two mods in fixpack and corrected the reference in BWS.

For banterpack you need to do it manually if you do a manual install. In BWS the tp2 should now be moved into the folder before patching is applied.

 

And thank you for providing this detail, this really helps to fix things.

Link to comment

Now, that Solaufein/Kelsy conflict. Looks like it is Solaufein mod problem. For BG2EE mods are supposed to be installed in order Sola-Kelsy. If I do it in EET Kelsy refuses to install with that ERROR message:

 

 

 

Copying 1 file ...

.....

 

EET_NPC_TRANSITION patching for J#Kelsey: BG2 NPC without BG1 content

 

Patching J#KLSY25.BCS

Extending game scripts ...

 

Patching J#KLSY.BCS

Extending game scripts ...

Extending game scripts ...

Copying and patching 1 file ...

 

FATESP.DLG already has J#Kelsey references. Patching not needed.

Copying and patching 1 file ...

ERROR: cannot resolve trigger 0x40df

ERROR: [AR4000.BCS] -> [override] 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 [Kelsey], rolling back to previous state

Will uninstall 802 files for [KELSEY.TP2] component 0.

Uninstalled 802 files for [KELSEY.TP2] component 0.

ERROR: Not_found

PLEASE email the file SETUP-KELSEY.DEBUG to jcompton@pocketplane.net

Using Language [English]

 

 

 

When I uninstalled Solaufein - Kelsy installed without problem (debug files for problematic installation attached).

 

Solaufein mod was treated with EET-Convertor (options 2 and 3).

 

The question is - would it be safe to install that problematic Solaufein mod later in the file chain, or better avoid?

 

It looks to me that Kelsey fails at the point where the Kelsey Solaufein interactions are supposed to be compiled. What comes out of your conversion and what Kelsey crossmod expects may not match.

Link to comment

 

Now, that Solaufein/Kelsy conflict. Looks like it is Solaufein mod problem. For BG2EE mods are supposed to be installed in order Sola-Kelsy. If I do it in EET Kelsy refuses to install with that ERROR message:

 

 

 

Copying 1 file ...

.....

 

EET_NPC_TRANSITION patching for J#Kelsey: BG2 NPC without BG1 content

 

Patching J#KLSY25.BCS

Extending game scripts ...

 

Patching J#KLSY.BCS

Extending game scripts ...

Extending game scripts ...

Copying and patching 1 file ...

 

FATESP.DLG already has J#Kelsey references. Patching not needed.

Copying and patching 1 file ...

ERROR: cannot resolve trigger 0x40df

ERROR: [AR4000.BCS] -> [override] 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 [Kelsey], rolling back to previous state

Will uninstall 802 files for [KELSEY.TP2] component 0.

Uninstalled 802 files for [KELSEY.TP2] component 0.

ERROR: Not_found

PLEASE email the file SETUP-KELSEY.DEBUG to jcompton@pocketplane.net

Using Language [English]

 

 

 

When I uninstalled Solaufein - Kelsy installed without problem (debug files for problematic installation attached).

 

Solaufein mod was treated with EET-Convertor (options 2 and 3).

 

The question is - would it be safe to install that problematic Solaufein mod later in the file chain, or better avoid?

 

It looks to me that Kelsey fails at the point where the Kelsey Solaufein interactions are supposed to be compiled. What comes out of your conversion and what Kelsey crossmod expects may not match.

 

 

Thanks for your incredible patience in answering countless stupid questions!

 

Solaufein installs just fine after Kelsy. Is it possible to predict the outcome if I leave both mods installed? Would that one (and only one) conversation broken and the rest of dialogs ok (in other mods affecting dialog.tlk too)?

 

Anyway, thanks again, at least problem is identified.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...