I’m trying to prep my game for final release on Steam, and I’ve found a few users who can’t run the game at all despite being able to run earlier versions. I’m not sure if its a 5.3 issue or if it was 5 in general, as my sample size is still small, but the issue is that the game just never loads (output_log.txt is never created) and there is no crash log either. I thought it might be a Steam issue, but I made these users custom non-steam builds and they have the same issue running it directly.
So… any ideas? It’s a tough one because I can’t repro it myself, and I can’t actually access any of the computers in question. I’ve given the users recommendations to follow (updating drivers, try safe-mode) and they have said none of it works, but the former-tech-support technician in me knows full well they may be lying or mistaken. Anyway, just curious if anyone has seen and resolved this problem before… a shot in the dark, I know
You were spot on (at least so far). Both users had Avast installed and if I install it and turn on “Hardened Mode” I get the same problem. Adding the game to the exclusions is a workaround (also worked for one of the two users who tried it, the other is going to try it this weekend), but its pretty lame that its happening at all. Would be nice if Unity could get on working with Avast to find some better solution.
Great - good to know. As mentioned in the other threads, Avast haven’t stated exactly why it’s happening (problem with main binary, supporting files, digital signatures, etc) and we never casually heard anything in the forums from Unity about it.
Our game is on Steam and sometimes Avast zombies the Steam process as well for some players which is pretty annoying. Our current solution is to manually submit our public builds to Avast for whitelisting (rather than ask players to manually exclude/whitelist the app themselves).
