Mahther wrote:I made a couple of new characters with the wizard and both of them have this problem, but the character set that I created manually does not. Does this have anything to do with the ISBoxer created cache?
No, ISBoxer generates cache folders for Slots rather than Characters. The cache folders will be reused by all of your teams and will work the same as when you made them manually. The only difference is that, now, they are copied for you the first time you load up. So the
first time someone plays with ISBoxer, it is expected for all instances to launch slower because the cache is being copied from the original, but after that the cache is already copied. That all happens when the game instance is launched, when you're waiting to see the Diablo 3 login screen. (Screen may appear gray while the cache is opened/copied; prior to the automatic cache handling this is where people used to get stuck for 7-8 minutes and then it wouldn't work, if they did the cache wrong).
However, this thread sounds more like the game comes up, you log in and are at the character screen, and then when you enter the game it takes longer than usual to join the game. This should not be related to the cache.
Diablo 3 keeps some log files that may be useful in diagnosing what is happening. Most importantly, "D3Debug.txt" in your Diablo 3 folder. Note that your Battle.net account e-mail address is listed in this file, so be aware of that if you're going to show this file to someone. But, it details the cache files being opened, games being joined, etc and might help identify the problem you guys are having. If you would like me to look at your D3Debug.txt file and try to figure out what is going wrong:
1. Delete the D3Debug.txt file
2. Launch your team and make the problem happen (join the game, or whatever)
3. Send me the new D3Debug.txt file; email to
lax@lavishsoft.com is fine
Fri May 18, 2012 1:41 pm 