Filename doesn't exist: data/models/weapon_hoplite_pike_high.CAS

Everytime I try to fight a battle I get this error message during the loading screen:

Filename doesn't exist: data/models/weapon_hoplite_pike_high.CAS

...

That is not a unit. It's the pike .cas filke used by all phalanx units. Answer: Bad EB install.

Quote:

---

Originally Posted by Aymar de Bois Mauri

That is not a unit. It's the pike .cas filke used by all phalanx units. Answer: Bad EB install.

---

that is what I figured and I reinstalled it but got the same error, should I try redownloading it?

Quote:

---

Originally Posted by alman7272

that is what I figured and I reinstalled it but got the same error, should I try redownloading it?

---

Some goo samaritan can just send you the file...

...can someone send me the cas file, please? :D

Quote:

---

Originally Posted by alman7272

...can someone send me the cas file, please? :D

---

First you should check in EB\Data\MODELS to see if it is there under another name.

It is actually there: weapon_hoplite_pike_high.CAS

The file size is 1.71 KB, is the file incomplete or damaged?

Quote:

---

Originally Posted by alman7272

It is actually there: weapon_hoplite_pike_high.CAS

The file size is 1.71 KB, is the file incomplete or damaged?

---

Same as mine. Check if the name is the exact same.

E:\Program Files\Activision\Rome - Total War\EB\Data\MODELS\weapon_hoplite_pike_high.CAS

that is the filepath.


compared to...

data/models/weapon_hoplite_pike_high.CAS

is it case sensitive?

sorry to doube post, but any ideas on what is wrong?

Try copying that from the EB/data/models/ directory to the data/models/ directory in the RTW folder. This will add it to your Vanilla directory structure.

If you encounter any other weird missing model errors it could very well be a bad installation for whatever reason. If that's the case, try reinstalling Vanilla 1.5 and then 0.8 over that.

Well, the setup file takes FOREVER to extract (it gets stuck at the end) and then when it's done it says not enough disk space. Which makes no sense, since I have 109 gigs left on my E: drive where programs are installed.

The Problem is that it uses your system drive C:\ as target to extract the temporary setup files.

Ok, this is what I figured, is there anyway to remedy this?

hum, apparently it's fixed now.