Dragon Ball FighterZ (DVD9 to DVD5/6xCD)

[Scarlet Blade]

Dragon Ball FighterZ (DVD9 to DVD5/6 or 7xCD)

Special thanks go to the FileForums' repacking veterans here.

Inno Setup Script template is based on pakrat2k2's Call of Duty: Modern Warfare 3 layout and my own Ridge Racer Unbounded script layout.

Current Script Version: Base Version.

Repacking Requirements:

- Inno Setup or Inno Script Studio (InnoIDE is defunct) - to compile the repack
- Post-Installation Files for the Game - i.e.: the game files you have after you have installed the game, whether you have installed it via Steam or via disc.

Repacking Instructions:

1. Download the "dbfz.7z" archive and extract its contents.

2. Locate all of the game's post-installation files, and note down the installation path that you have used to install the game in - e.g. if the game is installed in "C:\Program Files\BANDAI NAMCO Entertainment\Dragon Ball FighterZ", then simply note that down.

3. After you have done that, look for the following section in the Inno Setup script at the top of the page, and replace the path that is currently in the script as shown in Fig. 1 with the one you have noted down from Step 1, as shown in Fig. 2:

Fig. 1 - Before Editing The Script

#define SourcePath "D:\Dragon Ball FighterZ"

Fig. 2 - After Editing The Script (Example Provided)

#define SourcePath "C:\Program Files\BANDAI NAMCO Entertainment\Dragon Ball FighterZ"

4. Compile the repack now, and you should have seven files, which are:

- Dragon Ball FighterZ.exe: 686KB
- Dragon Ball FighterZ-1.bin: 699MB
- Dragon Ball FighterZ-2.bin: 699MB
- Dragon Ball FighterZ-3.bin: 699MB
- Dragon Ball FighterZ-4.bin: 699MB
- Dragon Ball FighterZ-5.bin: 699MB
- Dragon Ball FighterZ-6.bin: 693MB

Please note that the filesizes will vary slightly, depending on what files the end-user has, and what main executable he or she has, as a DRM-bypassed version of the main executable is usually significantly larger than a retail/original executable file.

Compiled on Microsoft Windows 10 x64.

[Scarlet Blade]

In a rather strange twist regarding creating installers that create shortcuts for easier access, I'm actually having an issue whereby if I use Inno Setup to create shortcuts, versus manually creating a shortcut directly from the target file, I get two completely different results, with the Inno Setup-created shortcut not working properly, in which this does apply to the experimental batch script I created to point to the target file, whereas the manually created shortcut works as it should.

Fig. 1: Inno Setup-created shortcut result



Fig. 2: Manually created shortcut result



Fig. 3: File hashes for the Inno Setup-created shortcut (top-left icon/top-left File Properties window), and for the manually created shortcut (bottom-left icon/bottom-middle File Properties window)



Can anybody please provide a way to fix this issue? Thank you.

UPDATE: I have tried creating an installer for Bat to Exe Converter as an experiment, and while the shortcut gets created and it supposedly points to the target file that exists in the target directory, the shortcut gives a blank image, and it is broken, stating that it cannot find the file, EVEN THOUGH IT EXISTS!

I am at a loss for words, as the previous repacks that I have made here actually work properly with the same shortcut settings, so I cannot find any obvious issues in the script whatsoever.

[pakrat2k2]

the line SetupIconFile=.\dbfz.ico should NOT have .\ infront of it. Script will read icon file wherever the ISS script is located.

[Scarlet Blade]

Originally Posted by pakrat2k2

the line SetupIconFile=.\dbfz.ico should NOT have .\ infront of it. Script will read icon file wherever the ISS script is located.

Thank you for that little tidbit of information - I'll keep that in mind for future reference, even though it does not remedy the dead shortcut issues I have been having.

I'll try creating the ISS script from scratch, and reinstalling Inno Setup from scratch to see if that remedies the problem.

UPDATE: After rewriting the script from scratch, I cannot get the shortcuts to work the way I want it to (see Fig. 2 for how I want the shortcuts to work).

HOWEVER, after installing Steam, and attempting to launch the game via the Inno Setup-created shortcut, it ACTUALLY launches Steam, like a Steam-created shortcut would do. In that case, I will leave this script as is, as I cannot see anything wrong with it at this moment in time.

[nsaer]

Originally Posted by Scarlet Blade

In a rather strange twist regarding creating installers that create shortcuts for easier access, I'm actually having an issue whereby if I use Inno Setup to create shortcuts, versus manually creating a shortcut directly from the target file, I get two completely different results, with the Inno Setup-created shortcut not working properly, in which this does apply to the experimental batch script I created to point to the target file, whereas the manually created shortcut works as it should.

Fig. 1: Inno Setup-created shortcut result



Fig. 2: Manually created shortcut result



Fig. 3: File hashes for the Inno Setup-created shortcut (top-left icon/top-left File Properties window), and for the manually created shortcut (bottom-left icon/bottom-middle File Properties window)



Can anybody please provide a way to fix this issue? Thank you.

UPDATE: I have tried creating an installer for Bat to Exe Converter as an experiment, and while the shortcut gets created and it supposedly points to the target file that exists in the target directory, the shortcut gives a blank image, and it is broken, stating that it cannot find the file, EVEN THOUGH IT EXISTS!

I am at a loss for words, as the previous repacks that I have made here actually work properly with the same shortcut settings, so I cannot find any obvious issues in the script whatsoever.

The game must be run as an administrator

[KaktoR]

Problem is probably, that shortcut will be created before the executable is unpacked. That's why the shortcut icon is blank. It's just a guess. I will check it for you

Edit:
I've just tested with a single random executable and it works fine here. Desktop/Start Menu shortcuts have icons and are running fine.

Edit2:
Nope, all is working fine. I've tested the game and didn't changed anything except for the game path. The problem is on your end.

[Scarlet Blade]

Originally Posted by nsaer

The game must be run as an administrator

Tried that - it still produces different results as I have mentioned earlier.

Originally Posted by KaktoR

Problem is probably, that shortcut will be created before the executable is unpacked. That's why the shortcut icon is blank. It's just a guess. I will check it for you

Edit:
I've just tested with a single random executable and it works fine here. Desktop/Start Menu shortcuts have icons and are running fine.

Edit2:
Nope, all is working fine. I've tested the game and didn't changed anything except for the game path. The problem is on your end.

You might actually be right (or so I thought). I tried to recompile the installer on my gaming system, but I get the same outcome, whereby the installer produces a shortcut that basically launches Steam, as opposed to the manually created shortcut that actually spits out the SteamAPI error, even though the two shortcuts point to the exact, same file in the exact, same location. It is weird, but I will live with that.

As I have stated though, I have compiled the installer on Microsoft Windows 10, using administrator privileges for obvious reasons.

Thanks for your help though.