Cragger, on 29 August 2013 - 02:37 PM, said:
Might want to stop before your entire face is brown. PGI released an update that caused this issue. Avast did not. MWO is the only title out of the 42 titles I have installed through steam and 30 titles installed outside of steam plus the other 115 programs on my network to have ever had or still be experiencing this issue.
Please read and research before committing to brown nosing.
Wow, nice personal attack.
QUICK SOMEONE TRIES TO MEDIATE THE HATE! KILL HIM!!!!!
ALSO
This bug IS present in other games suggesting that it is not JUST mwo and pgi.
That being said there is A LOT of things that pgi HASN"T done that **** me off but that is another matter.
If you had taken even an iota of time to look at my pasts posts you would see that I am not 100% happy with this game or with pgi as is.
Edit:
Just recieved a response from Russ on twitter.
"This one is weird as the binary is properly signed, they are working on it."
You can see the response on his twitter page.
They are working on the issue it's just a much larger problem than many of the other things that they have had to tackle in the last month. So you are seeing fixes for smaller things while this is being worked on. That DOES NOT mean they are abandoning you all.
I want to say that this issue is frustrating to me as well. I finally convinced one of my friends to try MWO right after that patch and he is unable to play due to the same reasons. The best thing we can do is send as much info to the developers as possible rather than sitting here and bitching about it. Nagging NEVER moves things faster.
Further Edit: My friend just discovered that you can exclude specific .exe files from avast sandboxing and this fixed his issue. Something worth looking into that won't completely leave your computer at risk.
Edited by 42and19, 30 August 2013 - 03:27 PM.