![]() 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. ![]() ![]() Edit: I currently see Exefile.exe in the quarantine with menace IDP. For instance, under some circumstances reading memory backward with might seem like a buffer underflow attack to the heuristic algorithm. Haven’t had any issue today following the update, yet, but I had popups from Avast after the patch on Singularity on (Edit November 3rd), mainly anytime I would log off and quit for an account. You could also add the program launcher to your AVs exclusions. I chack it on VT but there is no engine detected. Update your virus definition and try launching again, as this is most definitely a false positive. 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. I have IDP.generic detection on game instaled via ubi luncher. The root issue here is that c++ game engines are built for performance and robustness is correctness. 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. Can be a rubbish can symbol (Windows delete type icon), but not necessarily automatic delete - rather brings up several options. Originally posted by Konstanty:It's not an issue, it's Avast mistaking code optimizations for malware/viruses. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |