XTool 2020 (Main Project)

[IgorKolesnik]

Originally Posted by Razor12911

Thanks for the tests, 95% complete. the new release will first ship with 1 codec (zlib) just to see if everything works as expected

can update game file scaner? thank

[Razor12911]

Originally Posted by IgorKolesnik

can update game file scaner? thank

and add what feature?

@everyone

here's a benchmark

some file from Pro Evolution Soccer

old xtool = 275MB >> 381MB took 11.63 seconds using 4 threads
new xtool = 275MB >> 381MB took 06.09 seconds using 4 threads

same memory usage and I/O

note: I only reworked the encoder to use the cpu effectively so you should expect roughly x1.25-2 more speed from old version while using same resources and this applies to all codecs reflate, oodle and etc

[KaktoR]

Originally Posted by Razor12911

and add what feature?

Just fix the hang bug

Originally Posted by Razor12911

@everyone

here's a benchmark

some file from Pro Evolution Soccer

old xtool = 275MB >> 381MB took 11.63 seconds using 4 threads
new xtool = 275MB >> 381MB took 06.09 seconds using 4 threads

same memory usage and I/O

note: I only reworked the encoder to use the cpu effectively so you should expect roughly x1.25-2 more speed from old version while using same resources and this applies to all codecs reflate, oodle and etc

This is great.

[Razor12911]

Originally Posted by Simorq

Hi Razor12911

v: skip verification

This option works for oodle, crilayla, lzo.
Please do not delete this option in the new version.

The option will be there

Originally Posted by dixen

oodle detect, for example

I remember including an oodle scanner, but fine I'll think of something for the scanner.

Originally Posted by KaktoR

This is great.

how about this?

There will be a new feature in xtool called history data, what it does is simply store processed stream information and be able to recall it at the later stage.

If you are wondering how this helps, well there are certain games made by lazy developers who repeat game resources instead of just reusing them, resulting in bigger game size for no absolute reason, apart from that, if they are compressed streams it means that xtool will have to process the same stream over and over again, storing history data allows it to prevent the same stream from being reprocessed instead, it will just look at the history and find out how the previous copy was processed then automatically assume it's the same stream and then apply the same settings, resulting in more speed.

I ran a test on a file I repeated on purpose and these were the results.

old xtool took 196.671 seconds and used 335MB ram
new xtool took 154.174 seconds and used 319MB ram
new xtool with history feature took 72.223 seconds and used 439MB ram

the cost of the feature depends on how much history you want to be stored but with default settings, it should use an additonal 192mb ram usage than without, you can always disable it or order it to store more history, depends on how much memory you have to spare.

Note:
In a practical situation, you can shave off a few seconds but then again, depends on the input

[dixen]

Originally Posted by Razor12911

and add what feature?

oodle detect, for example