http://bugs.winehq.org/show_bug.cgi?id=29168
--- Comment #26 from Erik Weatherwax erik.weatherwax@gmail.com 2011-12-15 10:49:24 CST --- (In reply to comment #25)
I narrowed it down to a networking issue with winsock, but I have no idea what since there are absolutely no FIXMEs/warnings related to networking.
Using wireshark I can tell that the game connects to the server for 30-60 seconds then disconnects and leaves that loading screen on.
On windows 7 (using vmware) it connects fine and I was able to play for 6 hours without any problems, the only problem was having 10 fps on lowest settings but that's expected from vmware I suppose.
So it *is* in wine's networking code, I just have no idea how to pinpoint it.
Thanks for the confirmation, Ahmed. I just noticed the same thing (well, noticed an outbound TCP connection to an EA server in netstat) whereas in the past betas I never saw any outbound connection attempt to EA -- so that's an improvement, I guess?
Might I ask what version of vmware you're using? I use VirtualBox for my virtualization at home, but it usually chokes on any attempt to play modern games, even with the "experimental" 3d support.