soldia 1 Posted November 21, 2012 Hello Folks, yesterday I wanted to start a LAN MP Game with a friend of mine via Hamachi (correctly set-up and working). So we first updated to the latest beta (99202) and started with @ACE + @jsrs. I hosted a server but my friend wasn't able to see my game, neither automatically nor via "remote". Same situation the other way round, couldn't see his game myself. The next step was to deactivate the beta and mods and to start with simple Arma2:CO. With this config on both sides it works flawlessly. We tested a few different configs and came to the conclusion that the beta patch was the root cause for our problem. We tested with other beta versions as well, but that didn't help. To conclude: Working with 1.62 Working with 1.62 + @ACE Working with 1.62 + @ACE and other mods Not working with 1.62 + beta Not working with 1.62 + beta + mods Used game version: ArmaX (non-steam) on my friends side and Arma:CO (Steam) on my side. Is this problem obvious (crossread the changelog) and I am not able to see it? Thank you for your help Share this post Link to post Share on other sites
maddogx 13 Posted November 21, 2012 No, the cause for the problem is not obvious. Some questions: - How exactly are you launching the beta? (Which command line parameters?) - Have you tried (temporarily) disabling all firewalls and AV software to see if it helps? - Is Hamachi really necessary? Why not host over the internet with a password? Share this post Link to post Share on other sites
soldia 1 Posted November 21, 2012 Hi MadDogX, - I tried to start the beta on several ways. Via the beta-exe directly ("expansion/beta"), via the predefined link in the Arma2:OA install folder and via ArmaIILauncher (spirited_machine). I can provide the explicit command line this evening. - Firewall is not disabled, but Arma has all rights, but I'll give it a try. AV software...never had some sort of "slow_my_machine_down" SW installed :rolleyes: - Hamachi is not really necessary but a great relief. Sitting behind two switches/router and portforwarding isn't stable sometimes. But we can give it a try. Just curious why it works without beta and refuses to display the server with beta version installed. I will try to play around a little bit with the configurations of game and system and provide some feedback on this. Share this post Link to post Share on other sites
soldia 1 Posted November 21, 2012 Ok, the command line parameters are: Without beta "-mod=E:\Games\Steam\SteamApps\common\Arma 2;Expansion;ca" "-name=Soldia" -nosplash With beta "-mod=E:\Games\Steam\SteamApps\common\Arma 2;Expansion;ca;Expansion\beta;Expansion\beta\Expansion" "-name=Soldia" -nosplash (weird: the space is NOT included, just in the final post. Cannot edit) Share this post Link to post Share on other sites
Vixente 10 Posted November 21, 2012 May it be because when you select LAN recent betas disregard any server that has an uncommon high ping for a LAN connection? Let's say 60-90 ms. But another thing may be that the beta is not getting the correct server.cfg. When you launch a server you should specify which server.cfg to run. In that file there is a line that tells the executable where to publish that server. reportingIP="arma2pc.master.gamespy.com"; My server shortcut with some isles (in windows) looks like this: "-mod=Expansion\beta;Expansion\beta\Expansion;@cba;@lingor;@cba_a2;@cba_oa;@dingor;@mad_build;@mad_resh;@duala" -config=server.cfg -exthread=1 server.cfg is in my E:\Arma 2 folder but the beta exe actually "knows" that the A2 root directory is E:\Arma 2. Share this post Link to post Share on other sites
soldia 1 Posted November 22, 2012 May it be because when you select LAN recent betas disregard any server that has an uncommon high ping for a LAN connection? Let's say 60-90 ms. May be, but when starting a game without beta the ping is around 25-35 ms. Same thing when pinging the other side via hamachi (23-32ms). But another thing may be that the beta is not getting the correct server.cfg. When you launch a server you should specify which server.cfg to run. In that file there is a line that tells the executable where to publish that server. My server shortcut with some isles (in windows) looks like this: server.cfg is in my E:\Arma 2 folder but the beta exe actually "knows" that the A2 root directory is E:\Arma 2. Good hint, thx. Will check the config and line command parameters. But the config will not change when using beta, right? Share this post Link to post Share on other sites
soldia 1 Posted November 24, 2012 server.cfg makes no difference. Tested to host via Internet and it works fine. Seems to be the best way. Thx for your help Share this post Link to post Share on other sites