How to import Ashe (Overwatch) for Reforged graphics

Introduction

This is an automatically generated tutorial. It will guide you through the process of importing the model Ashe (Overwatch) for Reforged graphics of the bundle Ashe (Overwatch) for Reforged graphics. 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 Ashe (Overwatch) for Reforged graphics.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 OW_Ashe_Combined.mdx

Now Click the "Import File" Button:

Next select 'OW_Ashe_Combined.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 OW_Ashe_Combined.mdx.

Importing Ashe_base_diff.dds

Now Click the "Import File" Button:

Next select 'Ashe_base_diff.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 Ashe_base_diff.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 Ashe_base_diff.dds.

Importing Ashe_base_emis.dds

Now Click the "Import File" Button:

Next select 'Ashe_base_emis.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 Ashe_base_emis.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 Ashe_base_emis.dds.

Importing Ashe_base_nrm.dds

Now Click the "Import File" Button:

Next select 'Ashe_base_nrm.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 Ashe_base_nrm.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 Ashe_base_nrm.dds.

Importing Ashe_base_orm.dds

Now Click the "Import File" Button:

Next select 'Ashe_base_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 Ashe_base_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 Ashe_base_orm.dds.

Importing Ashe_Logo.dds

Now Click the "Import File" Button:

Next select 'Ashe_Logo.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 Ashe_Logo.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 Ashe_Logo.dds.

Importing Ashe_part_diff.dds

Now Click the "Import File" Button:

Next select 'Ashe_part_diff.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 Ashe_part_diff.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 Ashe_part_diff.dds.

Importing Ashe_part_emis.dds

Now Click the "Import File" Button:

Next select 'Ashe_part_emis.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 Ashe_part_emis.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 Ashe_part_emis.dds.

Importing Ashe_part_nrm.dds

Now Click the "Import File" Button:

Next select 'Ashe_part_nrm.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 Ashe_part_nrm.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 Ashe_part_nrm.dds.

Importing Ashe_part_orm.dds

Now Click the "Import File" Button:

Next select 'Ashe_part_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 Ashe_part_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 Ashe_part_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:

And we will do what we can to help you.