General Category > The Last Federation

For those who use AVAST or similar, and had it killing TLF, how did you fix it?

(1/5) > >>

x4000:
There are some other folks running into issues of the same sort, and I recall that some of the alpha testers said "after fiddling with AVAST for a bit it worked" or something to that effect.  Other forums for unity games have some players where they are just having to completely uninstall AVAST because even adding an exception for the game in question wasn't working.  For those who solved the issue, can you enlighten the others of us?  ;D

Other Solutions To Crashes:
------------------------------------------

From Here: http://www.arcengames.com/mantisbt/view.php?id=14308

"I have managed to get the game to run now. I read several people post similar issues in some other unity games, and a common thread seemed to be that people still on Vista could run the game. I launched the game from the app folder in Steam, and set it to run in Vista Compatibility mode, and am able to play it just fine. (Windows 8.1 machine) "

There is also a whole long list of things to try in that same thread: http://www.arcengames.com/mantisbt/view.php?id=14308

And in particular, some great things from Kerbal Space Program: http://forum.kerbalspaceprogram.com/threads/24536-Self-help-for-crashes-look-here-first-if-KSP-crashes

From Red_Machine on the Steam forums:
"Another Unity Engine game (Guns of Icarus Onlone) is having the same problem now. It used to work fine, but I tried launching it just now and it crashes in exactly the same way."
"No worries now, turns out Stardock's WindowBlinds was conflicting with it. Disabling it allows me to run Unity-based games."

topper:
I have Avast Free Antivirus

Starting from the alpha, the game would crash during initialization every time. (sometimes immediate black screen, sometimes it would get a few steps of initialization complete). When I would use Steam to "verify integrity of the game cache" after these crashes, it would consistently need to redownload at least one file.

I added C:\Program Files (x86)\Steam\steamapps\common\The Last Federation\ to the program exclusions and that worked through 0.862. After that alpha patch, the same problem as before showed up again.

I solved it that time by adding the entire C:\Program Files (x86)\Steam to the exlusions list for the file shield. What folders does the game access other than
C:\Program Files (x86)\Steam\steamapps\common\The Last Federation\ ? I would rather have a smaller list of exclusions.

How to add exclusions:
Under settings, for file shield, see the second image in the below link:
http://en.kioskea.net/faq/12294-avast-internet-security-create-an-exclusion
Make sure you verify your Steam cache for the game after doing this!

I might have changed a few other Avast settings too related to deep scanning, but this is the one I can remember for the moment that is repeatable going from "game will not load" to "loads fine".

x4000:
Thank you for the update there!  Two notes:

1. The one file that Steam always has to re-download when verifying the cache is just a log file, it's harmless.  There will always be one file, but no more.

2. I have no idea why it would have to include the whole steam folder, that's a bit odd... sort of.  TLF doesn't use anything directly from any of those other folders at all -- everything is within its own folder, and it doesn't even put settings elsewhere.  However, Steam itself does inject itself into the TLF process via adding some threads in there (so that you get the steam overlay, etc).  It's possible that Avast was also objecting to that.

topper:

--- Quote from: x4000 on April 22, 2014, 03:20:23 pm ---2. I have no idea why it would have to include the whole steam folder, that's a bit odd... sort of.  TLF doesn't use anything directly from any of those other folders at all -- everything is within its own folder, and it doesn't even put settings elsewhere.  However, Steam itself does inject itself into the TLF process via adding some threads in there (so that you get the steam overlay, etc).  It's possible that Avast was also objecting to that.

--- End quote ---
I was mostly just wondering if there were any other subfolders of Steam that might be affected by game files. It was strange that the game was fine pre .862 with only its own folder on the exclusions list. I did not bother to try anything else other than adding the top folder for Steam to make it work after .862. I might try some other things when I have time, to narrow down where the problem is coming from.

x4000:
Makes good sense.  And I'm really not sure of what we could have changed in an alpha version that would cause it to need more permissions outside of its own folder -- it really doesn't do anything out there of its own accord, there aren't any files out there.

Navigation

[0] Message Index

[#] Next page