uglycat on 27/9/2007 at 01:23

---

i felt like replaying this great game all of a sudden. what i'd like to do is to replace the stock sounds with new ones, as the originals are rather weak nowadays.

unfortunatly, it doesn't seem as simple as recreating the directory structure and plopping files that are named correctly to override them... it seems like i need to make a .u file, but there doesn't seem to be much information about that out there.

i know the main sounds that i want to replace are in the DeusExSounds.u file but there isn't really any information on how to make a .u file.

i've extracted all the contents with DeusExExtractor.exe, what i was planning to do was to replace what i want, and them repackage all those files into a new DeusExSounds.u

can any one tell me if there is a program out there that does it? afaik, the sdk doesn't, but i've seen other mods out there with .u files, so it must be possible...

Dr. Dumb_lunatic on 27/9/2007 at 11:16

---

The SDK should come complete with the UCC.exe compiler thingy, which is what you use to make .u packages.

If you've already extracted all the sounds, and made your replacements (keeping the filenames identical, hopefully), it's as simple as opening your system folder and finding deusexsounds.u...and deleting it. (I'd move it to a backups folder, actually: as long as it's not in the system folder it's ignored).

Then open a commandprompt, navigate to the system folder (usually "cd.." a couple of times to get to a raw c:\> prompt, and then "cd deusex\system" -no quotes)


At the system prompt, type

ucc make

And watch that compiler go! It looks through all the packages it SHOULD have, according to deusex.ini, and if it can't find them, recompiles them. It won't find deusexsounds, so it'll make a new one, using the sounds you provided (and put in the right place, hopefully).

Dr. Dumb_lunatic on 28/9/2007 at 10:32

---

Ahhhh..this old problem.

Well, you're either going to have to do some file renaming, or some code editing.

Both are fairly trivial in difficulty, but tiresome in execution.

Basically, when you import a file into a u package, be it a sound, texture, or whatever, you use an #exec import line, in which you specify what you're importing, what you want to call it, which group it'll be in (like 'generic', or 'weapons'), and what the filename actually is (and where the file is).

In other words, the filename of the original sound, and the name of the sound in compiled form...do not need to be the same. And, as you've seen: often are not.

I could import a file called DDL_is_A_N00b.wav, but tell the compiler to call the newly imported file LamExplode. The compiler doesn't care, after all.

In all code references thence onward, I would reference the file as sound'mypackage.LamExplode'

And, yes: if I exported the sound, it would be exported as lamexplode.wav, not as its original name.


Sooo....you need to open the classes folder in deusexsounds and look at the import lines (you can open/edit the .uc files with notepad quite happily).

And hunt for mismatches between the sounds it's trying to import, and the filenames. Either change the filenames to match the original import lines, or change the import lines to match the new filenames.

I would suggest the latter:

Find lines like this:



And change them so that the FILE= is the same as the NAME=

Thusly:




Yes, it's tedious, and ill-conceived from a coding standpoint, but there you go.

uglycat on 29/9/2007 at 18:27

---

i wrote a crappy VB program to rename all the filenames in the script file correctly...

(http://rapidshare.com/files/59128443/DeusExScriptRename.zip.html)

it's not amazing, and probably won't work on a lot of machines because i don't know what runtime files it needs... probably needs those .net framework 1.1 or 2.0 or something.
if you have Visual Studio 2005 installed, there's a good chance it will work for you though. :P