Errors with "Sand Troll Shaman" model imports.

[Pr0nogo]

The model.
Appears as a green box and gives me the 'could not read blah blah blah.mdl' error.

Map is attached. It's probably some newb mistake but all other models so far have worked out just fine.

 

[Sin'dorei300]

When you import it, remove the war3mapimported/ and then press OK to work properly.

 

[Bernkastel]

Remove war3mapimported/ from the texture, you do not have to do anything with the model.

 

[Pr0nogo]

You'd think the model wouldn't give me an unreadable error if I didn't have to do anything with it...

When I remove the imported path from the texture, it's still giving me the same error. It's an issue with reading the model, I think. The same goes for when I remove the imported path from the model itself, as well.

 

[Adiktuz]

you can try redownloading then reimporting the model

 

[Pr0nogo]

Already did, several times.

 

[Adiktuz]

Have you done it like this?

1)Delete model and texture from the imported files
2)Save your map
3)Close WE
4)Reopen WE
5)Reopen your map
6)Reimport
7)Remove war3mapimported from texture file
8)Hit save button

the crucial thing here is that you save then close the map when you remove imported textures, and that you set the file paths to the right ones before you save the map after importing something

 

[Bernkastel]

Atleast when I changed the path to SandTroll.blp, it worked properly. You are aware that it does not change without a restart, yes?
Also, as for the map I suggest adding "Turn off this trigger" as first action of every region based trigger.

 

[Pr0nogo]

Yes, I planned on including that trigger function. I haven't touched the triggers at all for years (the map was just left over from a long time ago, so nothing trigger-wise is indicative of my current mapping skills - which are rather limited for War3).

Opening/closing the editor did nothing. However, when I emailed the map to myself and continued working on it at a different computer, I found that the graphic was loading properly after loading it up with World Editor Unlimited. Strange, but at least the issue is resolved.