This page is for registering and setting up your custom sounds in your missions.

Why we have to do this, is because Graw2 doesn't allow custom sound mods like custom props. Why not? I can't work it out. I've spent 2-3 months on and off, and the only way I can get it to work is in the editor. Don't get me wrong, it does work in game but the problem is you can only have 1 sound mod working at a time in game but all the sounds in the editor??? So the best way I can get everyone to have new custom sounds in their new missions, is to have one mod that everyone downloads, and this is why we have to register. Such as life, the most easiest thing is the simplest thing. This means no big fancy scripting, just register and some small scripting.

So to explain how this works is simple -

First you must register, the next available slot,

Ie.

sound rego 1 = Radiator (Radiator = sound_rego_1.xml)

sound rego 2 = Davros (Davros = sound_rego_2.xml)

sound rego 3 = Bogie (Bogie = sound_rego_3.xml)

sound rego 4 = John (John = sound_rego_4.xml)

sound rego 5 = Spike (Spike = sound_rego5.xml)

sound rego 6 = YOUR NAME (so you will have = sound_rego_6.xml)

sound rego 7 =

There are 2 parts to setup.:- One in side the bundle and the other out side the bundle.

Part-1 ( out side the bundle)

First you add 2 XML files to your "local/english/sound" folder, they are (settings.xml & custom_sounds.xml). The settings.xml file over rights the original sounds in Graw2, it loads all the original sounds and then it looks at the new sounds in the custom_sounds.xml. In the custom_sounds.xml, I've added 100 pre-registered sounds. These files CAN NOT BE ALTERED, and are identified by rego_1, rego_2, rego_3 and so on up to rego_100.

What happens next is the custom_sounds.xml looks at a sound_rego_XXX.xml that you are registered to (Ie.I am registered to #1 so I renamed my xml to sound_rego_1.xml) This sound_rego_XXX.xml that you are registered to, will need to be added to the "local/english/sound" folder along with the settings.xml & custom_sounds.xml files. Then this "sound_rego_XXX.xml looks in your bundle file.

So for me I have:-

local/english/sound/settings.xml (this xml points to custom_sounds.xml)

local/english/sound/custom_sounds.xml (this xml points to sound_rego_XXX.xml)

local/english/sound/sound_rego_1.xml (this points to all of your sound folder within each of your mission bundles)

SCRIPTING:-

I'll use me as a example for the setups

YOU MUST NOT USE MY REGO NUMBER - THIS IS TO HELP YOU UNDERSTAND - YOU MUST USE YOUR REGO NUMBER -

You have downloaded a file "sound_rego_XXX.xml" .

Then you rename it to your number ( sound_rego_XXX.xml rename to sound_rego_1xml )

Open your sound_rego_XXX.xml in side it, it should look like this.

<?xml version="1.0" encoding="iso-8859-1"?>

<sound_rego_XXXxmlns:xi="x">

<xi:include href="/..\sound\YOURNAME_sounds_mission_1.xml#xpointer(/YOURNAME_sounds_mission_1/wavebanks/*)"/>

<xi:include href="/..\sound\YOURNAME_sounds_mission_2.xml#xpointer(/YOURNAME_sounds_mission_2/wavebanks/*)"/>

<xi:include href="/..\sound\YOURNAME_sounds_mission_3.xml#xpointer(/YOURNAME_sounds_mission_3/wavebanks/*)"/>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

<xi:include href="/..\sound\YOURNAME_sounds_mission_99.xml#xpointer(/YOURNAME_sounds_mission_99/wavebanks/*)"/>

<xi:include href="/..\sound\YOURNAME_sounds_mission_100.xml#xpointer(/YOURNAME_sounds_mission_100/wavebanks/*)"/>

</wavebanks>

<xi:include href="/..\sound\YOURNAME_sounds_mission_1.xml#xpointer(/YOURNAME_sounds_mission_1/soundbanks/*)"/>

<xi:include href="/..\sound\YOURNAME_sounds_mission_.2xml#xpointer(/YOURNAME_sounds_mission_2/soundbanks/*)"/>

<xi:include href="/..\sound\YOURNAME_sounds_mission_.3xml#xpointer(/YOURNAME_sounds_mission_3/soundbanks/*)"/>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

<xi:include href="/..\sound\YOURNAME_sounds_mission_.99xml#xpointer(/YOURNAME_sounds_mission_99/soundbanks/*)"/>

<xi:include href="/..\sound\YOURNAME_sounds_mission_.100xml#xpointer(/YOURNAME_sounds_mission_100/soundbanks/*)"/>

</soundbanks>

</sound_rego_XXX>

You must rename 2 things.

(1) Rename the open and closing tags to your rego number

<sound_rego_XXXxmlns:xi="x"> to <sound_rego_1xmlns:xi="x">

</sound_rego_XXX> to </sound_rego_1>

(2) Rename all the YOURNAME_ to your name.

<xi:include href="/..\sound\YOURNAME_sounds_mission_1.xml#xpointer(/YOURNAME_sounds_mission_1/wavebanks/*)"/>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

<xi:include href="/..\sound\YOURNAME_sounds_mission_2.xml#xpointer(/YOURNAME_sounds_mission_2/soundbanks/*)"/>

<xi:include href="/..\sound\radiator_sounds_mission_1.xml#xpointer(/radiator_sounds_mission_1/wavebanks/*)"/>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

<xi:include href="/..\sound\radiator_sounds_mission_2.xml#xpointer(/radiator_sounds_mission_2/soundbanks/*)"/>

There are 200 to change.

I use Window Excel to change all the YOURNAME to radiator.

Part one is all done.

========================================================================================

Part two. ( in the bundle or where your new mission files are keeped)

So to explain how this part works, you need three (3) XML files ( YOUR NAME HERE_sounds_mission_XXX_xml , YOUR MISSION_custom_wave_xml and YOUR MISSION_custom_sound_xml) you place these .xml files in your data/sound folder and to help make your first custom sounds to work in Graw2 and I add a .wav file too .

(test_code_word_irene.wav) add this to data/sound as well.

We'll start with "YOUR NAME HERE_sounds_mission_XXX_xml",

This xml just looks at "YOUR MISSION_custom_wave_xml" and "YOUR MISSION_custom_sound_xml" It doesn't really do anything, apart from stops anyone or everyone conflicting with your sounds.

SCRIPTING

Change YOUR NAME HERE to YOUR NAME.

( ie. YOUR NAME HERE_sounds_mission_XXX_xml = radiator_sounds_mission_XXX_xml)

Then you change the mission number (XXX) to your number for that mission.

This is where you have to keep a record of your missions so they don't conflict with each other, what this means is you have 100 premade missions with sounds. so you can't use "YOUR NAME HERE_mission_01_sounds.xml" for every mission. You have to change the number for every new mission.

YOUR NAME HERE_mission_02_sounds.xml, YOUR NAME HERE_mission_03_sounds.xml and so on....

For me ie. My first mission is BlackHawkDown, So I use "radiator_mission_01_sounds.xml" and my second mission I use "radiator_mission_02_sounds.xml" and so on for the third and forth missions.

I also have a file with a record of my missions to sound XML's. I have three (3) missions with sounds in them.

RADIATOR'S MISSION RECORD

(1) radiator_sounds_mission_01_xml = BlackHawkDown

(2) radiator_sounds_mission_02_xml = PearlHarbour

(3) radiator_sounds_mission_03_xml = HeavyDown

(4) radiator_sounds_mission_04_xml =

(5) radiator_sounds_mission_05_xml =

and so on......................

You can download this file if you like to.

( ie. YOUR NAME HERE_sounds_mission_XXX_xml = radiator_sounds_mission_01_xml)

open the file (YOUR NAME HERE_sounds_mission_XXX_xml ) in side it you will have to change three (3) things.

(1) Rename the open and closing tags from "YOUR NAME HERE" to "your name" ( this must be the same as the name you have given the xml file name)

(2) Rename the mission number (XXX) to the same as the xml file as well

(3) Rename YOUR MISSION to the name of your mission

It should look like this.( I'll use my first mission as an example)

</wavebanks>

</soundbanks>

</YOUR NAME HERE_sounds_mission_XXX>

The xml file "radiator_sounds_mission_01_xml"

<radiator_sounds_mission_01 xmlns:xi="x">

</wavebanks>

</soundbanks>

</radiator_sounds_mission_01>

Done.

The next two (2) XML's which are "YOUR MISSION_custom_wave_xml" and "YOUR MISSION_custom_sound_xml"

We'll start with YOUR MISSION_custom_wave_xml, the purpose of this xml file is to tell GRAW the names of the sounds and where the wave files (the new recorded sounds) are kept (which folder)

SCRIPTING

Rename YOUR MISSION to the name of your mission ( the same as before rad_blackhawkdown)

ie.. for me I changed "YOUR MISSION_custom_wave_xml" to rad_blackhawkdown_custom_wave_xml

open the file, it will look like this.

</wavebank>

Before we start here you should have the test_code_word_irene.wav file in your data/sound folder.

The first line "wavebank name=" This is name of the new group of .wav sounds that you are going load when you start up GRAW 2, it can be named what ever but it's should be named the same as your mission name.

"dir=" this is the path where the .wav files are kept.

Rename YOUR MISSION to your mission name

ie.. <wavebank name="YOUR MISSION_custom_wave" dir="data/sound" xmlns:xi="x">

The second line,

"wave name=" this is the name of the sound that your "YOUR MISSION_custom_sound_xml" will look for.

"file=" this is the .wav file that's linked to the "wave name="

For eg. you can name the "wave name=" rad_blackhawk_code_word_irene and the .wav file can be test_code_word_irene , a differant name.

But that way can get confusing, it's should be named the same. ie. the .wav file that you downloaded, it's name is "test_code_word_irene.wav " so the "wave name" and the "file name" should be named the same.

So for me, I have renamed the .wav file to "rad_blackhawkdown_code_word_irene.wav" so I will have,

But for now you just change:-

All done, you can add as many wave files and names as you like.

This is what I have in my BlackHawkDown map

"rad_blackhawkdown_custom_wave_xml"

</wavebank>

That's all for "YOUR MISSION_custom_wave_xml" lets move to the last XML."YOUR MISSION_custom_sound_xml"

This xml tells the game how to play the .wav sounds in game.

There are many ways to have this, player sound - world sound - location sound - large props - small props and so on....

And a lot of them are very unstable if you play a long sound ( ie.. if we set up a sound as a small prop, lets say a long music song is playing on a radio and you fire your gun., the sound crashes and stops playing)

So the two I found that are the best is, world and large props sounds.

The world sounds will play the sounds for everyone at the same time.

And the large props sounds are played at a location, which the size of the location can be alted ( 1 metre to 100 or more metres)

SCRIPTING - "YOUR MISSION_sound_xml"

The same as before -

Rename the xml fileYOUR MISSION_custom_sound_xml to your mission name ( ie.. "YOUR MISSION_custom_sound_xml" to "rad_blackhawkdown_custom_sound_xml")

Open the file, it should look like this.

I'll give you two (2) different ways to have the sounds, one is a world sound (ambient_loop) and the second is a location sound (large_props)

</sound>

</sound>

</soundbank>

We will not do any scripting with this one, It's setup to work.

I will just explain how to set it up.

"sound name="this is the name of the sound that you'll see in the editor

"group=" this is how the sound is played, there are 9 or so different ways they can be played, but some are unstable and there is really only four (4) you can use.

They are:-

(1) small props :- this has a sound radius of around 5 metres and is unstable with long playing sounds ie.. music sounds . (this is a location sound)

(2) Large Props :- this has a sound radius of around 25 metres and is very stable. (this is a location sound)

(3) narcom:- this has NO sound radius and is played to a side (ie. team "a" or team "b") and plays 90% of the time with no problems.

(4) ambient_loop :- This is a world sound that everyone can hear, it has no radius. This is a very stable sound.

I would NOT use number three (3) , most of the time COOP type games have only one (1) side anyway, So I would use number four (4) ambient_loop to play for everyone

I would also NOT use number one (1) Small Props this is very unstable with long playing sounds and there is no need for this type of sound, because which bring me to the next part

"zero_distance=" This set the distance from the centre point how far you hear the sound, This is why you don't need small props. you can have the large props playing a sound, 1 or 5 metre radius from the centre, just like a small props.

"has_custom_distances=" this must be set to true for large props.

"positioning=" this can be "2d" or "3d", I found that "2d" works better.

"loop=" this can be "true" or "false" if this is set to true the sound will play over and over again.

I have some of my sounds set to true, for eg.. In BlackHawkDown in the computer room, the computer sounds are playing over and over and I can stop and start them playing from with in the mission.XML . I will explain this later in sound and mission editing

"gain=" this is your volume control and can be set from -25 to 25. if you can just hear the sound in game,and you have the gain set to 5. You can turn the sound up by changing the number to 10.

the second line " <wave name="test_code_word_irene"/>

This is the name of the sound, that plays. and this name comes from your custom_wave.XML

("YOUR MISSION_custom_wave_xml"

<wave name="YOUR SOUND NAME" file="THE WAV FILE NAME.wav" stream="true" />).

That's all you need for setting up your LARGE_PROPS.

AMBIENT_LOOP also known as world sounds - There is not much you need to change with this one, apart from the "gain" and "loop"

Here's what I have in my "rad_blackhawkdown_custom_sound_xml"

<?xml version="1.0" encoding="iso-8859-1"?>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sequence>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

</sound>

<queue>

</queue>

</sound>

</group>

</sound>

<queue>

</queue>

</sound>

</group>

</sound>

<queue>

</queue>

</sound>

</group>

</sound>

</sequence>

</sound>

</sound>

</sound>

</sound>

</sound>

</soundbank>

You can see there are different ways I setup the sounds ie..

</sequence>

<queue>

</queue>

And I will explain this later, in sound and mission editing.

Well you are all finished, just start-up your graw2 editor, go to the sound tab and place a sound on your map. Then type in one at a time the two sounds "test_location_sound" "test_world_sound" in the sound cue tab .You must place the man on the map to hear the sounds.

You'll know if the sound works, because the sound location in the editor will go from gray to green.

When you send the map out for testing, they must download your bundle and the three XML files,

local/english/sound/settings.xml

local/english/sound/custom_sounds.xml

local/english/sound/sound_rego_XXXxml

They only have to download the three XML files once.

If they already have them. for ie..."settings.xml" "custom_sounds.xml" "sound_rego_01xml"("sound_rego_01xml" is all of radiators sounds) and John sends out a map they only have to download his sound pack ( (John = sound_rego_4.xml)

so they would have four XML files

"settings.xml"

"custom_sounds.xml"

"sound_rego_01xml"

"sound_rego_04xml

Now John and I can make 100 mission each and they don't have to download any XML file of our future missions.

SOUND AND MISSION EDITING

HAVE FUN

Rad....

Adding New Custom Sounds