Thank you Vanguard for the log translation
Vanguard wrote:Is your forever log complete, or did you prune it?
The log is complete, the archive was created with all my logs folder content plus the exception text.
Vanguard wrote:You have a Boatload of "bottleneck" messages in there indicating that your network performance is really bad, but I cannot see, in the logfile, at which time the game started.
...
What you should try to do is to go through the trouble of setting up a fixed port forwarding for the FAF ports needed.
The FAF Wiki should be able to help you with that:
http://wiki.faforever.com/index.php?tit ... _solutions
My ISP uses wireless connections to cover my area and is doing some hardware upgrades on his antennas. Due to these upgrades, my network performances suffers heavy performance drops in some timeslots.
However adding the port forward and disabling UPNP solved part of my problems! My game always hanged/crashed at the exit probably because of the UPNP issue. My router is a TP-Link and probably the UPNP implementation is somehow buggy
Vanguard wrote:Edit: Rereading your post, you said "also in LAN". Did any of you guys install maybe a personal firewall software or upgrade their Operating systems software? Windows has it´s own firewall rules and maybe something is off there?
We already add rules to windows firewall in order to permit FAF executable's traffic in all the possible ways on all machines. With FAF executables I meant "C:\ProgramData\FAForever\bin\ForgedAlliance.exe", "C:\Program Files (x86)\Forged Alliance Forever\FAForever.exe" and "C:\Program Files (x86)\Steam\steamapps\common\Supreme Commander Forged Alliance\bin\SupremeCommander.exe".
Vanguard wrote:Also, LAN - if you are using FAF, your connection should still go over the internet, as far as I know. This just means, if you meet your friends at the same location, the internet of the location is the problem.
You should test if you disconnect from a public game without any of your friends and your friends should do the same ( from their home location, not at the LAN place ). If all but you stay in game, the problem is on your machine/connection. This way you can at least start searching for the problem.
As I wrote, also the LAN game (all machines phisically on the same room) presented the crash after 20/30 minutes. When we play in LAN we use only the FAF copy of the game ("C:\ProgramData\FAForever\bin\ForgedAlliance.exe") without the FAF client running. This way the client is able to find lan games, however we also tryed to directly connect all clients through the server LAN IP. Unfortunately, playing this way, no logs were written into the logs folder.
Anyway I've done a fresh install of the whole game (steam game, FAF client and the FAF copy of the game) using all the default folders on C drive. I found some posts on the forum about issues caused by game and client installed in non standard paths but my files were all on D drive.
Vanguard wrote:Edit: If I am online in FAF, you can send me a chat message and I will stay with you in game for 30 minutes, to see if you disconnect from me. I have a very stable connection usually.
Thank you for your proposal, but on weekdays I have very little time to dedicate to FAF testing and this weekend, me and my friends will probably meet all toghether and try some more LAN games (from the same room). I hope the fresh install helps!
I'll return with our results next week.