![]() |
Error while unpacking
Hello! Can you give me some advice on where to look? Here’s the situation: I’m making a repack for Assassin’s Creed Shadows, and there’s a file called DataPC_Japan_ext.forge that’s 26 GB. Basically, errors pop up with large files—meaning when I run it on its own, everything’s fine, but when I run the whole 135 GB bundle, it always complains that this file is corrupted. I'm using xtool:mermaid+srep+lolz. I have 32 GB of RAM. What I’ve tried: I added RAM up to 48 GB, but it didn’t help; I reset all overclocks, but that didn’t help either. In Lolz, I set it to 2, 4, and 8 threads, but nothing changed—so it’s not a RAM issue. If I split the 135 GB into 3 files, it’s fine; but if I put them all together, I get an error during extraction saying the file is corrupted.
|
Most probably sreps fault. Try other versions or settings.
|
Quote:
|
Increase minimum match length to 1024 or 2048.
|
Could it be that there is some kind of bug where if the compressed block size is too large, all SREP versions will fail because of this? In principle, not v3.2, but is it possible? Maybe trash all "cls-srep.exe" and use the native "SREP.exe" file for unpacking.
Code:
[External compressor:srep] |
^^
The -s switch is to allow greater input volume for stdin/stdout usage. Requires a lot of ram. |
Increase minimum match length to 1024 or 2048.
it didn't help ((( |
Reduced SREP decompression memory from "cls.ini" file, not solved the problem? (old my post here.)
Or use this single and full "srep(64).exe" file, cls-files (dll and EXE's) will be deleted in parent folder? |
When I set less memory, the srep and xtool processes close immediately.
If you unpack it using Arc.exe and srep.exe, everything is fine. But if you use a script, unarc.dll, and cls-srep_x64.exe, then nothing. |
| All times are GMT -7. The time now is 02:21. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com