Error codes when I try to load poe

When I try to load path of exile, I get multiple error codes reading:

"Error opening file: Art/Models/Effects/poisen_arrow/poison_arrow.smd"

"'Metadata/Effects/Spells/poison_arrow/poison.ao': Error opening file: Art/Models/Effects/poisen_arrow/poison_arrow.smd" <--- this one 3 times

Then I get a message saying "Runtime Error!"

I've tried to do a Pack Check. I ran it and it said everything was in sync and fixed, but when I ran poe again, the same error codes popped up.
No clue what to do, someone please help!

Thanks

"

Drakier wrote:

Can you please post a DxDiag.exe export in a spoiler tag or pastebin link here?

How would I do that?

I'm having the exact same problem, as of today (haven't played in some time, though, so it may have cropped up sooner.) I can't help but wonder whether that "poisen" is a typo, and maybe it's looking for a file in a folder that is actually spelled correctly? Just a thought...


Regardless, I'm having the exact same problem, and I too have tried to PackCheck and it returned no errors for me, either.

(It makes me despondent that, after some months of being unable to play, I finally get some time, only to be greeted by this failure :( Just my luck...)

Here's the path that is being referenced:

Art/Models/Effects/poisen_arrow/poison_arrow.smd (Also: Metadata/Effects/Spells/poison_arrow/arrow.ao)

Actually, I had already read all those replies, and tried everything that was suggested (ie. defrag the pack then run the packcheck; also ignored one action that is inapplicable to my high-end rig) - none of it worked. I even specified in my post that I had already tried some of this, as well as trying to provide relevant (hopefully even useful) data. (Btw, I don't think DXdiag is going to reveal anything useful in this case: it appears to be a file addressing issue, not a graphics, sound, or input problem - but I could be mistaken, of course.)

I have since rectified the issue, but was forced to resort to a most unwelcome method - re-downloading the game, which is not only a VERY slow process in my country (took all night, 6hrs+), but also expensive, as data connections here are not uncapped as they are in pretty much the rest of the world. Furthermore, I did this with some trepidation, as another user reporting the same problem had mentioned that a reinstall had NOT, in fact, solved it for him - so I had to risk wasting 7GB of download that might not even solve the problem - THAT is why I posted here, in response to a thread dealing with the same problem. In every other forum I've been on, it is DISCOURAGED to spam out new threads about the same topic; users are encouraged to keep discussion of same issues contained within as few threads as possible - consolidate the information, so users don't have to hunt through half a dozen or more separate threads that are not easily searched out (I had to search externally to find topics within the forum), and which all start out the same way and go on to reinvent the wheel over and over, only to have their question NOT answered, ultimately. That's right: there was not a single definitive answer among them, the closest being a couple of people for whom reinstalling worked, but also another for whom it had not - but no actual tech-support-worthy FIX, such as the application of a troubleshooting tool, editing of an .ini or the like, small file download, etc. - instead, only a 7GB gamble based on hearsay. So, instead of spamming out a duplicate thread, or necroing an old one, I kept it to a current one (again, the appropriate approach in every single other forum I have used - not to mention logical.)

Why did I post in the first place? The first reason is obvious: in the hopes of a solution. But there is another, more "global" factor: this problem has been reported several times, and yet none of those posts were responded to in a satisfactorily resolutory manner - now, given that it's an issue that apparently recurs, I would say it merits some attention from the devs, don't you think?

*shakes head and walks away*

PS: SOLUTION (in this particular case, at any rate)
Add one to those for whom reinstalling this game DID fix this issue (but keep in mind that, for at least one other user, it did not.) Anyone else who has this same problem, and who lives in the first world with unlimited Internet access, can go ahead and try this (though I recommend first trying the pack defrag and pack check, followed by a reboot just to be safe.)

PPS: To GGG devs, a suggestion: As far as I can tell, this problem seems to stem from some sort of file corruption somewhere that is somehow getting past the PackCheck utility - I think it would behoove you to dig around for the cause of it - I suspect it may be simple to fix once it's identified (THAT part may be trickier, I suspect!) Another clue is in the fact that it's been the same file in this latest "outbreak" (poisen_arrow etc), but has previously also hinged on another file (mentioned in some other thread, so I'm not about to go digging for it to quote it - were it in THIS thread, it would be a different story...) Whether that points at an intermittent glitch in your server-side patch packaging process, or something entirely different, I can't even begin to guess.