![]() This is not feasible for an indie company that publishes fixes and updates often. The only way to avoid false positives is to whitelist every single build of the game with every single AV company, a process that can take weeks. ![]() For instance, under some circumstances reading memory backward with might seem like a buffer underflow attack to the heuristic algorithm. This means that often they implement strange memory access/management algorithms that are misinterpreted by AV software as potentially malicious since heuristics are rather dumb. Whats baffling is, that before launching the game, if I scan it with Avast, it detects nothing. While trying to recover HashCheck due to Windows 10 being updated to Creators Avast prevents me to be successful:C:\Users\AppData\Local\Temp\NSU14F.TMP > IDP.Now, it happens on launch, which makes it impossible to launch the game. But before, it was doing that only after I quit the game. The root issue here is that c game engines are built for performance and robustness is correctness. So, I have been having problem with Avast detecting Paladins.exe as an IDP.GENERIC for over a month now. Here (although I'm pretty sure I read this suggestion somewhere else on steam where it also explained why false positives are common in games): Actually, seldom is the case where a game is marked as a threat, and is unheard of in the realm of triple A games. Where exactly do steam advocate such behavior? Customers should never be forced to disable their anti-virus just to play a game. Submittimg every build to every antivirus company for whitelisting and waiting for them is unrealistic and would mean one update a year probably.įor that reason Steam recommends users to whitelist whole games directory. With each update code changes so issues like this come and go. Originally posted by Konstanty:It's not an issue, it's Avast mistaking code optimizations for malware/viruses.
0 Comments
Leave a Reply. |