54 replies to this topic

[skellytz]

Dunno whether it's GB related or a different problem. So if you want to move it to another thread, I don't mind.

Try unbiffing the game (uninstall GB), remove all setup-modname.exe from the game folder (but don't remove or delete anything else!), put weidu.exe v246 in the game folder, rename it to setup-generalized_biffing.exe and biff the game with that. That way we'll know if WeiDU v249 is causing issues again.

[Argent77]

I just want to chime in and point out that the x86-legacy version listed on the WeiDU 249 release page doesn't appear to be affected by the character encoding issue. Updating all your mod installers with that specific version should fix the crashes*.

Place the weidu.exe from the legacy zip archive into the game folder, and put this code into a batch file and run it to save some time:

@echo off
for %%f in (setup-*.exe) do copy /b /y weidu.exe %%f >nul && echo Updated successfully: %%f || echo Failed to update: %%f

* However, mods may still corrupt game data (with both 249-legacy or 246 WeiDU) if their tp2 scripts are encoded in utf-8 and contain verbatim instances of the filenames with special symbols.

 

Edit: For convenience I have attached a zip file with the batch file and legacy weidu.exe. Simply unpack it into the game folder and run "update-weidu.bat".

Attached Files

•  update-weidu.zip   1.02MB   65 downloads

[Azaghal]

Thanks for your advice, skellytz and Argent.

Will try both ways, but must admit to my utter shame that I don't know how to

 

put this code into a batch file and run it to save some time:

If you would try to explain for someone who has never wrote a batch file?

 

Thanks again.

 

Azghal

[Argent77]

Thanks for your advice, skellytz and Argent.

Will try both ways, but must admit to my utter shame that I don't know how to

 

put this code into a batch file and run it to save some time:

If you would try to explain for someone who has never wrote a batch file?

 

Thanks again.

 

Azghal

I have updated my previous post and attached a zip with the necessary files.

[Azaghal]

Well, I tried skellytz' proposal first, uninstalled GB (received a handful of warnings) and reinstalled it with WeiDU v246. Improved stability a lot. I'm further in the game now than before and experienced only one unspecific CTD so far. So I will stick to this solution unless number of problems rises.

 

Have a nice weekend and thank you!

 

Azaghal

[skellytz]

Split the related issues from Generalized Biffing thread into a new topic in Mega Mod Help forum: Crashes in mega-mod games installed with WeiDU 247, 248 and 249

 

The crashes aren't caused directly by Generalized Biffing, but by a bug in WeiDU installer versions 247, 248 and 249.

[Salk]

Should the WeiDU bug perhaps be reported at Pocketplane?

[jastey]

Should the WeiDU bug perhaps be reported at Pocketplane?

+1

And could this until it is fixed be put into a short note or howto - I have to admit I don't get whether this is a principle thing that should be communicated community wide or some special case for IA / GB.

[Argent77]

It's already known (topic).

Apparently this is due to a "recent" change in the Ocaml compiler used to create the WeiDU binaries, so I wouldn't expect a solution soon. The Windows x86-legacy isn't affected by this issue (yet), since it was compiled with an older compiler version.

[ALIEN]

Just FYI, the x86 cannot be used to install EET not SCS.

[skellytz]

To make a long story short: OCaml (the programming language behind WeiDU) deprecated functions operating on the Latin-1 (8859-1) character set and now uses only US-ASCII characters. Simple system actions, eg making WeiDU copy files with the filenames containing Latin-1 characters, or using translated dialogue strings in TRA files shouldn't cause issues on their own. But the setup functions that internally manipulate the unsupported characters or use them as identifiers won't work correctly. This applies to any mod (not only Generalized Biffing) which somehow processes non-ASCII characters during setup.

[Salk]

Got it.

 

I wonder now how many mods are affected but I guess it won't be just 2 or 3...

[jastey]

Because I'm super slow: does this also apply to IA?

[Argent77]

Because I'm super slow: does this also apply to IA?

Not directly (afaik). Only mods referencing IA resources in their scripts or IA resources handled by specific WeiDU actions may trigger this issue (such as Generalized Biffing). The issue should be solved if IA can get rid of their special non-ascii symbols in filenames. In general, mods should be safe if they restrict filenames and literal strings inside their code to the US-ASCII character set.

[jastey]

Thanks!