We’ve not found any situations that could produce a false positive, have found that the circumstances for which they were banned were clear and accurate, and we are extremely confident in our findings. We’ve extensively tested for false positive situations, including replicating system setups for those who have posted claiming they were banned unfairly. It turns out that Warden was crashing in some version of WINE that some Linux users were running and as a result it was flagging them. There were some who were botting but many were not. Once during the summer and more in November. ![]() What had happened was that there was a wave of bans that involved a lot of Linux users. ![]() If that fails, then do the following on the desktop shortcut for diablo 3:ģ.) In the "Target" line go to the end of it (place a space after the last ") and type " -launch" (no quotes)įollowing these steps got it to work for me, and boy is it worth it! Good Luck! If you're still having issues after that, I'd recommend running D3 as administrator. Follow these steps to get it to work:ġ) Download the latest version of sweetFX (1.4) from this link:Ģ) Grab the complete and proper config file from my google docs:ģ) extract the contents of the zip file in step 1 to your diablo 3 directoryĤ) replace SweetFX_settings.txt with the file you got from my docs folder ![]() I believe it's because the post points to an old version of sweetFX (1.3.3), and the settings file seems to be incomplete. Last updated at 14:00:17 UTC Weekly Help Desk RAGE Loot Thread Trade Thread
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |