[Razor12911]

Originally Posted by elit

I am having problem with latest R8 version if I scan games directory. Scan can get stuck on some file where progress bar reach the end but never move to another file. CPU core remain loaded but I think it encountered loop. It remain so forever(read hours). Only force quit app process is then solution. Chunk size or threads doesnt seem to help but different individual settings *may* make the app get stuck at different progress. This happen in almost every game that is big(20+gb)(GR Wildlands, Arma 3 LoW as few examples).

However if I scan that particular file where it got stuck it will pass fine. I scan Zlib, LZO and LZ4 only(for ztool). Zlib is probably ok as it alone passed game that got stuck before with +lzo +lz4 selected, those 2 can get stuck even if selected alone. I think one solution is to "tar" the directory and pass it as a single file, will try this later.

If anyone know something regarding this I would greatly appreciate it.

Btw is there an app to scan LZO like ds4zlib and ds4lz4? Something like "ds4lzo"? Those 2 are great and also show coverage percentage and most important have *zero problems*, if there was one for lzo as well I would use it instead.

PS!***THANK YOU RAZOR***!)

Originally Posted by KaktoR

i have the same.

No solution for it until now.

Originally Posted by elit

I tried tarring folder into single file, did not help still get stuck. There was enough free memory so its not memory leaks either. I dont know why it get stuck when same "problematic" individual file pass fine. I dont think it have to do with file itself I think app get into loop stuck.

That said zlib scan works great so its only lzo(and maybe lz4 and/or others), in fact zlib scan is better than ds4zlib including its headerless and force detection option. That one only found few mb's whereas GFS found over gb in latest arma 3.

EDIT: OK maybe I found something. In GR W game LZO kept hanging until I increased chunk size sufficiently. Anything below 256mb hanged but at 256 it consistently passed. Also I recommend 1 thread because even though it did not caused hanging, it still screwed calculation at one point - badly(at least for that game). So for LZ4 & LZO I recommend use 1 thread and start with big enough chunk size, then scale down. I will try it more in later days. Hanging looks like giving you a hint to use bigger chunk size for recompressor.

Zlib is fine at any setting and never hang but I suspect it *maybe* give false positives sometimes. Either that or recompressors are not as advanced yet. I tested on one .forge file from GR W game, scanner showed possibility of unpack by few hundred mb's(with dynamic streams), but I couldnt get it with anything I tried, at any settings. I tried precomp(+intense), ztool(pzlib:ultra, :m3, :x etc...), pzlib3 but no go I got exact same file size.

EDIT2: Also DS4LZ4 give different size for Mirrors Edge Catalyst. GFS find about 7gb(packed) and DS4LZ4 almost 11gb(packed)(and hang at 95%). Both same settings. I dont know which one to believe now.

No longer updating my programs, sorry. DS4LZ4 scans are false, almost all the time.