Every time I try to launch Boundless from Steam, it gives an error Fatal error 34, I can only press OK and then it closes. So far, I’ve exited and relaunched steam, restarted my computer, reverted changes to Boundless, uninstalled, and reinstalled, lastly I have uninstalled and reinstalled Steam. I can launch it outside of Steam just fine, no error, except that it won’t connect to servers. The only thing that has changed was that I recently loaded it from a different computer, and that computer still launches it just fine. But, when I exit Steam and try again on my desktop, same error. There is nothing recent in the logs file within the Boundless directory on my PC.
What does error 34 mean to begin with? This is a vague error response just giving us a number with absolutely 0 information as to what that number means.
@vdragon My antivirus was exactly what it was. I had disabled a portion of it, but it was still containing the launch without prompting me, which is odd because this happened out of nowhere. Oh well, that worked. Thank you!
@SephirothWS I agree, more information about what the error number meant would have been useful (but, that was all the information I was presented with), and google did not provide any more details. Hopefully, if anyone else runs into this issue, they’ll be able to find this thread.
This is definitely related to Avast. I just had it happen to me again (and I have had it occur a few times when switching between live and test in the past).
Avast detects changes in the executable file and prevents the game from launching the first time around. I added Boundless.exe as an exception to prevent it happening again.
its to do with a change in the exe (avg does the same)
but since it has been added to the safe list on avast (avg is part of avast)
it might give you an error now while the exe file gets automatically compared to the one in stored by them and they just replace it and it will just start up after
