Total War Modding - User contributions [en]

Audio modding

2023-05-19T19:00:58Z

H3ro:

After a long time, Audio modding is now possible (for Warhammer 3 at least!)

== Wwise ==
The total war games uses an audio engine called Wwise. This is a very powerful, but complex system. If you want to audio modding, you also need to get a basic understanding of the tool.

Its higly recommended that you read '''[https://github.com/bnnm/wwiser/blob/master/doc/WWISER.md this]''' and spend some time exploring the data using the "Audio Explorer" tool

=== WWise Naming ===
The first thing to understand, there is no names in wwise. When a wwise project is compiled (saved for use) the tool converts all the names into ids. This is why the game has a ton of files called 9484940112.wem. At some point they were named Karl_Eating_Goblins.wem and so on, but that name is converted (hashed)

=== Wwise event structure ===
Everything in wwise starts with an event (apart from music which is party controlled by some strange script). '''The game will typically refer to the events, either in script, anim.meta file or db.'''

There are two event types, '''Event''' and '''Dialog_event'''. After the event there is a chain of object that leads you to the actual audio played.

For example this basic '''Event''' will play a random sound from a collection of two.

Karl_Eating_Goblin_Event => Karl_Eating_Goblin_Event_ActionPlay => Random Container => Soundx.mp3 and soundy.mp3.

They follow a basic pattern most of the time. Event => Action => Container (optional) => Sound(s)

For more information look at wwisers documentation (without the project, there would be no audio modding) => https://github.com/bnnm/wwiser/blob/master/doc/WWISER.md

The second event type is a '''Dialog_Event'''. It has nothing to do with dialog, its a lookup table that results in container or sound object.
{| class="wikitable"
|+Enemy_spotted dialog event
!UnitVoiceActor
!UnitType
!SpottedFacton
!Child
|-
|Orc_Female_1
|Ranged
|Human
|123
|-
|Orc_Male_1
|Ranged
|DarkElf
|456
|-
|OrC_Male2
|Melee
|Orc
|678
|}
When the even is triggered, the game sets a set of variables which are used to lookup the child node, which typically points to a Container which in turn points to sounds

Currently Dialog_Events can not be modded, but soon...

The last important bit is the '''ActorMixer''' object. This object controls who owns the sounds. Is it a UI sound, game sound, battle sound and so on. This is important to make the sound play as not all ActorMixer has their volume set at all times

== Exploring Wwise in AssetEditor. ==
In AssetEditor there is a tool for exploring the audio data, called "Audio Explorer". This can be used to learn about how wwise works. It has multiple use case.

[[File:AssetEditor audio tool.png|thumb|alt=]]

=== Learn how wwise works ===
The tool allows pretty much all wwise objects to be explored. This is very useful to learn how you later can use the compiler to add new sounds. Under extra you can pick between Events and Dialog_Events.

The left side shows the full graph of the selected event, while the right side shows a detailed view of the Wwise data of the selected node.

=== Find what sound file to replace for a given event (Finding the real name of the 213123123123.wem files) ===
[[File:Audio explorer find soundname.png|thumb|alt=|How to make sense of the sound names in total war]]
Using this tool its very easy to lean which sound file is linked to what event.

Say you want to make a mod that replaces all of Throggs diplomacy lines. Doing a search in the database will give you all the events used, you can then look that up in the events view.

If one takes the event "Play_Nor_Throgg_Dip_Dwf_Greet_Neg_02" which is for when Throgg talks to dwarfs, one can see that this is linked to the sound file "605570708.wem"
=== Learn which audiomixer and audio bus is used for a group of sounds ===
[[File:Audio explorer find mixer.png|thumb|alt=|How to find the correct ActorMixer for adding custom sounds]]
All sounds have to be connected to a mixer (which in turn is connected to a bus). Not all busses have their volume set at all times. For example the UI and Battle bus is not both enabled at the same time. Because of this its important that the correct mixer is selected when adding new sounds. When selecting a Sound node on the left side, "Parent structure" is added on the right side. Here you can see the mixers and busses connected to the sound. you typically want to use the fist id of the first ActorMixer with an audio bus for the "RootAudioMixer" setting in your custom audio project.

=== Adding new Audio ===
We have tried to make adding new sounds as simple as possible. This is done using the Audio Compiler in AssetEditor. AssetEditor tries to fill out as much data as possible, to make it as simple as possible.
[[File:Audio compiler.png|thumb|The Audio Compiler]]
The format looks like this:
{
"Settings": {
"BnkName": "campaign_diplomacy",
"RootAudioMixer": "54848735",
"Language": "English(uk)"
},

"Events": [
{
"Name": "Play_Foo",
"Sound": "Audio\\WWise\\729867288.wem"
},
{
"Name": "Play_Bar",
"Sound": "Audio\\WWise\\906470917.wem"
}]
} 
{| class="wikitable"
|+Project explanation
!Attribute
!Description
!Example Value
|-
|Settings.BnkName
|The name of the created bnk file. Files can not be renamed as the file reference the name internally.
|customfaction_campaign_diplomacy
|-
|Settings.RootAudioMixer
|The mixer the sounds should belong to. See "Learn which audiomixer and audio bus is used for a group of sounds"
|54848735, which is the id for diplomacy lines
|-
|Settings.Language
|If the file is a language bnk, this needs to be set to the same name as one of the audio folders in the game
|English(uk)
|-
|Events
|A list of all the events
|
|-
|Event.Name
|The name which the game will use to find the sound
|Play_Foo
|-
|Event.Sound
|The path to the audio file in a packf
|Audio\\WWise\\906470917.wem
|-
|Event.FileSystemSound
|The path to the audio file on disk. It will be auto converted to a wem
|C:\\Users\\username\\soundLib\\wet-fart-6139.mp3
|}

Coming features:

* Support for adding dialog_events
* Support for containers like random.
* Fixed names for known ActorMixers

== File Types ==
Wem => The audio file format used by wwise

Bnk => The sound database used by wwise

Dat => A lookup table for connecting event names to wwise

Json => Projectfile for the audio compiler.

File:Audio compiler.png

2023-05-19T18:59:45Z

H3ro:

The audio compiler

Audio modding

2023-05-19T18:57:17Z

H3ro:

After a long time, Audio modding is now possible (for Warhammer 3 at least!)

== Wwise ==
The total war games uses an audio engine called Wwise. This is a very powerful, but complex system. If you want to audio modding, you also need to get a basic understanding of the tool.

Its higly recommended that you read '''[https://github.com/bnnm/wwiser/blob/master/doc/WWISER.md this]''' and spend some time exploring the data using the "Audio Explorer" tool

=== WWise Naming ===
The first thing to understand, there is no names in wwise. When a wwise project is compiled (saved for use) the tool converts all the names into ids. This is why the game has a ton of files called 9484940112.wem. At some point they were named Karl_Eating_Goblins.wem and so on, but that name is converted (hashed)

=== Wwise event structure ===
Everything in wwise starts with an event (apart from music which is party controlled by some strange script). '''The game will typically refer to the events, either in script, anim.meta file or db.'''

There are two event types, '''Event''' and '''Dialog_event'''. After the event there is a chain of object that leads you to the actual audio played.

For example this basic '''Event''' will play a random sound from a collection of two.

Karl_Eating_Goblin_Event => Karl_Eating_Goblin_Event_ActionPlay => Random Container => Soundx.mp3 and soundy.mp3.

They follow a basic pattern most of the time. Event => Action => Container (optional) => Sound(s)

For more information look at wwisers documentation (without the project, there would be no audio modding) => https://github.com/bnnm/wwiser/blob/master/doc/WWISER.md

The second event type is a '''Dialog_Event'''. It has nothing to do with dialog, its a lookup table that results in container or sound object.
{| class="wikitable"
|+Enemy_spotted dialog event
!UnitVoiceActor
!UnitType
!SpottedFacton
!Child
|-
|Orc_Female_1
|Ranged
|Human
|123
|-
|Orc_Male_1
|Ranged
|DarkElf
|456
|-
|OrC_Male2
|Melee
|Orc
|678
|}
When the even is triggered, the game sets a set of variables which are used to lookup the child node, which typically points to a Container which in turn points to sounds

Currently Dialog_Events can not be modded, but soon...

The last important bit is the '''ActorMixer''' object. This object controls who owns the sounds. Is it a UI sound, game sound, battle sound and so on. This is important to make the sound play as not all ActorMixer has their volume set at all times

== Exploring Wwise in AssetEditor. ==
In AssetEditor there is a tool for exploring the audio data, called "Audio Explorer". This can be used to learn about how wwise works. It has multiple use case.

[[File:AssetEditor audio tool.png|thumb|alt=|none]]

=== Learn how wwise works ===
The tool allows pretty much all wwise objects to be explored. This is very useful to learn how you later can use the compiler to add new sounds. Under extra you can pick between Events and Dialog_Events.

The left side shows the full graph of the selected event, while the right side shows a detailed view of the Wwise data of the selected node.

=== Find what sound file to replace for a given event ===
[[File:Audio explorer find soundname.png|thumb]]
Using this tool its very easy to lean which sound file is linked to what event.

Say you want to make a mod that replaces all of Throggs diplomacy lines. Doing a search in the database will give you all the events used, you can then look that up in the events view.

If one takes the event "Play_Nor_Throgg_Dip_Dwf_Greet_Neg_02" which is for when Throgg talks to dwarfs, one can see that this is linked to the sound file "605570708.wem"

=== Learn which audiomixer and audio bus is used for a group of sounds ===
[[File:Audio explorer find mixer.png|thumb]]
All sounds have to be connected to a mixer (which in turn is connected to a bus). Not all busses have their volume set at all times. For example the UI and Battle bus is not both enabled at the same time. Because of this its important that the correct mixer is selected when adding new sounds. When selecting a Sound node on the left side, "Parent structure" is added on the right side. Here you can see the mixers and busses connected to the sound. you typically want to use the fist id of the first ActorMixer with an audio bus for the "RootAudioMixer" setting in your custom audio project.

=== Adding new Audio ===
We have tried to make adding new sounds as simple as possible. This is done using the Audio Compiler in AssetEditor. AssetEditor tries to fill out as much data as possible, to make it as simple as possible.

The format looks like this:
{
"Settings": {
"BnkName": "campaign_diplomacy",
"RootAudioMixer": "54848735",
"Language": "English(uk)"
},

"Events": [
{
"Name": "Play_Foo",
"Sound": "Audio\\WWise\\729867288.wem"
},
{
"Name": "Play_Bar",
"Sound": "Audio\\WWise\\906470917.wem"
}]
} 
{| class="wikitable"
|+Project explanation
!Attribute
!Description
!Example Value
|-
|Settings.BnkName
|The name of the created bnk file. Files can not be renamed as the file reference the name internally.
|customfaction_campaign_diplomacy
|-
|Settings.RootAudioMixer
|The mixer the sounds should belong to. See "Learn which audiomixer and audio bus is used for a group of sounds"
|54848735, which is the id for diplomacy lines
|-
|Settings.Language
|If the file is a language bnk, this needs to be set to the same name as one of the audio folders in the game
|English(uk)
|-
|Events
|A list of all the events
|
|-
|Event.Name
|The name which the game will use to find the sound
|Play_Foo
|-
|Event.Sound
|The path to the audio file in a packf
|Audio\\WWise\\906470917.wem
|-
|Event.FileSystemSound
|The path to the audio file on disk. It will be auto converted to a wem
|C:\\Users\\username\\soundLib\\wet-fart-6139.mp3
|}

Coming features:

* Support for adding dialog_events
* Support for containers like random.
* Fixed names for known ActorMixers

== File Types ==
Wem => The audio file format used by wwise

Bnk => The sound database used by wwise

Dat => A lookup table for connecting event names to wwise

Json => Projectfile for the audio compiler.

File:Audio explorer find mixer.png

2023-05-19T18:51:12Z

H3ro:

File:Audio explorer find soundname.png

2023-05-19T18:49:56Z

H3ro:

Audio modding

2023-04-27T18:36:20Z

H3ro:

After a long time, Audio modding is now possible (for Warhammer 3 at least!)

== Wwise ==
The total war games uses an audio engine called Wwise. This is a very powerful, but complex system. If you want to audio modding, you also need to get a basic understanding of the tool.

=== WWise Naming ===
The first thing to understand, there is no names in wwise. When a wwise project is compiled (saved for use) the tool converts all the names into id strings. This is why the game has a ton of files called 9484940112.wem. At some point they were named Karl_Eating_Goblins.wem and so on, but that name is converted (hashed)

=== Wwise event structure ===
Everything in wwise starts with an event (apart from music).

There are two event types, Event and Dialog_event. After the event there is a chain of object that leads you to the actual audio played.

For example this basic event with will play a random sound from a collection of two.

Karl_Eating_Goblin_Event => Karl_Eating_Goblin_Event_ActionPlay => Random Container => Soundx.mp3, soundy.mp3.

They follow a basic pattern most of the time. Event => Action => Container (optional) => Sound(s)

The second event type is a dialog_Event. It has nothing to do with dialog, its a lookup table that results in container or sound object.
{| class="wikitable"
|+Enemy_spotted dialog event
!UnitVoiceActor
!UnitType
!SpottedFacton
!Child
|-
|Orc_Female_1
|Ranged
|Human
|123
|-
|Orc_Male_1
|Ranged
|DarkElf
|456
|-
|OrC_Male2
|Melee
|Orc
|678
|}
When the even is triggered, the game sets a set of variables which are used to lookup the child node, which typically points to a Container which in turn points to sounds

Currently Dialog_Events can not be modded, but soon...

The last important bit is the ActorMixer object. This object controls who owns the sounds. Is it a UI sound, game sound, battle sound and so on. This is important to make the sound play as not all ActorMixer has their volume set at all times

== Exploring Wwise in AssetEditor. ==
In AssetEditor there is a tool for exploring the audio data, called "Audio Explorer". This can be used to learn about how wwise works. It also allows you to find which ActorMixer Id you should use and what file to replace if you want to update the sound of something.
[[File:AssetEditor audio tool.png|left|thumb]]In the tool you get a list of all the events in the game. Under extra you can select if you want Events, Dialog_events or both. Picking one from the dropdown gives you the wwise object graph for the selected events.

In the example here, you see the "Evemt_battle_IND_Small_arms_dlc12_rattling_gun_fire_play_event". Somewhere in the game database or meta data files, there will be a reference to this name.

The event contains a play action, followed by a set of random containers. Why they are nested instead of one large, no one knows. But from this you can see all the sounds connected. If you want to replace a specific sound, this gives you the wav file to replace. The tool also allows you to preview the sounds.

=== Adding new Audio (Soon to be released, fixing bugs) ===
We have tried to make adding new sounds as simple as possible. This is done using the Audio Compiler in AssetEditor. AssetEditor tries to fill out as much data as possible, to make it as simple as possible.

This is done using the Audio Compiler, which takes a textfile as an input. The format looks like this:
{
"Settings": {
"Version": 1,
"OutputGame": "Warhammer3",
"BnkName": "campaign_diplomacy__ovn",
"RootAudioMixer": "54848735",
"Language": "English(uk)"
},

"Events": [
{
"Name": "Play_Foo",
"Sound": "Audio\\WWise\\729867288.wem"
},
{
"Name": "Play_Bar",
"Sound": "Audio\\WWise\\906470917.wem"
}]
} 
{| class="wikitable"
|+Project explanation
!Attribute
!Description
!Example Value
|-
|Settings.Version
|The version of the project file
|1
|-
|Settings.OutputGame
|The game to compile the audio project to.
|Warhammer3
|-
|Settings.BnkName
|The name of the created bnk file. Files can not be renamed as the file reference the name internally.
|
|-
|Settings.RootAudioMixer
|The mixer the sounds should belong to
|54848735, which is the id for diplomacy lines
|-
|Settings.Language
|If the file is a language bnk, this needs to be set to the same name as one of the audio folders in the game
|English(uk)
|-
|Events
|A list of all the events
|
|-
|Event.Name
|The name which the game will use to find the sound
|Play_Foo
|-
|Event.Sound
|The path to the audio file. At this point it needs to be imported manually and converted
|Audio\\WWise\\906470917.wem
|}

Coming features:

* Audio file importer/converter
* Support for adding dialog_events
* Support for containers like random.
* Fixed names for known ActorMixers

== File Types ==
Wem => The audio file format used by wwise

Bnk => The sound database used by wwise

Dat => A lookup table for connecting event names to wwise

Json => Projectfile for the audio compiler.

Audio modding

2023-04-27T18:35:18Z

H3ro: /* Adding new Audio */

After a long time, Audio modding is now possible (for Warhammer 3 at least!)

== Wwise ==
The total war games uses an audio engine called Wwise. This is a very powerful, but complex system. If you want to audio modding, you also need to get a basic understanding of the tool.

=== WWise Naming ===
The first thing to understand, there is no names in wwise. When a wwise project is compiled (saved for use) the tool converts all the names into id strings. This is why the game has a ton of files called 9484940112.wem. At some point they were named Karl_Eating_Goblins.wem and so on, but that name is converted (hashed)

=== Wwise event structure ===
Everything in wwise starts with an event (apart from music).

There are two event types, Event and Dialog_event. After the event there is a chain of object that leads you to the actual audio played.

For example this basic event with will play a random sound from a collection of two.

Karl_Eating_Goblin_Event => Karl_Eating_Goblin_Event_ActionPlay => Random Container => Soundx.mp3, soundy.mp3.

They follow a basic pattern most of the time. Event => Action => Container (optional) => Sound(s)

The second event type is a dialog_Event. It has nothing to do with dialog, its a lookup table that results in container or sound object.
{| class="wikitable"
|+Enemy_spotted dialog event
!UnitVoiceActor
!UnitType
!SpottedFacton
!Child
|-
|Orc_Female_1
|Ranged
|Human
|123
|-
|Orc_Male_1
|Ranged
|DarkElf
|456
|-
|OrC_Male2
|Melee
|Orc
|678
|}
When the even is triggered, the game sets a set of variables which are used to lookup the child node, which typically points to a Container which in turn points to sounds

Currently Dialog_Events can not be modded, but soon...

The last important bit is the ActorMixer object. This object controls who owns the sounds. Is it a UI sound, game sound, battle sound and so on. This is important to make the sound play as not all ActorMixer has their volume set at all times

== Exploring Wwise in AssetEditor. ==
In AssetEditor there is a tool for exploring the audio data, called "Audio Explorer". This can be used to learn about how wwise works. It also allows you to find which ActorMixer Id you should use and what file to replace if you want to update the sound of something.
[[File:AssetEditor audio tool.png|left|thumb]]In the tool you get a list of all the events in the game. Under extra you can select if you want Events, Dialog_events or both. Picking one from the dropdown gives you the wwise object graph for the selected events.

In the example here, you see the "Evemt_battle_IND_Small_arms_dlc12_rattling_gun_fire_play_event". Somewhere in the game database or meta data files, there will be a reference to this name.

The event contains a play action, followed by a set of random containers. Why they are nested instead of one large, no one knows. But from this you can see all the sounds connected. If you want to replace a specific sound, this gives you the wav file to replace. The tool also allows you to preview the sounds.

=== Adding new Audio ===
We have tried to make adding new sounds as simple as possible. This is done using the Audio Compiler in AssetEditor. AssetEditor tries to fill out as much data as possible, to make it as simple as possible.

This is done using the Audio Compiler, which takes a textfile as an input. The format looks like this:
{
"Settings": {
"Version": 1,
"OutputGame": "Warhammer3",
"BnkName": "campaign_diplomacy__ovn",
"RootAudioMixer": "54848735",
"Language": "English(uk)"
},

"Events": [
{
"Name": "Play_Foo",
"Sound": "Audio\\WWise\\729867288.wem"
},
{
"Name": "Play_Bar",
"Sound": "Audio\\WWise\\906470917.wem"
}]
} 
{| class="wikitable"
|+Project explanation
!Attribute
!Description
!Example Value
|-
|Settings.Version
|The version of the project file
|1
|-
|Settings.OutputGame
|The game to compile the audio project to.
|Warhammer3
|-
|Settings.BnkName
|The name of the created bnk file. Files can not be renamed as the file reference the name internally.
|
|-
|Settings.RootAudioMixer
|The mixer the sounds should belong to
|54848735, which is the id for diplomacy lines
|-
|Settings.Language
|If the file is a language bnk, this needs to be set to the same name as one of the audio folders in the game
|English(uk)
|-
|Events
|A list of all the events
|
|-
|Event.Name
|The name which the game will use to find the sound
|Play_Foo
|-
|Event.Sound
|The path to the audio file. At this point it needs to be imported manually and converted
|Audio\\WWise\\906470917.wem
|}

Coming features:

* Audio file importer/converter
* Support for adding dialog_events
* Support for containers like random.
* Fixed names for known ActorMixers

== File Types ==
Wem => The audio file format used by wwise

Bnk => The sound database used by wwise

Dat => A lookup table for connecting event names to wwise

Json => Projectfile for the audio compiler.

Audio modding

2023-04-27T18:33:25Z

H3ro:

After a long time, Audio modding is now possible (for Warhammer 3 at least!)

== Wwise ==
The total war games uses an audio engine called Wwise. This is a very powerful, but complex system. If you want to audio modding, you also need to get a basic understanding of the tool.

=== WWise Naming ===
The first thing to understand, there is no names in wwise. When a wwise project is compiled (saved for use) the tool converts all the names into id strings. This is why the game has a ton of files called 9484940112.wem. At some point they were named Karl_Eating_Goblins.wem and so on, but that name is converted (hashed)

=== Wwise event structure ===
Everything in wwise starts with an event (apart from music).

There are two event types, Event and Dialog_event. After the event there is a chain of object that leads you to the actual audio played.

For example this basic event with will play a random sound from a collection of two.

Karl_Eating_Goblin_Event => Karl_Eating_Goblin_Event_ActionPlay => Random Container => Soundx.mp3, soundy.mp3.

They follow a basic pattern most of the time. Event => Action => Container (optional) => Sound(s)

The second event type is a dialog_Event. It has nothing to do with dialog, its a lookup table that results in container or sound object.
{| class="wikitable"
|+Enemy_spotted dialog event
!UnitVoiceActor
!UnitType
!SpottedFacton
!Child
|-
|Orc_Female_1
|Ranged
|Human
|123
|-
|Orc_Male_1
|Ranged
|DarkElf
|456
|-
|OrC_Male2
|Melee
|Orc
|678
|}
When the even is triggered, the game sets a set of variables which are used to lookup the child node, which typically points to a Container which in turn points to sounds

Currently Dialog_Events can not be modded, but soon...

The last important bit is the ActorMixer object. This object controls who owns the sounds. Is it a UI sound, game sound, battle sound and so on. This is important to make the sound play as not all ActorMixer has their volume set at all times

== Exploring Wwise in AssetEditor. ==
In AssetEditor there is a tool for exploring the audio data, called "Audio Explorer". This can be used to learn about how wwise works. It also allows you to find which ActorMixer Id you should use and what file to replace if you want to update the sound of something.
[[File:AssetEditor audio tool.png|left|thumb]]In the tool you get a list of all the events in the game. Under extra you can select if you want Events, Dialog_events or both. Picking one from the dropdown gives you the wwise object graph for the selected events.

In the example here, you see the "Evemt_battle_IND_Small_arms_dlc12_rattling_gun_fire_play_event". Somewhere in the game database or meta data files, there will be a reference to this name.

The event contains a play action, followed by a set of random containers. Why they are nested instead of one large, no one knows. But from this you can see all the sounds connected. If you want to replace a specific sound, this gives you the wav file to replace. The tool also allows you to preview the sounds.

== Adding new Audio ==
We have tried to make adding new sounds as simple as possible. This is done using the Audio Compiler in AssetEditor. AssetEditor tries to fill out as much data as possible, to make it as simple as possible.

This is done using the Audio Compiler, which takes a textfile as an input. The format looks like this:
{
"Settings": {
"Version": 1,
"OutputGame": "Warhammer3",
"BnkName": "campaign_diplomacy__ovn",
"RootAudioMixer": "54848735",
"Language": "English(uk)"
},

"Events": [
{
"Name": "Play_Foo",
"Sound": "Audio\\WWise\\729867288.wem"
},
{
"Name": "Play_Bar",
"Sound": "Audio\\WWise\\906470917.wem"
}]
} 
{| class="wikitable"
|+Project explanation
!Attribute
!Description
!Example Value
|-
|Settings.Version
|The version of the project file
|1
|-
|Settings.OutputGame
|The game to compile the audio project to.
|Warhammer3
|-
|Settings.BnkName
|The name of the created bnk file. Files can not be renamed as the file reference the name internally.
|
|-
|Settings.RootAudioMixer
|The mixer the sounds should belong to
|54848735, which is the id for diplomacy lines
|-
|Settings.Language
|If the file is a language bnk, this needs to be set to the same name as one of the audio folders in the game
|English(uk)
|-
|Events
|A list of all the events
|
|-
|Event.Name
|The name which the game will use to find the sound
|Play_Foo
|-
|Event.Sound
|The path to the audio file. At this point it needs to be imported manually and converted
|Audio\\WWise\\906470917.wem
|}

Coming features:

* Audio file importer/converter
* Support for adding dialog_events
* Support for containers like random.
* Fixed names for known ActorMixers

Audio modding

2023-04-27T18:27:56Z

H3ro: /* Adding new Events */

Audio modding

2023-04-27T18:24:19Z

H3ro: /* Wwise */

Audio modding

2023-04-27T18:19:45Z

H3ro: /* Wwise */

File:AssetEditor audio tool.png

2023-04-27T18:19:23Z

H3ro:

AssetEditor audio tool

Audio modding

2023-04-27T18:15:42Z

H3ro:

Audio modding

2023-04-27T18:07:28Z

H3ro: Created page with "After a long time, Audio modding is now possible (for Warhammer 3 at least!) == Wwise == The total war games uses an audio engine called Wwise. This is a very powerful, but..."

Tutorial:AssetEditor

2022-09-01T10:15:00Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

'''Download link''': [https://github.com/olekristianhomelien/TheAssetEditor/releases/latest https://github.com/donkeyProgramming/TheAssetEditor/releases/latest]

'''Youtube tutorials:''' https://www.youtube.com/channel/UCXnf2q9fRNYlMn4XULPLKgg

'''Beginner tutorial by FaallenOon:''' [https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw/edit https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw]

'''Disclaimer''': I am not good at technical writing or enjoy it, so if someone feels the desire to improve this, then please!

==The Basics==

===Creating a New Packfile===
To create a new packfile go to the top left corner of the program and click file then select New Packfile and a window will open asking you to enter a name, once you have entered a name press ok and your packfile will be created in the file browser to the left and will be marked as active which is identified by '''bold''' text.

===Opening a Model ===
To get started working with models navigate to the file browser on the left and open the All CA Packs folder, scroll down to variantmeshes, into wh_variantmodels and browse through the list for a model of your choosing and once you have found the model that you seek you can double click upon the rigid_model_v2 file to open the model within the 3d viewer.

====How to find a Model====
If you have an idea of what kind of model you are looking for you can use the Search Filter box at the top of the file browser to try and narrow down the amount of folders you need to search through but if you do not then you can take a rough guess at where models are located by the folder names which correspond to the models skeleton for example:

*hu1 = humanoid01 - which are associated with male humans.

*hu1b = humanoid01b - which are associated with female humans and female elves.

*hu1c = humanoid01c - which are associated with norscan and chaos humans.

Etc, you'll quickly become familiar with these while modding.

===Camera Controls===
While in the visual work space you can navigate the 3d area by placing your mouse cursor within the window and using the following:

*Holding down Alt + Left Mouse Button (LMB) will move the camera around a fixed point.

*Holding down Alt + Scrolling the Mouse Wheel up will zoom in towards the fixed point and scrolling it back will zoom out.

*Holding down Alt + Right Mouse Button (RMB) will allow you to reposition the fixed point.

===Saving a Model===
To save your freshly acquired model to your packfile navigate to the tool bar at the top of the screen and hit the save icon (Ctrl+S) at which point you will see the model appear under your packfile in the file browser marked in red which means that you have saved the models current state but this does not save your packfile and closing the program before doing so will delete any work you have done up to this point.

If you are working with multiple packfiles at the same time you must switch to the correct packfile before saving your models or they will save in the wrong place, to do this right click an inactive pack in the file browser and select Set as Editable Pack.

===Saving a Packfile===
To save your packfile navigate to the file browser and right click your packfiles name, select Save or Save As and select a location for your file then hit save again, your packfile is now saved and it is safe to close the program.[[File:SavePackfile.png|thumb|alt=|none]]

== Sub Tools==

=== Kitbash Editor===
Select a .rmv2 file to open the Kitbash Editor

Find your self a model to play with. Go to:

variantmeshes/

wh_variantmodels/

There is folders named after skeletons. hu1 is for humans.

In hu1 you have files for each factions that use it.

Look for a file that ends with .rigid_model_V2

Ignore the .wsmodels for now

Youtube tutorial: https://www.youtube.com/watch?v=LeObDGqV2PM

====Re-Regging====
One of the key parts of the Kitbash editor is the ability to re-rig a mesh from one skeleton to an other. If this is not done, the mesh will turn into spaghetti when an animation is applied.

It works by doing a 1:1 mapping between bones in the original skeleton (left side) and the target skeleton (right side)

It works by selecting bones one by one on the left side and then selecting a bone on the right side. When this is done the column on the left side that says -1 should turn into the same the bone selected on the right side.

The tool can also attempt to auto fit the mesh onto the skeleton by selecting the "Fit mesh to skeleton" checkbox.

[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb|Bone selected and mapped correctly]]
[[File:Remapping.png|none|thumb|Old and messy tutorial]]

====BMI tool====
The BMI editor allows the scaling of a mesh along its normals. This gives the impression of adding or removing thickness to and object.

All the bones that are selected in the tree view is applied to the scale when the apply button is pressed.[[File:BmiTool before.png|none|thumb|Before]]
[[File:BmiTool After.png|none|thumb|After]]

===Mount Animation Creator===
The tool also allows for attaching an animation to a vertex on an other skeleton. This is useful for creating mount animations for mount that does not exist in the game.

An example of this would be adding a Squig mound to Karl Franze or a Lion animation to the High Elf Princess. https://www.youtube.com/watch?v=4dKFXAu4R1Y

'''Excellent, must read tutorial for how to use the tool''': https://docs.google.com/document/d/123LZH16sY2EGRJWwTH4T3XvT0ENUUQXLLfL6tVUtezk/edit

A run-through of the UI components:

#Information about the rider and mount (mesh, skeleton and animation)
#Control how the rider is attached to the mount
#*Rider root bone (probably never change this)
#*Leg animation (disabled for now)
#*The vertex the rider is attached to. Select the mount, press F3 then select the vertex that the rider should be select to and press Set. The first selected vertex is used if multiple vertexes are selected
#Settings for the animation - Hopefully pretty intuitive
#Rider and mount animation fragment and active slots
#*Mount is the animation fragment used by the mount
#*Rider is the animation fragment used by the rider
#*Mount animation tag is the animation used by the mount
#Save and Preview:
#*Update the preview to reflect changes done in the animation settings view
#*Active fragment to add items to
#*Slot in the active fragment to add to
#*Batch process based on the values in "Mount link shortcut view"
#Drawing related things
[[File:Mount tool defaultworkflow.png|none|thumb|Screenshot]]
[[File:Image2.png|none|thumb|Selecting vertex]]

====Workflow====
#Select rider and mount meshes
#Select attachment point
#Select rider and mount fragment
#Play around with the settings until you are happy with how it looks
#Press Batch prosess to generate animpack, bin and fragment.
#Look at the report to see if manual tweaks are needed.
#If manual tweaks are needed:
##Load the new fragment into "selected fragment"
##Find a slot that needs to be fixed.
##Select the correct Mount tag for the selected rider slot
##Select a rider tag that looks good
##Press add to fragment
##Repeat
[[File:Mount tool defaultworkflow fixstuff.png|none|thumb]]

====Sliding====
If the rider is sliding around or popping, make sure that the scale of the mount is correct.

====Matched animations====
Matched animations does not work well right now, I recommend deleting them.

===Anm.Meta files Editor===
The tool can display and edit most meta file, more information will be added later[[File:ImageMeta.png|none|thumb]]

=== AnimPack Editor ===
The tool comes with an animation pack editor. The animpack is the file which controls how animations are configured.

Refer to the "animation and you" tutorial for more information about how they are structured

[[File:Images.png|alt=|1226x1226px]]

==== How to create a new fragment (animation set) for a unit ====

Go to '''File -> Create -> New AnimPack(game''') and enter a name when prompted. This gives you a very basic example of how the file works. For more information I recommend looking into the existing game animpack

By default the tool creates a placeholder bin entry[[File:CustomAnimPack.png|left|alt=|1373x1373px]]

Create a new fragment by going to '''File->New AnimationSet(Game)''' inside the animpack editor. This gives you the fragment where the animation information about the unit is stored

Edit the bin to to be sensible values. Best way to do this is by copying a bin which is the closest to what you want to do. In this case it was the "hu2_orc_2handed_axe" entry and then I replaced the "hu2_orc_2handed_axe" names with the new name of the fragment.

'''Save the bin.'''

[[File:BinValues.png|alt=|1376x1376px]]

Go the the frag, it contains some example data. Replace it with the data you want. Typically this means copy pasting in the fragment the closest to what you want, then updating it. In this case it was the "hu2_orc_2handed_axe" and I updated some of the meta files to use the new files I have created (Note, the files on the left in the tree view has not yet been renamed!)

'''Save the frg, then save the animpack by going to File->Save'''
[[File:EditAndSaveFrg.png|thumb|alt=|none|1375x1375px]]Now your animpack is done, but you need to link it to a unit. Dindi has kindly created an example animpack for how to do this!
[[File:Anim db example.pack|none|thumb]]

Tutorial:AssetEditor

2022-01-15T11:51:01Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

'''Download link''': https://github.com/olekristianhomelien/TheAssetEditor/releases/latest

'''Youtube tutorials:''' https://www.youtube.com/channel/UCXnf2q9fRNYlMn4XULPLKgg

'''Beginner tutorial by FaallenOon:''' [https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw/edit https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw]

'''Disclaimer''': I am not good at technical writing or enjoy it, so if someone feels the desire to improve this, then please!

==The Basics==

===Creating a New Packfile===
To create a new packfile go to the top left corner of the program and click file then select New Packfile and a window will open asking you to enter a name, once you have entered a name press ok and your packfile will be created in the file browser to the left and will be marked as active which is identified by '''bold''' text.

===Opening a Model ===
To get started working with models navigate to the file browser on the left and open the All CA Packs folder, scroll down to variantmeshes, into wh_variantmodels and browse through the list for a model of your choosing and once you have found the model that you seek you can double click upon the rigid_model_v2 file to open the model within the 3d viewer.

====How to find a Model====
If you have an idea of what kind of model you are looking for you can use the Search Filter box at the top of the file browser to try and narrow down the amount of folders you need to search through but if you do not then you can take a rough guess at where models are located by the folder names which correspond to the models skeleton for example:

*hu1 = humanoid01 - which are associated with male humans.

*hu1b = humanoid01b - which are associated with female humans and female elves.

*hu1c = humanoid01c - which are associated with norscan and chaos humans.

Etc, you'll quickly become familiar with these while modding.

===Camera Controls===
While in the visual work space you can navigate the 3d area by placing your mouse cursor within the window and using the following:

*Holding down Alt + Left Mouse Button (LMB) will move the camera around a fixed point.

*Holding down Alt + Scrolling the Mouse Wheel up will zoom in towards the fixed point and scrolling it back will zoom out.

*Holding down Alt + Right Mouse Button (RMB) will allow you to reposition the fixed point.

===Saving a Model===
To save your freshly acquired model to your packfile navigate to the tool bar at the top of the screen and hit the save icon (Ctrl+S) at which point you will see the model appear under your packfile in the file browser marked in red which means that you have saved the models current state but this does not save your packfile and closing the program before doing so will delete any work you have done up to this point.

If you are working with multiple packfiles at the same time you must switch to the correct packfile before saving your models or they will save in the wrong place, to do this right click an inactive pack in the file browser and select Set as Editable Pack.

===Saving a Packfile===
To save your packfile navigate to the file browser and right click your packfiles name, select Save or Save As and select a location for your file then hit save again, your packfile is now saved and it is safe to close the program.[[File:SavePackfile.png|thumb|alt=|none]]

== Sub Tools==

=== Kitbash Editor===
Select a .rmv2 file to open the Kitbash Editor

Find your self a model to play with. Go to:

variantmeshes/

wh_variantmodels/

There is folders named after skeletons. hu1 is for humans.

In hu1 you have files for each factions that use it.

Look for a file that ends with .rigid_model_V2

Ignore the .wsmodels for now

Youtube tutorial: https://www.youtube.com/watch?v=LeObDGqV2PM

====Re-Regging====
One of the key parts of the Kitbash editor is the ability to re-rig a mesh from one skeleton to an other. If this is not done, the mesh will turn into spaghetti when an animation is applied.

It works by doing a 1:1 mapping between bones in the original skeleton (left side) and the target skeleton (right side)

It works by selecting bones one by one on the left side and then selecting a bone on the right side. When this is done the column on the left side that says -1 should turn into the same the bone selected on the right side.

The tool can also attempt to auto fit the mesh onto the skeleton by selecting the "Fit mesh to skeleton" checkbox.

[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb|Bone selected and mapped correctly]]
[[File:Remapping.png|none|thumb|Old and messy tutorial]]

====BMI tool====
The BMI editor allows the scaling of a mesh along its normals. This gives the impression of adding or removing thickness to and object.

All the bones that are selected in the tree view is applied to the scale when the apply button is pressed.[[File:BmiTool before.png|none|thumb|Before]]
[[File:BmiTool After.png|none|thumb|After]]

===Mount Animation Creator===
The tool also allows for attaching an animation to a vertex on an other skeleton. This is useful for creating mount animations for mount that does not exist in the game.

An example of this would be adding a Squig mound to Karl Franze or a Lion animation to the High Elf Princess. https://www.youtube.com/watch?v=4dKFXAu4R1Y

'''Excellent, must read tutorial for how to use the tool''': https://docs.google.com/document/d/123LZH16sY2EGRJWwTH4T3XvT0ENUUQXLLfL6tVUtezk/edit

A run-through of the UI components:

#Information about the rider and mount (mesh, skeleton and animation)
#Control how the rider is attached to the mount
#*Rider root bone (probably never change this)
#*Leg animation (disabled for now)
#*The vertex the rider is attached to. Select the mount, press F3 then select the vertex that the rider should be select to and press Set. The first selected vertex is used if multiple vertexes are selected
#Settings for the animation - Hopefully pretty intuitive
#Rider and mount animation fragment and active slots
#*Mount is the animation fragment used by the mount
#*Rider is the animation fragment used by the rider
#*Mount animation tag is the animation used by the mount
#Save and Preview:
#*Update the preview to reflect changes done in the animation settings view
#*Active fragment to add items to
#*Slot in the active fragment to add to
#*Batch process based on the values in "Mount link shortcut view"
#Drawing related things
[[File:Mount tool defaultworkflow.png|none|thumb|Screenshot]]
[[File:Image2.png|none|thumb|Selecting vertex]]

====Workflow====
#Select rider and mount meshes
#Select attachment point
#Select rider and mount fragment
#Play around with the settings until you are happy with how it looks
#Press Batch prosess to generate animpack, bin and fragment.
#Look at the report to see if manual tweaks are needed.
#If manual tweaks are needed:
##Load the new fragment into "selected fragment"
##Find a slot that needs to be fixed.
##Select the correct Mount tag for the selected rider slot
##Select a rider tag that looks good
##Press add to fragment
##Repeat
[[File:Mount tool defaultworkflow fixstuff.png|none|thumb]]

====Sliding====
If the rider is sliding around or popping, make sure that the scale of the mount is correct.

====Matched animations====
Matched animations does not work well right now, I recommend deleting them.

===Anm.Meta files Editor===
The tool can display and edit most meta file, more information will be added later[[File:ImageMeta.png|none|thumb]]

=== AnimPack Editor ===
The tool comes with an animation pack editor. The animpack is the file which controls how animations are configured.

Refer to the "animation and you" tutorial for more information about how they are structured

[[File:Images.png|alt=|1226x1226px]]

==== How to create a new fragment (animation set) for a unit ====

Go to '''File -> Create -> New AnimPack(game''') and enter a name when prompted. This gives you a very basic example of how the file works. For more information I recommend looking into the existing game animpack

By default the tool creates a placeholder bin entry[[File:CustomAnimPack.png|left|alt=|1373x1373px]]

Create a new fragment by going to '''File->New AnimationSet(Game)''' inside the animpack editor. This gives you the fragment where the animation information about the unit is stored

Edit the bin to to be sensible values. Best way to do this is by copying a bin which is the closest to what you want to do. In this case it was the "hu2_orc_2handed_axe" entry and then I replaced the "hu2_orc_2handed_axe" names with the new name of the fragment.

'''Save the bin.'''

[[File:BinValues.png|alt=|1376x1376px]]

Go the the frag, it contains some example data. Replace it with the data you want. Typically this means copy pasting in the fragment the closest to what you want, then updating it. In this case it was the "hu2_orc_2handed_axe" and I updated some of the meta files to use the new files I have created (Note, the files on the left in the tree view has not yet been renamed!)

'''Save the frg, then save the animpack by going to File->Save'''
[[File:EditAndSaveFrg.png|thumb|alt=|none|1375x1375px]]Now your animpack is done, but you need to link it to a unit. Dindi has kindly created an example animpack for how to do this!
[[File:Anim db example.pack|none|thumb]]

Tutorial:AssetEditor

2022-01-15T11:50:28Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

'''Download link''': https://github.com/olekristianhomelien/TheAssetEditor/releases/latest

'''Youtube tutorials:''' https://www.youtube.com/channel/UCXnf2q9fRNYlMn4XULPLKgg

'''Beginner tutorial by FaallenOon:''' [https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw/edit https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw]

'''Disclaimer''': I am not good at technical writing or enjoy it, so if someone feels the desire to improve this, then please!

==The Basics==

===Creating a New Packfile===
To create a new packfile go to the top left corner of the program and click file then select New Packfile and a window will open asking you to enter a name, once you have entered a name press ok and your packfile will be created in the file browser to the left and will be marked as active which is identified by '''bold''' text.

===Opening a Model ===
To get started working with models navigate to the file browser on the left and open the All CA Packs folder, scroll down to variantmeshes, into wh_variantmodels and browse through the list for a model of your choosing and once you have found the model that you seek you can double click upon the rigid_model_v2 file to open the model within the 3d viewer.

====How to find a Model====
If you have an idea of what kind of model you are looking for you can use the Search Filter box at the top of the file browser to try and narrow down the amount of folders you need to search through but if you do not then you can take a rough guess at where models are located by the folder names which correspond to the models skeleton for example:

*hu1 = humanoid01 - which are associated with male humans.

*hu1b = humanoid01b - which are associated with female humans and female elves.

*hu1c = humanoid01c - which are associated with norscan and chaos humans.

Etc, you'll quickly become familiar with these while modding.

===Camera Controls===
While in the visual work space you can navigate the 3d area by placing your mouse cursor within the window and using the following:

*Holding down Alt + Left Mouse Button (LMB) will move the camera around a fixed point.

*Holding down Alt + Scrolling the Mouse Wheel up will zoom in towards the fixed point and scrolling it back will zoom out.

*Holding down Alt + Right Mouse Button (RMB) will allow you to reposition the fixed point.

===Saving a Model===
To save your freshly acquired model to your packfile navigate to the tool bar at the top of the screen and hit the save icon (Ctrl+S) at which point you will see the model appear under your packfile in the file browser marked in red which means that you have saved the models current state but this does not save your packfile and closing the program before doing so will delete any work you have done up to this point.

If you are working with multiple packfiles at the same time you must switch to the correct packfile before saving your models or they will save in the wrong place, to do this right click an inactive pack in the file browser and select Set as Editable Pack.

===Saving a Packfile===
To save your packfile navigate to the file browser and right click your packfiles name, select Save or Save As and select a location for your file then hit save again, your packfile is now saved and it is safe to close the program.[[File:SavePackfile.png|thumb|alt=|none]]

== Sub Tools==

=== Kitbash Editor===
Select a .rmv2 file to open the Kitbash Editor

Find your self a model to play with. Go to:

variantmeshes/

wh_variantmodels/

There is folders named after skeletons. hu1 is for humans.

In hu1 you have files for each factions that use it.

Look for a file that ends with .rigid_model_V2

Ignore the .wsmodels for now

Youtube tutorial: https://www.youtube.com/watch?v=LeObDGqV2PM

====Re-Regging====
One of the key parts of the Kitbash editor is the ability to re-rig a mesh from one skeleton to an other. If this is not done, the mesh will turn into spaghetti when an animation is applied.

It works by doing a 1:1 mapping between bones in the original skeleton (left side) and the target skeleton (right side)

It works by selecting bones one by one on the left side and then selecting a bone on the right side. When this is done the column on the left side that says -1 should turn into the same the bone selected on the right side.

The tool can also attempt to auto fit the mesh onto the skeleton by selecting the "Fit mesh to skeleton" checkbox.

[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb|Bone selected and mapped correctly]]
[[File:Remapping.png|none|thumb|Old and messy tutorial]]

====BMI tool====
The BMI editor allows the scaling of a mesh along its normals. This gives the impression of adding or removing thickness to and object.

All the bones that are selected in the tree view is applied to the scale when the apply button is pressed.[[File:BmiTool before.png|none|thumb|Before]]
[[File:BmiTool After.png|none|thumb|After]]

===Mount Animation Creator===
The tool also allows for attaching an animation to a vertex on an other skeleton. This is useful for creating mount animations for mount that does not exist in the game.

An example of this would be adding a Squig mound to Karl Franze or a Lion animation to the High Elf Princess. https://www.youtube.com/watch?v=4dKFXAu4R1Y

'''Excellent, must read tutorial for how to use the tool''': https://docs.google.com/document/d/123LZH16sY2EGRJWwTH4T3XvT0ENUUQXLLfL6tVUtezk/edit

A run-through of the UI components:

#Information about the rider and mount (mesh, skeleton and animation)
#Control how the rider is attached to the mount
#*Rider root bone (probably never change this)
#*Leg animation (disabled for now)
#*The vertex the rider is attached to. Select the mount, press F3 then select the vertex that the rider should be select to and press Set. The first selected vertex is used if multiple vertexes are selected
#Settings for the animation - Hopefully pretty intuitive
#Rider and mount animation fragment and active slots
#*Mount is the animation fragment used by the mount
#*Rider is the animation fragment used by the rider
#*Mount animation tag is the animation used by the mount
#Save and Preview:
#*Update the preview to reflect changes done in the animation settings view
#*Active fragment to add items to
#*Slot in the active fragment to add to
#*Batch process based on the values in "Mount link shortcut view"
#Drawing related things
[[File:Mount tool defaultworkflow.png|none|thumb|Screenshot]]
[[File:Image2.png|none|thumb|Selecting vertex]]

====Workflow====
#Select rider and mount meshes
#Select attachment point
#Select rider and mount fragment
#Play around with the settings until you are happy with how it looks
#Press Batch prosess to generate animpack, bin and fragment.
#Look at the report to see if manual tweaks are needed.
#If manual tweaks are needed:
##Load the new fragment into "selected fragment"
##Find a slot that needs to be fixed.
##Select the correct Mount tag for the selected rider slot
##Select a rider tag that looks good
##Press add to fragment
##Repeat
[[File:Mount tool defaultworkflow fixstuff.png|none|thumb]]

====Sliding====
If the rider is sliding around or popping, make sure that the scale of the mount is correct.

====Matched animations====
Matched animations does not work well right now, I recommend deleting them.

===Anm.Meta files Editor===
The tool can display and edit most meta file, more information will be added later[[File:ImageMeta.png|none|thumb]]

=== AnimPack Editor ===
The tool comes with an animation pack editor. The animpack is the file which controls how animations are configured.

Refer to the "animation and you" tutorial for more information about how they are structured

[[File:Images.png|alt=|1226x1226px]]

==== How to create a new fragment (animation set) for a unit ====

Go to '''File -> Create -> New AnimPack(game''') and enter a name when prompted. This gives you a very basic example of how the file works. For more information I recommend looking into the existing game animpack

By default the tool creates a placeholder bin entry[[File:CustomAnimPack.png|left|alt=|1373x1373px]]

Create a new fragment by going to '''File->New AnimationSet(Game)''' inside the animpack editor. This gives you the fragment where the animation information about the unit is stored

Edit the bin to to be sensible values. Best way to do this is by copying a bin which is the closest to what you want to do. In this case it was the "hu2_orc_2handed_axe" entry and then I replaced the "hu2_orc_2handed_axe" names with the new name of the fragment.

'''Save the bin.'''

[[File:BinValues.png|alt=|1376x1376px]]

Go the the frag, it contains some example data. Replace it with the data you want. Typically this means copy pasting in the fragment the closest to what you want, then updating it. In this case it was the "hu2_orc_2handed_axe" and I updated some of the meta files to use the new files I have created (Note, the files on the left in the tree view has not yet been renamed!)

'''Save the frg, then save the animpack by going to File->Save'''
[[File:EditAndSaveFrg.png|thumb|alt=|none|1375x1375px]]Now your animpack is done, but you need to link it to a unit. Dindi has kindly created an example animpack for how to do this!
[[File:Anim db example.pack|none|thumb]]

Tutorial:AssetEditor

2022-01-14T20:31:49Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

'''Download link''': https://github.com/olekristianhomelien/TheAssetEditor/releases/latest

'''Youtube tutorials:''' https://www.youtube.com/channel/UCXnf2q9fRNYlMn4XULPLKgg

'''Beginner tutorial by FaallenOon:''' [https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw/edit https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw]

'''Disclaimer''': I am not good at technical writing or enjoy it, so if someone feels the desire to improve this, then please!

==The Basics==

===Creating a New Packfile===
To create a new packfile go to the top left corner of the program and click file then select New Packfile and a window will open asking you to enter a name, once you have entered a name press ok and your packfile will be created in the file browser to the left and will be marked as active which is identified by '''bold''' text.

===Opening a Model ===
To get started working with models navigate to the file browser on the left and open the All CA Packs folder, scroll down to variantmeshes, into wh_variantmodels and browse through the list for a model of your choosing and once you have found the model that you seek you can double click upon the rigid_model_v2 file to open the model within the 3d viewer.

====How to find a Model====
If you have an idea of what kind of model you are looking for you can use the Search Filter box at the top of the file browser to try and narrow down the amount of folders you need to search through but if you do not then you can take a rough guess at where models are located by the folder names which correspond to the models skeleton for example:

*hu1 = humanoid01 - which are associated with male humans.

*hu1b = humanoid01b - which are associated with female humans and female elves.

*hu1c = humanoid01c - which are associated with norscan and chaos humans.

Etc, you'll quickly become familiar with these while modding.

===Camera Controls===
While in the visual work space you can navigate the 3d area by placing your mouse cursor within the window and using the following:

*Holding down Alt + Left Mouse Button (LMB) will move the camera around a fixed point.

*Holding down Alt + Scrolling the Mouse Wheel up will zoom in towards the fixed point and scrolling it back will zoom out.

*Holding down Alt + Right Mouse Button (RMB) will allow you to reposition the fixed point.

===Saving a Model===
To save your freshly acquired model to your packfile navigate to the tool bar at the top of the screen and hit the save icon (Ctrl+S) at which point you will see the model appear under your packfile in the file browser marked in red which means that you have saved the models current state but this does not save your packfile and closing the program before doing so will delete any work you have done up to this point.

If you are working with multiple packfiles at the same time you must switch to the correct packfile before saving your models or they will save in the wrong place, to do this right click an inactive pack in the file browser and select Set as Editable Pack.

===Saving a Packfile===
To save your packfile navigate to the file browser and right click your packfiles name, select Save or Save As and select a location for your file then hit save again, your packfile is now saved and it is safe to close the program.[[File:SavePackfile.png|thumb|alt=|none]]

== Sub Tools==

=== Kitbash Editor===
Select a .rmv2 file to open the Kitbash Editor

Find your self a model to play with. Go to:

variantmeshes/

wh_variantmodels/

There is folders named after skeletons. hu1 is for humans.

In hu1 you have files for each factions that use it.

Look for a file that ends with .rigid_model_V2

Ignore the .wsmodels for now

Youtube tutorial: https://www.youtube.com/watch?v=LeObDGqV2PM

====Re-Regging====
One of the key parts of the Kitbash editor is the ability to re-rig a mesh from one skeleton to an other. If this is not done, the mesh will turn into spaghetti when an animation is applied.

It works by doing a 1:1 mapping between bones in the original skeleton (left side) and the target skeleton (right side)

It works by selecting bones one by one on the left side and then selecting a bone on the right side. When this is done the column on the left side that says -1 should turn into the same the bone selected on the right side.

The tool can also attempt to auto fit the mesh onto the skeleton by selecting the "Fit mesh to skeleton" checkbox.

[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb|Bone selected and mapped correctly]]
[[File:Remapping.png|none|thumb|Old and messy tutorial]]

====BMI tool====
The BMI editor allows the scaling of a mesh along its normals. This gives the impression of adding or removing thickness to and object.

All the bones that are selected in the tree view is applied to the scale when the apply button is pressed.[[File:BmiTool before.png|none|thumb|Before]]
[[File:BmiTool After.png|none|thumb|After]]

===Mount Animation Creator===
The tool also allows for attaching an animation to a vertex on an other skeleton. This is useful for creating mount animations for mount that does not exist in the game.

An example of this would be adding a Squig mound to Karl Franze or a Lion animation to the High Elf Princess. https://www.youtube.com/watch?v=4dKFXAu4R1Y

'''Excellent, must read tutorial for how to use the tool''': https://docs.google.com/document/d/123LZH16sY2EGRJWwTH4T3XvT0ENUUQXLLfL6tVUtezk/edit

A run-through of the UI components:

#Information about the rider and mount (mesh, skeleton and animation)
#Control how the rider is attached to the mount
#*Rider root bone (probably never change this)
#*Leg animation (disabled for now)
#*The vertex the rider is attached to. Select the mount, press F3 then select the vertex that the rider should be select to and press Set. The first selected vertex is used if multiple vertexes are selected
#Settings for the animation - Hopefully pretty intuitive
#Rider and mount animation fragment and active slots
#*Mount is the animation fragment used by the mount
#*Rider is the animation fragment used by the rider
#*Mount animation tag is the animation used by the mount
#Save and Preview:
#*Update the preview to reflect changes done in the animation settings view
#*Active fragment to add items to
#*Slot in the active fragment to add to
#*Batch process based on the values in "Mount link shortcut view"
#Drawing related things
[[File:Mount tool defaultworkflow.png|none|thumb|Screenshot]]
[[File:Image2.png|none|thumb|Selecting vertex]]

====Workflow====
#Select rider and mount meshes
#Select attachment point
#Select rider and mount fragment
#Play around with the settings until you are happy with how it looks
#Press Batch prosess to generate animpack, bin and fragment.
#Look at the report to see if manual tweaks are needed.
#If manual tweaks are needed:
##Load the new fragment into "selected fragment"
##Find a slot that needs to be fixed.
##Select the correct Mount tag for the selected rider slot
##Select a rider tag that looks good
##Press add to fragment
##Repeat
[[File:Mount tool defaultworkflow fixstuff.png|none|thumb]]

====Sliding====
If the rider is sliding around or popping, make sure that the scale of the mount is correct.

====Matched animations====
Matched animations does not work well right now, I recommend deleting them.

===Anm.Meta files Editor===
The tool can display and edit most meta file, more information will be added later[[File:ImageMeta.png|none|thumb]]

=== AnimPack Editor ===
The tool comes with an animation pack editor. The animpack is the file which controls how animations are configured.

Refer to the "animation and you" tutorial for more information about how they are structured

[[File:Images.png|alt=|1226x1226px]]

==== How to create a new fragment (animation set) for a unit ====

Go to File -> Create -> New AnimPack(game) and enter a name when prompted. This gives you a very basic example of how the file works. For more information I recommend looking into the existing game animpack

By default the tool creates a placeholder bin entry[[File:CustomAnimPack.png|left|alt=|1373x1373px]]

Create a new fragment by going to File->New AnimationSet(Game). This gives you the fragment where the animation information about the unit is stored

Edit the bin to to be sensible values. Best way to do this is by copying a bin which is the closest to what you want to do. In this case it was the "hu2_orc_2handed_axe" entry and then I replaced the "hu2_orc_2handed_axe" names with the new name.

Save the bin.

[[File:BinValues.png|alt=|1376x1376px]]

Go the the frag, it contains some example data. Replace it with the data you want. Typically this means copy pasting in the fragment the closest to what you want, then updating it. In this case it was the "hu2_orc_2handed_axe" and I updated some of the meta files to use the new files I have created (Note, the files on the left in the tree view has not yet been renamed!)

Save the frg, then save the animpack by going to File->Save
[[File:EditAndSaveFrg.png|thumb|alt=|none|1375x1375px]]Now your animpack is done, but you need to link it to a unit. Dindi has kindly created an example animpack for how to do this!
[[File:Anim db example.pack|none|thumb]]

File:Anim db example.pack

2022-01-14T20:30:58Z

H3ro:

Tutorial:AssetEditor

2022-01-14T20:30:16Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

'''Download link''': https://github.com/olekristianhomelien/TheAssetEditor/releases/latest

'''Youtube tutorials:''' https://www.youtube.com/channel/UCXnf2q9fRNYlMn4XULPLKgg

'''Beginner tutorial by FaallenOon:''' [https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw/edit https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw]

'''Disclaimer''': I am not good at technical writing or enjoy it, so if someone feels the desire to improve this, then please!

==The Basics==

===Creating a New Packfile===
To create a new packfile go to the top left corner of the program and click file then select New Packfile and a window will open asking you to enter a name, once you have entered a name press ok and your packfile will be created in the file browser to the left and will be marked as active which is identified by '''bold''' text.

===Opening a Model ===
To get started working with models navigate to the file browser on the left and open the All CA Packs folder, scroll down to variantmeshes, into wh_variantmodels and browse through the list for a model of your choosing and once you have found the model that you seek you can double click upon the rigid_model_v2 file to open the model within the 3d viewer.

====How to find a Model====
If you have an idea of what kind of model you are looking for you can use the Search Filter box at the top of the file browser to try and narrow down the amount of folders you need to search through but if you do not then you can take a rough guess at where models are located by the folder names which correspond to the models skeleton for example:

*hu1 = humanoid01 - which are associated with male humans.

*hu1b = humanoid01b - which are associated with female humans and female elves.

*hu1c = humanoid01c - which are associated with norscan and chaos humans.

Etc, you'll quickly become familiar with these while modding.

===Camera Controls===
While in the visual work space you can navigate the 3d area by placing your mouse cursor within the window and using the following:

*Holding down Alt + Left Mouse Button (LMB) will move the camera around a fixed point.

*Holding down Alt + Scrolling the Mouse Wheel up will zoom in towards the fixed point and scrolling it back will zoom out.

*Holding down Alt + Right Mouse Button (RMB) will allow you to reposition the fixed point.

===Saving a Model===
To save your freshly acquired model to your packfile navigate to the tool bar at the top of the screen and hit the save icon (Ctrl+S) at which point you will see the model appear under your packfile in the file browser marked in red which means that you have saved the models current state but this does not save your packfile and closing the program before doing so will delete any work you have done up to this point.

If you are working with multiple packfiles at the same time you must switch to the correct packfile before saving your models or they will save in the wrong place, to do this right click an inactive pack in the file browser and select Set as Editable Pack.

===Saving a Packfile===
To save your packfile navigate to the file browser and right click your packfiles name, select Save or Save As and select a location for your file then hit save again, your packfile is now saved and it is safe to close the program.[[File:SavePackfile.png|thumb|alt=|none]]

== Sub Tools==

=== Kitbash Editor===
Select a .rmv2 file to open the Kitbash Editor

Find your self a model to play with. Go to:

variantmeshes/

wh_variantmodels/

There is folders named after skeletons. hu1 is for humans.

In hu1 you have files for each factions that use it.

Look for a file that ends with .rigid_model_V2

Ignore the .wsmodels for now

Youtube tutorial: https://www.youtube.com/watch?v=LeObDGqV2PM

====Re-Regging====
One of the key parts of the Kitbash editor is the ability to re-rig a mesh from one skeleton to an other. If this is not done, the mesh will turn into spaghetti when an animation is applied.

It works by doing a 1:1 mapping between bones in the original skeleton (left side) and the target skeleton (right side)

It works by selecting bones one by one on the left side and then selecting a bone on the right side. When this is done the column on the left side that says -1 should turn into the same the bone selected on the right side.

The tool can also attempt to auto fit the mesh onto the skeleton by selecting the "Fit mesh to skeleton" checkbox.

[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb|Bone selected and mapped correctly]]
[[File:Remapping.png|none|thumb|Old and messy tutorial]]

====BMI tool====
The BMI editor allows the scaling of a mesh along its normals. This gives the impression of adding or removing thickness to and object.

All the bones that are selected in the tree view is applied to the scale when the apply button is pressed.[[File:BmiTool before.png|none|thumb|Before]]
[[File:BmiTool After.png|none|thumb|After]]

===Mount Animation Creator===
The tool also allows for attaching an animation to a vertex on an other skeleton. This is useful for creating mount animations for mount that does not exist in the game.

An example of this would be adding a Squig mound to Karl Franze or a Lion animation to the High Elf Princess. https://www.youtube.com/watch?v=4dKFXAu4R1Y

'''Excellent, must read tutorial for how to use the tool''': https://docs.google.com/document/d/123LZH16sY2EGRJWwTH4T3XvT0ENUUQXLLfL6tVUtezk/edit

A run-through of the UI components:

#Information about the rider and mount (mesh, skeleton and animation)
#Control how the rider is attached to the mount
#*Rider root bone (probably never change this)
#*Leg animation (disabled for now)
#*The vertex the rider is attached to. Select the mount, press F3 then select the vertex that the rider should be select to and press Set. The first selected vertex is used if multiple vertexes are selected
#Settings for the animation - Hopefully pretty intuitive
#Rider and mount animation fragment and active slots
#*Mount is the animation fragment used by the mount
#*Rider is the animation fragment used by the rider
#*Mount animation tag is the animation used by the mount
#Save and Preview:
#*Update the preview to reflect changes done in the animation settings view
#*Active fragment to add items to
#*Slot in the active fragment to add to
#*Batch process based on the values in "Mount link shortcut view"
#Drawing related things
[[File:Mount tool defaultworkflow.png|none|thumb|Screenshot]]
[[File:Image2.png|none|thumb|Selecting vertex]]

====Workflow====
#Select rider and mount meshes
#Select attachment point
#Select rider and mount fragment
#Play around with the settings until you are happy with how it looks
#Press Batch prosess to generate animpack, bin and fragment.
#Look at the report to see if manual tweaks are needed.
#If manual tweaks are needed:
##Load the new fragment into "selected fragment"
##Find a slot that needs to be fixed.
##Select the correct Mount tag for the selected rider slot
##Select a rider tag that looks good
##Press add to fragment
##Repeat
[[File:Mount tool defaultworkflow fixstuff.png|none|thumb]]

====Sliding====
If the rider is sliding around or popping, make sure that the scale of the mount is correct.

====Matched animations====
Matched animations does not work well right now, I recommend deleting them.

===Anm.Meta files Editor===
The tool can display and edit most meta file, more information will be added later[[File:ImageMeta.png|none|thumb]]

=== AnimPack Editor ===
The tool comes with an animation pack editor. The animpack is the file which controls how animations are configured.

Refer to the "animation and you" tutorial for more information about how they are structured

[[File:Images.png|alt=|1226x1226px]]

==== How to create a new fragment (animation set) for a unit ====

Go to File -> Create -> New AnimPack(game) and enter a name when prompted. This gives you a very basic example of how the file works. For more information I recommend looking into the existing game animpack

By default the tool creates a placeholder bin entry[[File:CustomAnimPack.png|left|alt=|1373x1373px]]

Create a new fragment by going to File->New AnimationSet(Game). This gives you the fragment where the animation information about the unit is stored

Edit the bin to to be sensible values. Best way to do this is by copying a bin which is the closest to what you want to do. In this case it was the "hu2_orc_2handed_axe" entry and then I replaced the "hu2_orc_2handed_axe" names with the new name.

Save the bin.

[[File:BinValues.png|alt=|1376x1376px]]

Go the the frag, it contains some example data. Replace it with the data you want. Typically this means copy pasting in the fragment the closest to what you want, then updating it. In this case it was the "hu2_orc_2handed_axe" and I updated some of the meta files to use the new files I have created (Note, the files on the left in the tree view has not yet been renamed!)

Save the frg, then save the animpack by going to File->Save
[[File:EditAndSaveFrg.png|thumb|alt=|none|1375x1375px]]Now your animpack is done, but you need to link it to a unit. Dindi has kindly created an example animpack for how to do this!

Tutorial:AssetEditor

2022-01-14T20:16:08Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

'''Download link''': https://github.com/olekristianhomelien/TheAssetEditor/releases/latest

'''Youtube tutorials:''' https://www.youtube.com/channel/UCXnf2q9fRNYlMn4XULPLKgg

'''Beginner tutorial by FaallenOon:''' [https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw/edit https://docs.google.com/document/d/1QZefJwJLvG_ny2MUMZZvvxV-4o2AAuSCmmiA-twAIXw]

'''Disclaimer''': I am not good at technical writing or enjoy it, so if someone feels the desire to improve this, then please!

==The Basics==

===Creating a New Packfile===
To create a new packfile go to the top left corner of the program and click file then select New Packfile and a window will open asking you to enter a name, once you have entered a name press ok and your packfile will be created in the file browser to the left and will be marked as active which is identified by '''bold''' text.

===Opening a Model ===
To get started working with models navigate to the file browser on the left and open the All CA Packs folder, scroll down to variantmeshes, into wh_variantmodels and browse through the list for a model of your choosing and once you have found the model that you seek you can double click upon the rigid_model_v2 file to open the model within the 3d viewer.

====How to find a Model====
If you have an idea of what kind of model you are looking for you can use the Search Filter box at the top of the file browser to try and narrow down the amount of folders you need to search through but if you do not then you can take a rough guess at where models are located by the folder names which correspond to the models skeleton for example:

*hu1 = humanoid01 - which are associated with male humans.

*hu1b = humanoid01b - which are associated with female humans and female elves.

*hu1c = humanoid01c - which are associated with norscan and chaos humans.

Etc, you'll quickly become familiar with these while modding.

===Camera Controls===
While in the visual work space you can navigate the 3d area by placing your mouse cursor within the window and using the following:

*Holding down Alt + Left Mouse Button (LMB) will move the camera around a fixed point.

*Holding down Alt + Scrolling the Mouse Wheel up will zoom in towards the fixed point and scrolling it back will zoom out.

*Holding down Alt + Right Mouse Button (RMB) will allow you to reposition the fixed point.

===Saving a Model===
To save your freshly acquired model to your packfile navigate to the tool bar at the top of the screen and hit the save icon (Ctrl+S) at which point you will see the model appear under your packfile in the file browser marked in red which means that you have saved the models current state but this does not save your packfile and closing the program before doing so will delete any work you have done up to this point.

If you are working with multiple packfiles at the same time you must switch to the correct packfile before saving your models or they will save in the wrong place, to do this right click an inactive pack in the file browser and select Set as Editable Pack.

===Saving a Packfile===
To save your packfile navigate to the file browser and right click your packfiles name, select Save or Save As and select a location for your file then hit save again, your packfile is now saved and it is safe to close the program.[[File:SavePackfile.png|thumb|alt=|none]]

== Sub Tools==

=== Kitbash Editor===
Select a .rmv2 file to open the Kitbash Editor

Find your self a model to play with. Go to:

variantmeshes/

wh_variantmodels/

There is folders named after skeletons. hu1 is for humans.

In hu1 you have files for each factions that use it.

Look for a file that ends with .rigid_model_V2

Ignore the .wsmodels for now

Youtube tutorial: https://www.youtube.com/watch?v=LeObDGqV2PM

====Re-Regging====
One of the key parts of the Kitbash editor is the ability to re-rig a mesh from one skeleton to an other. If this is not done, the mesh will turn into spaghetti when an animation is applied.

It works by doing a 1:1 mapping between bones in the original skeleton (left side) and the target skeleton (right side)

It works by selecting bones one by one on the left side and then selecting a bone on the right side. When this is done the column on the left side that says -1 should turn into the same the bone selected on the right side.

The tool can also attempt to auto fit the mesh onto the skeleton by selecting the "Fit mesh to skeleton" checkbox.

[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb|Bone selected and mapped correctly]]
[[File:Remapping.png|none|thumb|Old and messy tutorial]]

====BMI tool====
The BMI editor allows the scaling of a mesh along its normals. This gives the impression of adding or removing thickness to and object.

All the bones that are selected in the tree view is applied to the scale when the apply button is pressed.[[File:BmiTool before.png|none|thumb|Before]]
[[File:BmiTool After.png|none|thumb|After]]

===Mount Animation Creator===
The tool also allows for attaching an animation to a vertex on an other skeleton. This is useful for creating mount animations for mount that does not exist in the game.

An example of this would be adding a Squig mound to Karl Franze or a Lion animation to the High Elf Princess. https://www.youtube.com/watch?v=4dKFXAu4R1Y

'''Excellent, must read tutorial for how to use the tool''': https://docs.google.com/document/d/123LZH16sY2EGRJWwTH4T3XvT0ENUUQXLLfL6tVUtezk/edit

A run-through of the UI components:

#Information about the rider and mount (mesh, skeleton and animation)
#Control how the rider is attached to the mount
#*Rider root bone (probably never change this)
#*Leg animation (disabled for now)
#*The vertex the rider is attached to. Select the mount, press F3 then select the vertex that the rider should be select to and press Set. The first selected vertex is used if multiple vertexes are selected
#Settings for the animation - Hopefully pretty intuitive
#Rider and mount animation fragment and active slots
#*Mount is the animation fragment used by the mount
#*Rider is the animation fragment used by the rider
#*Mount animation tag is the animation used by the mount
#Save and Preview:
#*Update the preview to reflect changes done in the animation settings view
#*Active fragment to add items to
#*Slot in the active fragment to add to
#*Batch process based on the values in "Mount link shortcut view"
#Drawing related things
[[File:Mount tool defaultworkflow.png|none|thumb|Screenshot]]
[[File:Image2.png|none|thumb|Selecting vertex]]

====Workflow====
#Select rider and mount meshes
#Select attachment point
#Select rider and mount fragment
#Play around with the settings until you are happy with how it looks
#Press Batch prosess to generate animpack, bin and fragment.
#Look at the report to see if manual tweaks are needed.
#If manual tweaks are needed:
##Load the new fragment into "selected fragment"
##Find a slot that needs to be fixed.
##Select the correct Mount tag for the selected rider slot
##Select a rider tag that looks good
##Press add to fragment
##Repeat
[[File:Mount tool defaultworkflow fixstuff.png|none|thumb]]

====Sliding====
If the rider is sliding around or popping, make sure that the scale of the mount is correct.

====Matched animations====
Matched animations does not work well right now, I recommend deleting them.

===Anm.Meta files Editor===
The tool can display and edit most meta file, more information will be added later[[File:ImageMeta.png|none|thumb]]

=== AnimPack Editor ===
asddasd
[[File:Images.png|left|thumb]]

[[File:CustomAnimPack.png|left|thumb]]

[[File:BinValues.png|left|thumb]]

[[File:EditAndSaveFrg.png|left|thumb]]

File:EditAndSaveFrg.png

2022-01-14T20:15:29Z

H3ro:

asd

File:BinValues.png

2022-01-14T20:12:42Z

H3ro:

BinValues

File:CustomAnimPack.png

2022-01-14T20:08:57Z

H3ro:

File:Images.png

2022-01-14T20:07:22Z

H3ro:

Tutorial:AssetEditor

2021-08-27T20:30:24Z

H3ro:

Tutorial:AssetEditor

2021-08-27T20:29:52Z

H3ro:

Tutorial:AssetEditor

2021-08-23T11:23:31Z

H3ro:

Tutorial:AssetEditor

2021-08-23T11:22:42Z

H3ro:

Tutorial:Animation and You

2021-07-08T19:25:33Z

H3ro:

Animations in Total war controls a great deal, but its important to know that the game has no idea what an animation is. It depends on configuration and meta data to actually use it for anything apart from a visual display.

The game often works by stacking animations on top of each other. Such as walk + attack + close hands = moving attack.

Most animations can be view in AssetEditor or RME. The animation files can be edited in RPFM, and viewed (soon-ish edited) using AssetEditor
=== File types ===

==== Animpacks (.animpack) ====
The animation pack is the main file which acts like the container of the bin file and the fragments. This file can be edited using RPFM. To do so you must unpack the files inside of it and make sure that you repack them when done.

==== Bin (.bin) ====
The bin file contains the key that is used by the database and links that with a skeleton, and optional mount bin entry and a set of fragments. Most entries contains multiple fragments, where the fragments later in the list overrides Slots in earlier fragments.

==== Fragments (.frg) ====
The fragment files contains the actual capabilities of the animation set. This is where you link action with the visual animation.
[[File:RPFM frg view.png|none|thumb]]
The "Slot and Id" tells the game what action the animation should trigger for. If you try to use any capabilities without having the slot, it will often not work. For example adding a ranged attack without adding the correct Slots will result in the unit not being able to fire its weapon.

For each row there is also a meta file which can override how the animation looks, as well as add effects such as particles, camera shake, hit position, AOE, etc.

The row also contains a checkbox for which prop slots in the VMD should be visible.

==== Skeletons (.anim) ====

==== Animations (.anim) ====

==== Animation meta (.meta.anim) ====

=== Mounts ===
The game uses two different mount systems:

==== Attachment point mounts ====
The attachment system is used for two different things; Rider animations for units not really doing much (unit on top of a war mammoth which is just sitting there, no matter what is happening) and units with multiple riders which are attacking but not moving (Necrofex, war-wagon)

Attachment point mounts riders are officers

==== Synced animation mounts ====
The most common mount system is the one for synced animations. Both the rider and the mount must have the same slots. (Typically Attack_1 and Rider_attack_1) where both animations are synced to each other.

Tutorial:Animation and You

2021-07-08T18:55:33Z

H3ro:

Animations in Total war controls a great deal, but its important to know that the game has no idea what an animation is. It depends on configuration and meta data to actually use it for anything apart from a visual display.

The game often works by stacking animations on top of each other. Such as walk + attack + close hands = moving attack.

Most animations can be view in AssetEditor or RME. The animation files can be edited in RPFM, and viewed (soon-ish edited) using AssetEditor
=== File types ===

==== Animpacks (.animpack) ====
The animation pack is the main file which acts like the container of the bin file and the fragments. This file can be edited using RPFM. To do so you must unpack the files inside of it and make sure that you repack them when done.

==== Bin (.bin) ====
The bin file contains the key that is used by the database and links that with a skeleton, and optional mount bin entry and a set of fragments. Most entries contains multiple fragments, where the fragments later in the list overrides Slots in earlier fragments.

==== Fragments (.frg) ====
The fragment files contains the actual capabilities of the animation set. This is where you link action with the visual animation.
[[File:RPFM frg view.png|none|thumb]]
The "Slot and Id" tells the game what action the animation should trigger for. If you try to use any capabilities without having the slot, it will often not work. For example adding a ranged attack without adding the correct Slots will result in the unit not being able to fire its weapon.

For each row there is also a meta file which can override how the animation looks, as well as add effects such as particles, camera shake, hit position, AOE, etc.

The row also contains a checkbox for which prop slots in the VMD should be visible.

==== Skeletons (.anim) ====

==== Animations (.anim) ====

==== Animation meta (.meta.anim) ====

=== Mounts ===
The game uses two different mount systems:

==== Attachment point mounts ====
The attachment system is used for two different things; Rider animations for units not really doing much (unit on top of a war mammoth which is just sitting there, no matter what is happening) and units with multiple riders (Necrofex, war-wagon)

==== Synced animation mounts ====
The most common mount system is the one for synced animations. Both the rider and the mount must have the same slots. (Typically Attack_1 and Rider_attack_1) where both animations are synced to each other.

Tutorial:Animation and You

2021-07-08T17:29:50Z

H3ro:

Animations in Total war controls a great deal, but its important to know that the game has no idea what an animation is. It depends on configuration and meta data to actually use it for anything apart from a visual display.

The game often works by stacking animations on top of each other. Such as walk + attack + close hands.

Most animations can be view in AssetEditor or RME. The animation files can be edited in RPFM, and viewed (soon-ish edited) using AssetEditor
=== File types ===

==== Animpacks (.animpack) ====
The animation pack is the main file which acts like the container of the bin file and the fragments. This file can be edited using RPFM. To do so you must unpack the files inside of it and make sure that you repack them when done.

==== Bin (.bin) ====
The bin file contains the key that is used by the database and links that with a skeleton, and optional mount bin entry and a set of fragments. Most entries contains multiple fragments, where the fragments later in the list overrides Slots in earlier fragments.

==== Fragments (.frg) ====
The fragment files contains the actual capabilities of the animation set. This is where you link action with the visual animation.
[[File:RPFM frg view.png|none|thumb]]
The "Slot and Id" tells the game what action the animation should trigger for. If you try to use any capabilities without having the slot, it will often not work. For example adding a ranged attack without adding the correct Slots will result in the unit not being able to fire its weapon.

For each row there is also a meta file which can override how the animation looks, as well as add effects such as particles, camera shake, hit position, AOE, etc.

The row also contains a checkbox for which prop slots in the VMD should be visible.

==== Skeletons (.anim) ====

==== Animations (.anim) ====

==== Animation meta (.meta.anim) ====

=== Mounts ===
The game uses two different mount systems:

==== Attachment point mounts ====
The attachment system is used for two different things; Rider animations for units not really doing much (unit on top of a war mammoth which is just sitting there, no matter what is happening) and units with multiple riders (Necrofex, war-wagon)

==== Synced animation mounts ====

File:RPFM frg view.png

2021-07-08T17:16:37Z

H3ro:

RPFM_frg_view

Tutorial:Animation and You

2021-07-08T17:08:46Z

H3ro:

Animations in Total war controls a great deal, but its important to know that the game has no idea what an animation is. It depends on configuration and meta data to actually use it for anything apart from a visual display.
=== File types ===

==== Animpacks (.animpack) ====

==== Bin (.bin) ====

==== Fragments (.frg) ====

==== Skeletons (.anim) ====

==== Animations (.anim) ====

==== Animation meta (.meta.anim) ====

=== Mounts ===

==== Attachment point mounts ====

==== Synced animation mounts ====

Tutorial:Animation and You

2021-07-08T17:07:09Z

H3ro: Created page with "Animations in Total war controls a great deal, but its important to know that the game has no idea what an animation is. It depends on configuration and meta data to actually..."

Animations in Total war controls a great deal, but its important to know that the game has no idea what an animation is. It depends on configuration and meta data to actually use it for anything apart from a visual display.

The key filetypes for animations are:

* Animpacks (.animpack)
* Bin (.bin)
* Fragments (.frg)
* Skeletons (.anim)
* Animations (.anim)
* Animation meta (.meta.anim)

=== File types ===

==== Animpacks ====

==== Bin ====

==== Fragments ====

==== Skeletons ====

==== Animations ====

==== Animation meta ====

Tutorial:AssetEditor

2021-06-23T13:48:35Z

H3ro:

Tutorial:AssetEditor

2021-06-22T07:29:21Z

H3ro:

File:Mount tool defaultworkflow fixstuff.png

2021-06-22T07:29:08Z

H3ro:

Mount tool defaultworkflow fixstuff

Tutorial:AssetEditor

2021-06-21T21:00:57Z

H3ro:

File:Mount tool defaultworkflow.png

2021-06-21T20:25:17Z

H3ro:

Mount tool defaultworkflow

Tutorial:AssetEditor

2021-05-26T10:21:25Z

H3ro:

Tutorial:AssetEditor

2021-05-23T19:49:57Z

H3ro:

Tutorial:AssetEditor

2021-05-23T19:46:32Z

H3ro:

Tutorial:AssetEditor

2021-05-23T19:46:07Z

H3ro:

Tutorial:AssetEditor

2021-05-23T19:45:49Z

H3ro:

File:Remapping.png

2021-05-23T19:45:25Z

H3ro:

Remapping

Tutorial:AssetEditor

2021-05-23T19:37:05Z

H3ro:

Tutorial:AssetEditor

2021-05-23T19:35:53Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

'''Disclaimer''': I am not good at technical writing or enjoy it, so if someone feels the desire to improve this, then please!

==Basics==

=== Camera ===
All the visual editors uses ALT+ Mouse to move the camera.

Zoom = Alt+ Mouse Wheel

Move = Alt + Right button

Rotate = Alt + Left button

=== Saving ===
The tool works both with individual files and the pack files themselves. As a result of this each of them has to be saved separately. Saving a file in an editor adds it to the in memory packfile (which then goes red), which have to be right clicked then saved.
[[File:SavePackfile.png|thumb|alt=|none]]

==Sub Tools==

===Kitbash Editor===
Some text to come here, maybe someone want to write it?

Youtube tutorial: https://www.youtube.com/watch?v=LeObDGqV2PM

====Re-Regging====
One of the key parts of the Kitbash editor is the ability to re-rig a mesh from one skeleton to an other. If this is not done, the mesh will turn into spaghetti when an animation is applied.

It works by doing a 1:1 mapping between bones in the original skeleton (left side) and the target skeleton (right side)

It works by selecting bones one by one on the left side and then selecting a bone on the right side. When this is done the column on the left side that says -1 should turn into the same the bone selected on the right side.

The tool can also attempt to auto fit the mesh onto the skeleton by selecting the "Fit mesh to skeleton" checkbox.

[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb|Bone selected and mapped correctly]]

====BMI tool====
The BMI editor allows the scaling of a mesh along its normals. This gives the impression of adding or removing thickness to and object.

All the bones that are selected in the tree view is applied to the scale when the apply button is pressed.[[File:BmiTool before.png|none|thumb|Before]]
[[File:BmiTool After.png|none|thumb|After]]

===Mount Animation Creator===
The tool also allows for attaching an animation to a vertex on an other skeleton. This is useful for creating mount animations for mount that does not exist in the game.

An example of this would be adding a Squig mound to Karl Franze or a Lion animation to the High Elf Princess. https://www.youtube.com/watch?v=4dKFXAu4R1Y

A run-through of the UI components:

# Information about the rider (mesh, skeleton and animation)
# Information about the mount (mesh, skeleton and animation)
# A shortcut menu to make it easier to work with animation sets.
#* Mount is the animation fragment used by the mount
#* Rider is the animation fragment used by the rider
#* Mount animation tag is the animation used by the mount
#* Rider animation tag is the animation used by rider. The tool tries to auto select the matching animation when a mount animation is selected
#* "Generate and save all" Runs through all the animations in the mounts animation set and generates animations for the rider.
# Control how the rider is attached to the mount
#* Rider root bone (probably never change this)
#* The vertex the rider is attached to. Select the mount, press F3 then select the vertex that the rider should be select to and press Set. The first selected vertex is used if multiple vertexes are selected
# Settings for the animation - Hopefully pretty intuitive apart from the Max Rider rot, which you probably should always leave at default
# Press "Preview" to generate an animation with the current settings
# The animation preview controller to see how the animation looks

[[File:Image.png|none|thumb|Screenshot]]
[[File:Image2.png|none|thumb|Selecting vertex]]

===Anm.Meta files Editor===
The tool can display and edit most meta file, more information will be added later[[File:ImageMeta.png|none|thumb]]

Tutorial:AssetEditor

2021-05-23T19:28:37Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

'''Disclaimer''': I am not good at technical writing or enjoy it, so if someone feels the desire to improve this, then please!

==Basics==

=== Camera ===
All the visual editors uses ALT+ Mouse to move the camera.

Zoom = Alt+ Mouse Wheel

Move = Alt + Right button

Rotate = Alt + Left button

=== Saving ===
The tool works both with individual files and the pack files themselves. As a result of this each of them has to be saved separately. Saving a file in an editor adds it to the in memory packfile (which then goes red), which have to be right clicked then saved.
[[File:SavePackfile.png|thumb|alt=|none]]

==Sub Tools==

===Kitbash Editor===
Some text to come here, maybe someone want to write it?

Youtube tutorial: https://www.youtube.com/watch?v=LeObDGqV2PM

====Re-Regging====
One of the key parts of the Kitbash editor is the ability to re-rig a mesh from one skeleton to an other. If this is not done, the mesh will turn into spaghetti when an animation is applied.

It works by doing a 1:1 mapping between bones in the original skeleton (left side) and the target skeleton (right side)

It works by selecting bones one by one on the left side and then selecting a bone on the right side. When this is done the column on the left side that says -1 should turn into the same the bone selected on the right side.

The tool can also attempt to auto fit the mesh onto the skeleton by selecting the "Fit mesh to skeleton" checkbox.

[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb|Bone selected and mapped correctly]]

====BMI tool====
The BMI editor allows the scaling of a mesh along its normals. This gives the impression of adding or removing thickness to and object.

All the bones that are selected in the tree view is applied to the scale when the apply button is pressed.[[File:BmiTool before.png|none|thumb|Before]]
[[File:BmiTool After.png|none|thumb|After]]

===Mount Animation Creator===
The tool also allows for attaching an animation to a vertex on an other skeleton. This is useful for creating mount animations for mount that does not exist in the game.

An example of this would be adding a Squig mound to Karl Franze or a Lion animation to the High Elf Princess. https://www.youtube.com/watch?v=4dKFXAu4R1Y

[[File:Image.png|none|thumb|Screenshot]]
[[File:Image2.png|none|thumb|Selecting vertex]]

===Anm.Meta files Editor===
[[File:ImageMeta.png|none|thumb]]

Tutorial:AssetEditor

2021-05-23T19:03:36Z

H3ro:

The AssetEditor is a poor man's 3d program for Total war games (currently only supports WH2).

It aims at trying to recreate the Kit bashing feeling you get when working with plastic models.

==Basics==

=== Camera ===
All the visual editors uses ALT+ Mouse to move the camera.

Zoom = Alt+ Mouse Wheel

Move = Alt + Right button

Rotate = Alt + Left button

=== Saving ===
The tool works both with individual files and the pack files themselves. As a result of this each of them has to be saved separately. Saving a file in an editor adds it to the in memory packfile (which then goes red), which have to be right clicked then saved.
[[File:SavePackfile.png|thumb|alt=|none]]

==Sub Tools==

===Model editor===

====Re-Regging====
[[File:ReriggingImage.png|none|thumb]]
[[File:RemappingBoneSelected.png|none|thumb]]

====BMI tool====
[[File:BmiTool before.png|none|thumb]]
[[File:BmiTool After.png|none|thumb]]

===Mount Animation Creator===
[[File:Image.png|none|thumb]]
[[File:Image2.png|none|thumb]]

===Anm.Meta files decoder===
[[File:ImageMeta.png|none|thumb]]