update ashitaShinta wrote:viken62 wrote:sorry, i should have mentioned i'm playing on the DS Test server. I needed to update my client like you suggested. i used the instructions found on the following link:
http://tehkrizz.net/FFXI/patchguide.php
Thanks!
Did this fix the crash on attack issue? I tried this method, and now when I boot up Ashita, I get a POL crash error as FFXI begins to open. I'm using Windows 7 64-bit and I downloaded/installed the correct version of POL to use. Any suggestions?
crash when i attack
Re: crash when i attack
Re: crash when i attack
Thanks for the quick reply. I found the answer in the other thread but you would have been 100% correct as well. Time to play!!kjLotus wrote:update ashitaShinta wrote:viken62 wrote:sorry, i should have mentioned i'm playing on the DS Test server. I needed to update my client like you suggested. i used the instructions found on the following link:
http://tehkrizz.net/FFXI/patchguide.php
Thanks!
Did this fix the crash on attack issue? I tried this method, and now when I boot up Ashita, I get a POL crash error as FFXI begins to open. I'm using Windows 7 64-bit and I downloaded/installed the correct version of POL to use. Any suggestions?
-
bluekirby0
- Developer
- Posts: 707
- Joined: Sun Jul 22, 2012 12:11 am
Re: crash when i attack
Just as a note to people who try the file check and get "No problems found"
The file check is done in two stages. First is an offline check that checks files against the hashes stored locally. If your client is out of date and all files are intact, you will not proceed to the second stage, thus the "No problems found" message.
The second stage is an online check, where it downloads the latest patch version hashes and redoes the entire file check against THOSE hashes. Why this isn't done in the first place is a mystery to me as the file with the hashes is very small and the amount of time it would save skipping the first step is often an hour or more. Anyway, anything that is missing or doesn't match this second set of hashes is re-downloaded.
The one exception is any DAT that, in the latest update, is still identical to the original installation media version and gets corrupted will be detected as bad but will not be replaced. For example, if you mod a DAT containing an armor model for an older piece of equipment, it will likely show as bad but will not be repaired. You can use this to your advantage to make your client "always update-able" via file check as long as the mod itself does not cause any issues.
Anyway, that concludes the lesson for today. Feel free to smack SE around for making this stupid update system that doubles the burden on the end-user needlessly.
The file check is done in two stages. First is an offline check that checks files against the hashes stored locally. If your client is out of date and all files are intact, you will not proceed to the second stage, thus the "No problems found" message.
The second stage is an online check, where it downloads the latest patch version hashes and redoes the entire file check against THOSE hashes. Why this isn't done in the first place is a mystery to me as the file with the hashes is very small and the amount of time it would save skipping the first step is often an hour or more. Anyway, anything that is missing or doesn't match this second set of hashes is re-downloaded.
The one exception is any DAT that, in the latest update, is still identical to the original installation media version and gets corrupted will be detected as bad but will not be replaced. For example, if you mod a DAT containing an armor model for an older piece of equipment, it will likely show as bad but will not be repaired. You can use this to your advantage to make your client "always update-able" via file check as long as the mod itself does not cause any issues.
Anyway, that concludes the lesson for today. Feel free to smack SE around for making this stupid update system that doubles the burden on the end-user needlessly.