woot!

My thanks in advance (again), regardless of outcome

Added XML pretty printing and batch conversion in v1.4.

A lot more usable with readable files and batch conversion, yay! And only one Convert button instead of save/loading LSBs. Great work Norbyte.

And I noticed you can unpack story files now? That's probably not very useful without the ability to recompile the story, though, right? Gotta wait for the editor to really start scripting?

Thats a WIP feature, I'm hoping to add some additional stuff (like compilation) later.

Just to clarify, the Pak extractor only extracts SOME files? I just don't understand where a lot of stuff is stored (e.g., talent effects), and I assume they must be in some files that your extractor just doesn't touch because they're Larian-specific files or something that we just can't open?

No, it extracts everything.
Talent effects are hardcoded in EoCApp.exe.

Norton really does not like this program at all.

edit: you need to add an exception to your sonar etc for the whole folder to get it to work.

Norton has no issue with this.
Got a 22.5.5.15 NIS (bought and paid for) and have never had any trouble. Are your sonar settings perhaps at an overly high level?

Which by the way, you do not need. Sonar 'on', all its subcategories to 'off' is good enough

Hi i am having trouble with the LSF files from the MainLSF.pak. When i try to convert them (eg properties.lsf) to the LSX Format i get this error.



Converting existing lsx to lsf and back works fine. Do they use a new serialization or am i doing something wrong?

Had the same issue here.

I'll investigate and add support for the new LSF format asap

Someone give him a medal

I've added support for v2 LSF files.
I haven't worked out all the details yet, so some files may fail to load unfortunately.

Thank you for the umpteenth time Norbyte, much obliged!

Thanks for the first time, its working great.

I'm getting this when trying to convert the globals.lsf to a lsx file
http://imgur.com/zd4Ygmn

I'm using the latest GoG version.

I am getting the same error on my globals.lsf System.OutOfMemoryException: Array dimensions exceeded supported range.

Here is a link to the file https://www.dropbox.com/s/012kzqs8e5dp7rk/globals.lsf?dl=0

Yeah, this is a known issue at the moment with larger LSF files, sadly
I'm trying to find out why these files decompress incorrectly, but haven't found the root cause yet.

I believe I know what the problem could be. Would you be willing to post the source code here so I could take a look at it? It's written in C# or VB right? The problem I think is that the maximum amount of items in an array is limited by the maximum integer size. I think since the files are so large the maximum integer limit is being reached.

If you would be willing to post the source code I would be extremely grateful!

Here it is:
https://github.com/Norbyte/lslib/tree/master/LSLib

The prolematic part starts here:
https://github.com/Norbyte/lslib/blob/master/LSLib/LS/LSFReader.cs#L483

The problem is that the LSFv2 format introduced chunked compression, where the LZ4 stream is split into multiple parts. However, simply putting the chunks together corrupts the output stream subtly, ie. some output bytes become consistently different while most of the others stay the same. Because of this, streams over 0x8000 bytes (that are chunked) will probably decompress incorrectly. This is what causes the out of memory error (array sizes becoming impossibly large as the decompressed length values are corrupted).
I don't really know why it could be, but I'll experiment with it a bit when I have some time.