Darn paths!

[Destiny]

That's just one of those things that make me mad. I AM NOT ABLE TO IMPORT MODELS AND SKINS PROPERLY!!! Whenever I import a custom model it says "Could not load blablablabla" and the model becomes a green box. I've tried this about a hundred times now and I also read some threads and tutorials about importing. But I never seem to get it right. Most of the times people say that you need to insert the path which stands on the site where I downloaded the model (and it's skins). But there aren't always paths given. Sometimes there's only the name of the skin (in green). So where should I get the paths from?

 

[acolyteofdoom]

The name in green is the path..... It coincides to what the name of the skin is...

 

[GreyArchon]

For models, change the path of the files in the import editor to exactly what it says on the site. If it says only the filename... MAKE IT ONLY THE FILENAME. (by removing war3mapimported\)

For skins, rename the entire file to the skin for the unit it belongs too. So if someone made a UBERDRUIDOMGLOL.blp skin, which fits on the druid of the talon, rename it to the exactl path of the druid of the talon's skin, including .blp name.

 

[Sopho]

Ignore the error message.
It will always show that up for a while. WE Takes longer to recognise the model than in the game does. It'll effect the object manager, be patient and do not be discouraged.

As long as it works in the game its ok.

+ Some models have no paths. Restart WE. Make sure all the model files are imported with their paths correct.

 

[Destiny]

Ok. The model I downloaded is named Owa. And on the site it says the paths are simply the names of the skins. So I renamed the paths to the names of skins and now it says: "Could not load Warcraft III/Owa/Owa.mdl"
And there is a txt file which reads:
path:
Warcraft III/units/Owa (somehow I can't write backslashes on this site)

Import manager:
TextOWA2.blp
white.blp
Owa.mdx

My paths are now exactly what it says above and it still doesn't work. Why do I need an Owa mdl file?

 

[Destiny]

And no, it didn't work in the game.

 

[Nasrudin]

You know, you can open a mdx file with the notepad (BUT DON'T MAKE ANY CHANGES, OR YOU'LL RUIN IT) the path should be near the beginning. Useful if you download a model and the author didn't wrote the paths

 

[GreyArchon]

MDX's become MDL's after being imported... somehow. :/ It's odd, have you tried asking the maker of the model?

 

[Destiny]

Thx for your advice Nas. This will help me cery much in the future. But in this case it just reads the names of the skins. So that must be what I should name the paths. But I've already done that and when I load the map it still says: "Could not load Warcraft III/Owa/Owa.mdl" And I've never heard that you need an mdl file. So why does it say that?

 

[Destiny]

"It's odd, have you tried asking the maker of the model?"
No. But I'll do that right away.

 

[Nasrudin]

Try making a new map and don't import anything else than the model that give you problems. Be sure the path are correct, save and quit the editor. Load and if you are sure you've made no mistakes than the model is bugged.

 

[Destiny]

Am I an idiot or what? All I needed to do was reassigning the model to the unit. I'm so dumb.