logion

I did try the Remote button, but it didn't work either with the same error. The issue has been resolved now though.

Unfortunately your server is running v0.59 and Arma 3 refuses to connect. I have made some progress, I managed to setup a NAT rule that forwards the reverse leg back into my LAN. So now the tcpdumps look like this: LAN-side tcpdump: tcpdump host 82.73.34.xx -i vr0 21:48:24.131537 IP 192.168.1.35.2304 > 5xxxxx1E.cm-4-2a.dynamic.ziggo.nl.2302: UDP, length 20 21:48:24.144845 IP 5xxxxx1E.cm-4-2a.dynamic.ziggo.nl.2302 > 192.168.1.35.57901: UDP, length 20 21:48:24.145006 IP 192.168.1.35 > 5xxxxx1E.cm-4-2a.dynamic.ziggo.nl: ICMP 192.168.1.35 udp port 57901 unreachable, length 56 WAN-side tcpdump: tcpdump -i pppoe0 host 82.73.34.xx 21:48:24.131693 IP ip-81-11-172-xxx.dsl.scarlet.be.59818 > 5xxxxx1E.cm-4-2a.dynamic.ziggo.nl.2302: UDP, length 20 21:48:24.144694 IP 5xxxxx1E.cm-4-2a.dynamic.ziggo.nl.2302 > ip-81-11-172-xxx.dsl.scarlet.be.57901: UDP, length 20 21:48:24.145066 IP ip-81-11-172-xxx.dsl.scarlet.be > 5xxxxx1E.cm-4-2a.dynamic.ziggo.nl: ICMP ip-81-11-172-xxx.dsl.scarlet.be udp port 57901 unreachable, length 56 I've also noticed that the server's end isn't responding to ICMP echo requests(pings), so I'd guess the ICMP unreachable isn't arriving either. Also the in-game PING is listed as ? (which uses Gamespy's UDP ping I assume?). I didn't know that ICMPv4 was required to host an A3 server? ---------- Post added at 10:32 PM ---------- Previous post was at 09:52 PM ---------- It appeared this was the issue: http://kentie.net/article/m0n0wallgamespy/index.htm. Setting NAT to 'Manual Outbound NAT rule generation' in pfSense and choosing Static Port so that pfSense won't rewrite the outbound port fixed it. This is the same solution proposed as in http://feedback.arma3.com/view.php?id=2467 (i.e. the Static NAT); it's just a bit more cryptic to find in pfSense. I'm guessing the problem only arises with servers behind NAT which activates some kind of NAT penetration technique that doesn't play so nicely with dynamic NAT. Luckily I can set up a specific NAT rule per server (well actually per ipv4 subnet that server belongs too) so that I don't have to use static NAT for everything... Maybe using these kind of NAT penetrations techniques could be made optional, as they aren't needed when the server has setup its NAT rules correctly. Would love to get some feedback on this from the devs/community. It's clear in the above tcpdump that pfSense chooses 59818 as the outbound port in the dynamic NAT case; in the static NAT case it would probably use the 2304 port. The only question I'm asking myself i:, why does the server reply to a totally different port 57901? Is it somehow calculated from the first port? If so, it isn't a simple offset. It seems to me that the A3 server should just reply to the same port (i.e. 59818 and not 57901) and all would be well. I'm guessing when the game is running these kind of ports come into play (ports above 55000> and as these can be asymmetric I could imagine the different ports). But as this is the first connection attempt to the A3 server, the server shouldn't assume that my client has reached this state yet. I'm still convinced that this is bad design of the A3 server and nothing else.

Hi, I'm trying to connect to a home-run Arma 3 server by a friend, everyone else can manage to connect except me (that's 6 people connecting over public Internet vs me not managing to connect). I'm running pfSense on my router and I'm guessing this in combination with some exotic Arma 3 networking ideas is causing problems (I can successfully connect to a remote home-run DCS A-10C server (where the host is behind NAT as well) without any changes on my end). I ran tcpdump to inspect what kind of NAT is going on and it seems that asymmetric return leg is giving problems. Notice how 15250 in the server's answer differs from the NAT port my pfsense box chose, hence it doesn't know what to do with it and it is dropped... It could choose to translate it to my private IP (192.168.1.35) as it has seen the previous packet and guess that it's a reply to that packet. But I'm guessing pfSense isn't configured to do this by default. LAN-side tcpdump: tcpdump host 82.73.34.xx -i vr0 21:10:48.649089 IP 192.168.1.35.2304 > 5xxxxx.cm-4-2a.dynamic.ziggo.nl.2302: UDP, length 20 WAN-side tcpdump: tcpdump -i pppoe0 host 82.73.34.xx 21:10:48.649214 IP ip-81-11-172-xxx.dsl.scarlet.be.18425 > 5xxxxx.cm-4-2a.dynamic.ziggo.nl.2302: UDP, length 20 21:10:48.687891 IP 5xxxxx.cm-4-2a.dynamic.ziggo.nl.2302 > ip-81-11-172-xxx.dsl.scarlet.be.15250: UDP, length 20 I am aware of this ticket: http://feedback.arma3.com/view.php?id=2467 and tried to alter my pfSense NAT accordingly but I can't seem to get it to work. I'm wondering why the A3 server-instance doesn't reply to the same port? It just seems to choose a random port to reply to every time; which makes setting up NAT rules particularly difficult. For some reason I can connect to some of the publicly available servers, I'm guessing these a) aren't behind NAT or b) reply to the open port on the NAT. Regards, logion

Thx! It works now. Your last comment isn't entirely true, as MOUSE5 did register while other keys didn't. Thanks again.

I'm having an issue with ACRE blocking my push to talk key. When i set my PPT to accent grave (above TAB) and start TS3, it works fine. As soon as I join an ACRE-enabled server or as I enable the plugin manually my hot key stops working. My ACRE hotkey is set to CAPS LOCK, so they shouldn't conflict. When I set my TS PPT to an other key (e.g. MOUSE 5), then everything works as expected. However, I prefer to use accent grave instead. I've added some log/config files below, but I can't find any suspicious. Note that the keycode for accent grave (41) is not in acre_keys.hpp * AppData\Roaming\TS3Client\acre_config * AppData\Roaming\TS3Client\logs\ts3client_2013-02-01__22_36_34.993245 * C:\Program Files\TeamSpeak 3 Client\acre * C:\Program Files\TeamSpeak 3 Client\acre_keys.hpp * C:\Program Files\Bohemia Interactive\ArmA 2\userconfig\acre\acre_clientside_config.hpp I had the same setup on my previous OS install with largely the same hardware and it worked flawlessly. Now I've added a new SSD, external monitor and new azerty external keyboard (used my onboard laptop UK qwerty keyboard before) and reinstalled windows+drivers+all software and it stopped working. When I switch back to my laptop keyboard, the problem persists. I am running an other audio driver however, might this be causing the issue? I don't see how it could affect a key setting? I'm running REALTEK HD audio driver v6.0.1.5910, can't remember what I was running before... Any ideas/suggestions?

You can rewind the stream on gamespot, it starts around 44:30 http://e3.gamespot.com/live-cam-tour/live-cam-day-1/

I have not tried the latest beta patch, does it allow to be installed next to v1.05? Because from time to time I play online with a few mates and they don't have the beta patch installed. Or isn't there an issue in mixing versions?

I play with : reso 1920x1080 visibility 1600m AA & AF : low terrain detail, texture detail, shadow detail, object detail: normal post procsessing: low This makes it playable for me but don't expect a consistent 30fps+

I own a Clevo W860cu/Sager NPNP8690 with the following hardware: CPU: Intel Core i7-720QM GPU: ATi Mobility Radeon HD 5870 1GB GDDR5 RAM: 4GB DDR3 HDD: 320GB (7200rpm) OS: Windows 7 64bit Professional Screen: 15.6" Full HD at 1920x1080 I've run some benchmarks at these setting: Results from the first ingame benchmark(labeled Benchmark1 under SP missions): Results from the second ingame benchmark(labeled Benchmark2 under SP missions): Results from benchmarking tool named Arma2 FPS Analyser: All benchmarks were run with the latest official arma2 patch(1.05). edit: if you have any specific benchmark request, post them and I'll see what I can do ---------- Post added at 10:17 AM ---------- Previous post was at 10:08 AM ---------- I should mention that those arma2 fps analyser benchmarks aren't that representable for a normal gaming situation. They consist of camera fly bys through waypoints. I guess they would only be a good comparison when you're piloting high speed aircrafts.

Also having troubles with the BRDM. When the air support comes flying in it's under heavy fire because of the BRDM. I've never seen the chopper, I just hear it approaching but he doesn't make it to the BRDM due to enemy fire.(it never goes down though) Maybe I could try distracting it by providing suppresive fire untill the chopper arrives? Any other ideas?

I bought a 5850 unknowing that ATI isn't planning on releasing their drivers for windows XP. I found the folowing drivers however: http://downloads.guru3d.com/ATI-Catalyst-9.10-Beta--Windows-XP-%2832|64%29-download-2389.html It works ok, but I suggest switching to windows 7 in the near future because I believe that the drivers for Windows 7 will be better than those for XP and that this will make the balance tilt in favor of windows 7 performance wise.

Great guide, Daniel. Might I ask how you estimated the range while testing? The editor seems to lack a distance measurement tool, I could use the squares on the map but that only works well for horizontal/vertical directions. Also, is it possible to fire tracer rounds with every weapon ingame? So far I've only managed to shoot off tracers with a machinegun allthough tracer ammunition is enabled under difficulty settings. cheers

My current squad isn't all that active at the moment. So I'm up for some co-op on the side :) edit : xfire : logion

Offtopic: @PJ[CZ] did you notice a big difference in performance after switching to the 260 GTX from the 8800 GTS? Thanks in advance

Has anyone tried arma2 on the core i5 750(socket 1156)? It should be as fast as the core i7 920(socket 1366) when it comes to arma but I'd like to see some benchmarks proving that first...