Hi guys,
I've been having this problem for the last couple of weeks now, and I have tried many options and variations to figure out what might be the issue.
Simply put, when I run DB with an Archon Wizard, if it casts Disintegration Wave for a while it will cause Diablo to give me a "Network Disconnect" error.
What does a while mean? Here's where I begin my tests:
- Latest .Net and VC++ installed
- Fresh install of Diablo 3 and DB (comes with Trinity 1.7.3.10) - Worse case, ~2.5-3s of laser and error will occur
- Downgrade to Trinity 1.7.3.9 - Problem still exists but better, ~5-6s of laser and error will occur
- Downgrade to Trinity 1.7.3.8 - Best case, problem still exist though, ~7-10s of laser and error will occur
- Tested multiple profiles, all have the same results with corresponding Trinity versions, so it seems that it is not a profile problem
- Another thread indicated it could be a TPS issue; tested @ default values, and custom values (10 and 20), with the same results per Trinity version
At the moment I am completely lost; short of doing a fresh install of Windows I have no idea what else to try.
To add to this:
I do have another computer which I have tested on, it's not a "fresh" install, but it is a school computer, meaning minimal programs installed (Windows, Drivers, Office, Adobe). Using this computer to test, the results get a little better, but not by much. By a bit a mean by 1 or 2 seconds.
As you can imagine, this is pretty hassle some for me, as I am forced to run at reduced MP lvls to make sure my Wizard doesn't "cast" too long and cause a DC.
I have also attached a log from DB right after the DC happens and the bot closes the DC error dialog, using Trinity 1.7.3.8 (best results) and TPS at 30.
I've been having this problem for the last couple of weeks now, and I have tried many options and variations to figure out what might be the issue.
Simply put, when I run DB with an Archon Wizard, if it casts Disintegration Wave for a while it will cause Diablo to give me a "Network Disconnect" error.
What does a while mean? Here's where I begin my tests:
- Latest .Net and VC++ installed
- Fresh install of Diablo 3 and DB (comes with Trinity 1.7.3.10) - Worse case, ~2.5-3s of laser and error will occur
- Downgrade to Trinity 1.7.3.9 - Problem still exists but better, ~5-6s of laser and error will occur
- Downgrade to Trinity 1.7.3.8 - Best case, problem still exist though, ~7-10s of laser and error will occur
- Tested multiple profiles, all have the same results with corresponding Trinity versions, so it seems that it is not a profile problem
- Another thread indicated it could be a TPS issue; tested @ default values, and custom values (10 and 20), with the same results per Trinity version
At the moment I am completely lost; short of doing a fresh install of Windows I have no idea what else to try.
To add to this:
I do have another computer which I have tested on, it's not a "fresh" install, but it is a school computer, meaning minimal programs installed (Windows, Drivers, Office, Adobe). Using this computer to test, the results get a little better, but not by much. By a bit a mean by 1 or 2 seconds.
As you can imagine, this is pretty hassle some for me, as I am forced to run at reduced MP lvls to make sure my Wizard doesn't "cast" too long and cause a DC.
I have also attached a log from DB right after the DC happens and the bot closes the DC error dialog, using Trinity 1.7.3.8 (best results) and TPS at 30.






