feature request - skip bin file generation for pre-existing bin files

[retrosapien]

So, here is my idea.
What happens if you use the same wad2bin command twice? I think it rewrites all files. Or at least changes mod times.
Which is fine for a small wads. But wasteful on large wads.
Can you make it detect that the file is already written, and skip?

RS

[DarkMatterCore]

Hi there.

It could be added as an opt-in option (e.g. enabled through an additional argument) instead of setting it as the default behavior. The reason being that generated content data between different wad2bin runs could also use keydata from different consoles, even if unlikely.

The existence of multiple WADs with matching title IDs but different content data also represents a problem, which is why rewriting pre-existent files is just the easy way to go -- unless you're an advanced user and know what you're doing.

tl;dr: yes, it can be implemented as an additional argument (e.g. --skip-bins or something like that).

[DarkMatterCore]

@retrosapien I started working on this earlier today after finally getting some free time. If possible, please hit me up on Discord -- I'd like to test this before pushing any changes. Thanks.

[retrosapien]

hey,
thanks for the interest!
I don't have discord, but i would be happy to share my results here, if you'd like.

[DarkMatterCore]

wad2bin.zip

@retrosapien Please give it a try. The updated usage message should reflect the newly introduced changes:

wad2bin v0.9 (c) DarkMatterCore.
Built on: 2025-02-17 17:53:42 UTC.

Usage: wad2bin <keys.txt> <device.cert> <input WAD> <output dir> [--skip-bins] [<parent title ID> [--nullkey]]

Paths must not exceed 259 characters. Relative paths are supported.
The required directory tree for the *.bin file(s) will be created at the output directory.
You can set your SD card root directory as the output directory.

If "--skip-bins" is provided, *.bin file generation will be skipped if a corresponding *.bin file already
exists at the output path.

Notes about DLC support:

* Parent title ID is only required if the input WAD is a DLC. A 16 character long hex string is expected.
* If "--nullkey" is set after the parent title ID, a null key will be used to encrypt DLC content data.
  Some older games (like Rock Band 2) depend on this to properly load DLC data when launched via the Disc Channel.

For more information, please visit: https://github.com/DarkMatterCore/wad2bin.

Let me know how it goes.

[retrosapien]

dang!
guess i didn't mention on this issue, I'm using Debian (x86), not windows. I compiled myself.
can you upload the changed source files?

[DarkMatterCore]

Sure. Check the skip_bins branch.

[Sad0wner]

It create a new bogus wad for each wad thah didnt touch, Is it necesary?

[Sad0wner]

and for the WGSC wads i don´t need to install the bogus wad

[DarkMatterCore]

It create a new bogus wad for each wad thah didnt touch, Is it necesary?

It's alright. A single bogus WAD is generated per each input WAD. DLC WADs may end up yielding several <index>.bin files, though, which may severely decrease wad2bin's performance due to additional I/O overhead -- this is what the new option aims to prevent, but it can only work properly if that's what the user actually intends to do.

and for the WGSC wads i don´t need to install the bogus wad

You still need to install them if you haven't previously done so.