I thought I'd document some things on the installer itself which will help if anyone wants to package it along with their own mods. (Also functioning as bumping this topic.) You'll notice I've done this with the GMDX installers I've done in the past.
In order to run the installer, you unpack it from your own (or copy it probably is better) to a temp directory and then call it like this:
Code: Select all
HDTP-Release3.exe /SILENT /NOCANCEL /TASKS="d3d9,otpuifix" /dir="C:\Deus Ex"
/SILENT = makes it not prompt anything. You'll provide all the other inputs it needs anyway on the command-line so it doesn't matter, assuming you get them right of course.
/NOCANCEL = eliminates the use of the CANCEL button. Good if you want it as a prerequisite to your own mod.
/TASKS = this specifies which things are selected within the installer, listed as described above. The tasks that I've defined in the installer are:
opengl = "Chris Donhal's OpenGL renderer v 2.1";
d3d9 = "Chris Donhal's DirectX 9 renderer r13"
d3d10 = "Kentie's DirectX 10 renderer r28"
d3d11 = "Kentie's DirectX 11 renderer r1" (coded for in the script but not enabled/built with as Kentie has not released a stable version of this)
otpuifix = "OTP User Interface Scaling Fix"
kentiedx = "Kentie's Deus Ex Replacement v 5.3"
All the renderers and default settings are installed no matter what, but the choice indicated is what is installed as the active renderer. So note that those are mutually exclusive
(meaning you only specify the default for your mod)
/DIR = the directory your mod installs in - you want this to be the main Deus Ex directory the user selects within YOUR installer. Here I have it installing into "C:\Deus Ex"
When I hear word of HDTP source files being released (or GMDX ones), I'll be releasing the corresponding installer scripts.