Oodle precompressor (Side project)

[Toximan69]

I don't no, but I'll tried to pack game0.arc 846 MB, like L0v3craft

using oo2reck+oo2recs on the file game0.arc from Just Cause 4:
========================================
FreeArc 0.67 (March 15 2014) creating archive: data.arc
Compressed 1 file, 887,443,456 => 955,165,272 bytes. Ratio 107.63%
Compression time: cpu 1.00 sec/real 41.61 sec = 2%. Speed 21.33 mB/s
All OK

It turns out only 846=>910 MB
My PC:
Core i7-4720HQ 2.6 GHz, 16 GB RAM, Windows 10. P.S. On Windows 7 same 846=>910 MB

I don't understand how L0v3craft did 2.33GB

[felice2011]

Good job Zee, you should enter some options for the choice of CPU threads for different hardware systems.

[L0v3craft]

Originally Posted by Toximan69

I don't no, but I'll tried to pack game0.arc 846 MB, like L0v3craft

using oo2reck+oo2recs on the file game0.arc from Just Cause 4:
========================================
FreeArc 0.67 (March 15 2014) creating archive: data.arc
Compressed 1 file, 887,443,456 => 955,165,272 bytes. Ratio 107.63%
Compression time: cpu 1.00 sec/real 41.61 sec = 2%. Speed 21.33 mB/s
All OK

It turns out only 846=>910 MB
My PC:
Core i7-4720HQ 2.6 GHz, 16 GB RAM, Windows 10. P.S. On Windows 7 same 846=>910 MB

I don't understand how L0v3craft did 2.33GB

Same thing here on windows server 2016. If i run the tools on my old pc with windows 10 looks like the tools from razor are able to detect many more streams in the files, that is strange. Ok maybe it is not a problem of O.S. version but it is dependant from another thing, i don't know.

[doofoo24]

testing on AC Odyssey forge files 43.3gb inflate to 78730mb > srep+lolz 20gb
seems to me others that used afr get better result.
i need test with afr to be sure...
cpu usage like zig zag it took around 43min on I7 8700K at 4.7gb...

[Razor12911]

Update available

Changes

- Fixed compatibility issues... hopefully, give big thanks to ShivShubh and FitGirl for helping and community for tests

[doofoo24]

also work on monster world hunter inflate from 19.9gb to 34.4gb but i got blue sreen in the middle of lolz
my ssd nvme evo die after 378tbw

[FitGirl]

Originally Posted by doofoo24

my ssd nvme evo die after 378tbw

That's why you should never make your repacks on SSDs.

[PsYcHo_RaGE]

Originally Posted by FitGirl

That's why you should never make your repacks on SSDs.

what do you recommend then, i know ssd's are bit fast when we use em to compress files but same "Dead"!

[FitGirl]

Always use HDDs for that, they have no write limits. In example, 378 TB of writes I exceed in a couple of weeks. Imagine I'd done it on SSD. SSDs are for OS or for rare read files. Never use them for frequent writes.

[PsYcHo_RaGE]

Originally Posted by FitGirl

Always use HDDs for that, they have no write limits. In example, 378 TB of writes I exceen in a couple of weeks. Imagine I'd done it on SSD. SSDs are for OS or for rare read files. Never use them for frequent writes.

so basically, SSD's don't support frequent writing of the data.....
now my question is what should be the recommended speed of an HDD....i mean they differ in range of speeds and quality....that matters a bit

[KaktoR]

7200 rpm obviously

[PsYcHo_RaGE]

Originally Posted by KaktoR

7200 rpm obviously

hmmm, well yeah.....what about the cpu's? i have seen and tested on many of em but still some suggestions?

[KaktoR]

The more threads the better.

[L0v3craft]

Originally Posted by Razor12911

Update available

Changes

- Fixed compatibility issues... hopefully, give big thanks to ShivShubh and FitGirl for helping and community for tests

I can confirm now everything works on windows server 2016 too

Thank you Razor !

[danswano]

Thanks Razor for the amazing effort and the tools you provide us for free.

I have a question
Is there a general list of games that uses oodle compression?