How to import CSW - Orc Fortress (T3)

Introduction

This is an automatically generated tutorial. It will guide you through the process of importing the model CSW - Orc Fortress (T3) of the bundle CSW - Orc Fortress (T3). Please note that all the screenshots in this tutorial were made using a Mac, however it should be no problem to interpret what is equivalent on a Windows or Linux machine.

Extract and Access

I am assuming that you have already downloaded the file CSW - Orc Great Hall ( Upgrades).zip and know where it is located on your hard drive. The file is compressed as a zip archive. Most modern operating systems allow you to unzip the archive by double clicking it and dragging the contents out to the desktop (or any other place).

When you have extracted the archive, it should look like this:

Open World Editor and click Module -> Import Manager:

This is the Import Manager. From here you can add and remove custom files from your map file:

Importing WC2GreatHallTier3.mdx

Now Click the "Import File" Button:

Next select 'WC2GreatHallTier3.mdx' in the folder which you extracted from the zip archive:

The file has been properly added to the map archive:

Done, you have imported the file WC2GreatHallTier3.mdx.

Importing Fortress_Diffuse.dds

Now Click the "Import File" Button:

Next select 'Fortress_Diffuse.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file Fortress_Diffuse.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file Fortress_Diffuse.dds.

Importing Fortress_Emissive.dds

Now Click the "Import File" Button:

Next select 'Fortress_Emissive.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file Fortress_Emissive.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file Fortress_Emissive.dds.

Importing Fortress_Normal.dds

Now Click the "Import File" Button:

Next select 'Fortress_Normal.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file Fortress_Normal.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file Fortress_Normal.dds.

Importing Fortress_ORM.dds

Now Click the "Import File" Button:

Next select 'Fortress_ORM.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file Fortress_ORM.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file Fortress_ORM.dds.

Importing FortressGround_Diffuse.dds

Now Click the "Import File" Button:

Next select 'FortressGround_Diffuse.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file FortressGround_Diffuse.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file FortressGround_Diffuse.dds.

Importing FortressGround_Emissive.dds

Now Click the "Import File" Button:

Next select 'FortressGround_Emissive.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file FortressGround_Emissive.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file FortressGround_Emissive.dds.

Importing FortressGround_Normal.dds

Now Click the "Import File" Button:

Next select 'FortressGround_Normal.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file FortressGround_Normal.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file FortressGround_Normal.dds.

Importing FortressGround_ORM.dds

Now Click the "Import File" Button:

Next select 'FortressGround_ORM.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file FortressGround_ORM.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file FortressGround_ORM.dds.

Importing Stronghold_Diffuse.dds

Now Click the "Import File" Button:

Next select 'Stronghold_Diffuse.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file Stronghold_Diffuse.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file Stronghold_Diffuse.dds.

Importing Stronghold_Normal.dds

Now Click the "Import File" Button:

Next select 'Stronghold_Normal.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file Stronghold_Normal.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file Stronghold_Normal.dds.

Importing Stronghold_ORM.dds

Now Click the "Import File" Button:

Next select 'Stronghold_ORM.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file Stronghold_ORM.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file Stronghold_ORM.dds.

Importing StrongholdRocks_Diffuse.dds

Now Click the "Import File" Button:

Next select 'StrongholdRocks_Diffuse.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file StrongholdRocks_Diffuse.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file StrongholdRocks_Diffuse.dds.

Importing StrongholdRocks_Normal.dds

Now Click the "Import File" Button:

Next select 'StrongholdRocks_Normal.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file StrongholdRocks_Normal.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file StrongholdRocks_Normal.dds.

Importing StrongholdRocks_ORM.dds

Now Click the "Import File" Button:

Next select 'StrongholdRocks_ORM.dds' in the folder which you extracted from the zip archive:

As you see, the field "Full Path" starts with something like "war3mapimported/". But most models do not look for their assets in that directory. The assets need to be in a specific location in order for the model to find them. Therefore, you will have to change the "Full Path" to what the model looks for. You can find the required paths in the readme.txt and also on this page.

Double-click the file StrongholdRocks_ORM.dds:

Tick the box "Use Custom Path" and type in the correct path:

The file has been properly added to the map archive:

Done, you have imported the file StrongholdRocks_ORM.dds.

You're done

You have now imported your model. Don't be afraid when you place the object and it appears to be a purple cube. Just close the map, re-open it and it will look fine in the World Editor.

If you did exactly as this guide told you and it did not work properly. Please make a thread in the Modeling & Animation Forum containing the following: