Lokyi

no grass = haxxors. I'm only running a 6870, and have no problems with grass and framerate TBH. You'll find most clientside framerate issues are actually caused by sub-30 FPS on the server.

Yeah, clients on the LAN side should be able to use the LAN IP from memory, because if you're trying to use the WAN IP you're going to get port conflicts.

Terox pretty much nailed it. If you're so worried about it, at least auto-start with one mission. Remember, this is an Alpha, not a full-blown release. There's a lot of stuff missing at the moment, but we're here to TEST stuff, not treat it like the full game has just been released.

Yeah, Powershell is baus once you learn how to use it. Can do pretty much everything via script without having to RDC.

We're running the equivalent of what they call an EX6. i7-920's are getting pretty old now =P It should still work fine for a server box though. No idea on hosts in EU though, sorry!

First port of call... your MPMissions folder. Most of the missions coming out at the moment are absolute rubbish. Most are ports of stuff from Arma2 and throw up so many errors it's ridiculous. A lot of AI features at the moment aren't implemented properly either, so the server is running harder than it needs to.

^^^This. If it's accidental and they apologise, no issue. If they keep doing it and don't say boo.... bye bye.

It is, after all, an Alpha. Deal with.

You don't as it is, unless you add some line in there to keep adding a number each time it runs the start section... but that's beyond me lol

Yea I just noticed that too. It's reportingIP="arma3.master.gamespy.com";

...because it's still only a 32-bit process, it won't address that much memory. Your script is win though, have been running it since I saw it on one of the other threads earlier.

Dodgey mission.

sometimes it doesn't come up in chat that you have successfully logged in, particularly in the lobby.

Where's the "high five" button Dwarden? It's refreshing to see some heads-up information getting posted on the forums for once :cool: Top work, keep it up.

As per every other server thread about performance... It's not the server, it's the missions.

THIS. Is fscking brilliant dude. Just put it on our server and it works perfectly. 10 out of 10.

Of course you can run dedi's, you just need Steam on the box and a purchased copy of the game. If you read all the other threads, you'll find there's no dedicated server exe available yet, you just have to force the game exe into server mode with the -server command. Thinking you know a thing or two, and actually knowing a thing or two are completely different things :p

Problem with crash reports is that I've found most of them are mission related, not server related. Make sure you're actually looking at the RPT file to see what went wrong. Also at the moment as dedicated server exe isn't released you'll have more problems than normal. Dedicated server handles crashes/errors a lot more gracefully than forcing the game exe into server mode. Usually if you have a crash with dedi is has to be pretty severe to kill the process, most errors will just dump it back to lobby.

This should not be possible, a default dedicated server actually uses 3 ports: 2302, 2303, 2305. For safety, I always space mine out by ~ 10 ports anyway, and I've set our Arma3 server up using 3302.

The server RPT files are in the hidden Appdata/Arma3 folder. There's a thread somewhere on the DirectX issue, but I don't think it's a guaranteed workaround.

Server performance is severely affected by the missions more than anything else now. Check your RPT file in the (hidden) User\username\Appdata\Arma3 folder. Nearly all the missions I've seen run so far chuck up so many errors it's not funny. Simple TvT missions you should get at least that many players without any issues at all. It also depends how may AI you're putting in the mission, too many and you'll bring it to a grinding halt very quickly.

I've found most crashes so far are caused by sh*tty missions more than anything else. Even bad missions just sitting in the MPMissions folder and not actually running can cause crashes on server startup. Is it happening after a mission is actually started, or a short while after the server is started but sitting at lobby?

This issue has always been contentious, so there's always going to be love/hate arguments. The basic thing even with Arma2 on Steam, it's NOT necessarily a matter of just getting it and modding it and playing it, we've spent countless hours with some of our guys just trying to get them running mods correctly so that they can play with us. Everyone is entitled to their own opinion on using Steam, however, like I stated earlier and was misquoted, I would like BIS to let us know how Arma3 is going to handle mods using Steam, and dedicated servers. I don't want the opinion of some clown who doesn't know the facts, I just want... the facts.

Most noobs to Arma play DayZ, now that's a fact. They don't use ACE or other mods. My biggest gripe is that Arma is going to think they're the next CoD or Battlefield which sadly it isn't. What Arma has always been about is modding, which by moving to Steam, is most probably going to stamp all over. I'd like to see this issue addressed; how is a Steam distribution of Arma going to handle mods? Because unless Arma somehow includes ACE features in release, then vanilla is probably going to suck balls. Vanilla Arma audio sucked, hence JSRS, ACE_SM etc. Vanilla effects suck, hence WarFX. Also interested to see what Shacktak have to say as well.

What's with the new update on Six making "_new" now obsolete?