sobrek

Just got ARMA 3 yesterday and installed this morning, and got to wonder a bit. I have a TV as main screen and a monitor as second screen. I'm accustomed to have TeamSpec, IRC and such thins running on the second screen so I can see what's happening there. And now, I start ARMA 3, and the second screen goes black. So far I don't see any option to set something up. This is a total show stopper for me and currently annoys me big time.

Just one tiny little question: is there a linux server? Back then that used to be no problem.

Sorry, I'm feeling a bit blind, but, is there no non-BAF Takistan version?

Is there anything known about incompatibilities to linux servers? We tried to try Insurgency yesterday, but, several times i lost my admin control on the server and had to reconnect to end the mission, didn't see any other player, and the opponents needed big numbers of hits to die finally. There was no desync reported, and I don't experience that kind of things with other missions.

It's not a general problem. What made it look very illogical was, I was the only one who had it with that server, and others could play. On the other hand I could join others, so it is a very specific problem to my route. The alternative connection was a mobile phone with 3g connection, which unfortunately had the same problem. No I could not swap to other missions. That resulted in the same packets and the same problem. ArmA2 also just crashed in most cases when I tried to join a running mission.

There is no saving, but I found some workarounds, since join-in-progress works since ArmA 1. If you are hosting on a Windows machine, you could hibernate it and restart it if you want to continue. If you are runinng a linux dedicated hosted somewhere, you can suspend and continue the server process with # kill -Stop #pid # kill -Cont #pid As default, you find the process id in the 2302.pid file.

The command is in my case ifconfig venet0:0 mtu 1464 but making the change persistant needs a change in the / etc/ network/ interfaces.template Didn't have the time to figure that out completly. For the moment, every change I make to that template, renders the machine unreachable externally :< /e ok, just fixed it, added the following to the template (replace the xx with the correct IP, the values for address and netmask can be identified with ifconfig before): auto venet0:0 iface venet0:0 inet static address xx.xxx.xx.xxx netmask 255.255.255.255 mtu 1464

Thanks, but no, that's not the problem (can't change the value even as root though). It already happens on strictly vanilla arma 2, and apparently other people dont have any problem on the server. Today, I added a 3rd machine. Have an older Win Vista box, acting as a tv set normally... Only Windows installed, and ArmA 2. Shows the same behavior. "wait for host at any other mission". I was tracing a bit with wireshark then. First with my local server, then on both, the internet linux box and the game machine. Seems the first part of the mission header is going to nirvana somewhere, the server sends it but my client does not receive id. Would explain why it downloads the mission file for running missions ever and ever again. The missing part: Could be an MTU problem. This header part packet is 1506 bytes long. Almost sure that is too much. ---------- Post added at 07:48 PM ---------- Previous post was at 07:20 PM ---------- It was the MTU. Reduced it to 1464 on the serverside and now it's working again. The cause must have been the bigger header packets with more complex missions, that was why only Deathmatch worked.

After other people played over the week, it looks like the server is running for them. But what can I do? No suggestions left?

Newest update; the guys who still can play on my server tell me, the AI is acting really strange. Also it looks like only parts of it spawn in the EVO. And if I connect, it dowloads the mission file every single time again. Althouh it locally exists. With identical checksum. For myself, I can join foreign servers. No problems like this there with anything.

Server has been set up again with the previous default OS (ubuntu), reinstalled ArmA2 server, removed my local ArmA profile, nothing changed. Still can only start deathmatch, everything else does not go further than briefing or cannot be started at all. Talking about builtin missions... /e Double check all file/folder names are lower case. <<-- tolower executed byinstall after upload, worked, but checked countless times. Check permissions on missions files in mpmissions folder. <<-- nothing in mpmissions - everything set up and unpacked using the server user. ---------- Post added at 08:33 PM ---------- Previous post was at 08:10 PM ---------- Just let a friend select a mission. It started. I still couldn't connect, he could play. Now I don't understand anything anymore. Can't be my connection, I tried in another city during the week. Can't be my computer, as the gaming machine and the notebook don't have anything in common except for both are using Windows 7, but one 32bit and one 64bit. Different profiles. Different installations. Installed the game again. What elso should I do? :(

No mods were ever in use on the server or the notebook installation. Removed the whole ArmA2 folder locally before reinstalling, then crosschecked the contents with the server and compared md5 sums of the addons files. Uninstall only was available for OA, did that before. An I didn't reinstall OA so far. Currently I'm pushing the addons folder content over to my web space; will order a reinstall of the linux box after backup is complete.

Done a fresh install and patch 1.07 - nothing new. Can't start anything except deathmatch.

Maybe posting this into another thread with a slightly different issue was not a good idea at first ... However, problem still exists and I'm helpless as it looks.

After I was on a business trip during the week, I now have set up a complete parallel installation under a new user on the linux machine. I was using only the server files from the download, without anything of my usual changes. It still does not work either way. There are two missions I can choose, that's Deathmatch and Close Quarters Battle, all other builtin missions show the same "wait for host" issue. And Close Quarters Battle lets me start it, but not join it. It hangs up with no error or anything else bevor it should switch to 1st person view from the starting map view. So the one and only mission working is Deathmatch. I also tried another player profile (useless, as the error occurs regardless which of my computers I use), and I tried another network connection, without any success. -exthreads=1 does not help either. During this "wait for host" I still can login and logout as admin, the server logs this, but neither #missions nor #reassign do anything. #shutdown works, but does not really help... I'm completely out of ideas. Is cancelling the server all that's left now?