Hello fellow ArmA fans, I have a big problem.
After the new update (containing "multiplayer optimalization"++) for Arma 3 here the other day i have not been able to stable get in to the multiplayer serverbrowser nor servers.
I own the "Digital Deluxe Edition" pre-ordered through Steam at pre-alpha stage. Singelplayer works just fine, but this is not why I bought the game and built my desktop-computer.
I have played 300 hours of Arma 3 since the alpha, and has not encountered any problems until now, and I am really frustrated. It seems that I have tried everything.
Description
Details
- Legacy ID
- 2873334189
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Always
- Category
- Multiplayer
- When I launch the game and press "Play">"Multiplayer" to get to the serverbrowser it freezes, and after a while Windows comes up with "Arma3.exe has stopped working" without any form for information on what's wrong. This happends approx. 3/4 times i try.
- IF I at all get in to the browser at all and try to connect to a server (any mission or host), Arma3 comes with "Connecting failed" error and brings me back to the serverbrowser. This happends more frequent than nr.1.
- If I get to connect to a server, Battleye kicks me with "Battleye not responding" and brings me back to server browser. When I connect to the server Battleye initializes and lets me know that i have the latest one and wich version it is and that it is communication OK with the server. This happends as frequent as nr.2.
- If I get to connect and play without battleye kick, it lets me play for a while (random time) and then the game freezes completely and I have to end the arma3.exe process through task manager. It says in task manager that arma3.exe is "Not responding" This does not happend so frequently, but that is just becouse i rearly get to connect and play. But happends EVERY time i connect to a server.
This is what I've tried to solve:
- Google.com
- arma3.com
- Updated all my drivers.
- Updated Windows to all the latest.
- Verified my gamefiles trough Steam.
- Un- and reinstalled the game.
- Un- and reinstalled Steam.
- reinstalled the game again.
- Verified the gamefiles trough Steam again.
- Downloaded BEClient.dll directly from Battleye's pages.
- Deleted the profile files in Documents.
- Formated the SSD disk Arma 3 and Steam is on.
- Reinstalled Steam again.
- Reinstalled the game again.
- Downloaded BEClient.dll directly from Battleye's pages again.
- Verified the gamefiles throug Steam yet again.
- Tried devbuild.
- Went back to normal build.
- bistudio.com
- Tried unsubscribing two content subscriptions from Steam workshop.
- Tried deleting files in "user/appdata/local/arma3/mpmissioncache/"
- Un- and reinstalled the game after unsubscribing from Steam workshop content.
Event Timeline
Hello,
Are you still experiencing the issue?
If so, we need dxdiag and files from this folder for solve your problem. C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package please?
When package will be smaller than 5000k, you can attach it here. When package is bigger, please use some free sharing service and post link here.
How find correct crashdump file:
Play until you will have this crash
Look into crashdump folder
Upload crashdump with latest date in name (crashdump is rpt + bidmp + mdmp file with same name)
Thank you.
I have very similar issue. It started with arma2 around second half 2012 and A3 early 2014. Before this time B.E. protected servers worked fine. I have been trying to resolve issue with Bastion at B.E. with no luck. During this time I have had same router, I might try a new one soon.
The A3FT is more a bug tracker, not a support platform.
I suggest you rather open a forum thread in the BI Arma 3 Troubleshooting forums (http://forums.bistudio.com). You may of course link to the ticket here.
Thanks Fireball, your very right. As I said, I was receiving support, and have already tried the forums and continue too.
I was giving feedback as to when (Q3 2012 and Q1 2014) something was applied to A3 that was applied to A2, that broke it.
If you think it's your router (which seems very plausible to me), please review this ticket: #2467.