Windows users can't connect to lobby!

[SpookyMarathon]

I have been using the 1.3b2 version of Aleph for lots of things and its been great! Thanks for the update. Wrk told me not to assume that devs knew about problems but considering how major this one is I thought you would know. So here I am reporting it a bit late.

When I am setting up Windows users machines by remote the new Aleph works great for things like controller settings integration but freezes and crashes when trying to join the lobby. I cant remember getting much of an error message out of it but it is easily replicable.

Thanks for all of your contributions to the Marathon community!

[Hopper262]

I was unaware of this issue. Even if it is discussed elsewhere, GitHub is our best way to keep problems organized and visible, so your report is extremely helpful!

[SpookyMarathon]

Thanks Hopper nice to meet you. Long time fan.

[treellama]

There's a chance this is the Windows firewall spawning a window asking for control. Are you running full screen, and have you ever accepted the firewall settings for Aleph One on that computer before?

What happens if you try switching to windowed mode (alt-enter) before connecting?

[SpookyMarathon]

I don't use windows myself but I will remotely connect to the person who's computer I was helping with and check and get back to you. Cheers.

[raptor200221]

I can attest that the latest beta of aleph one will not connect to the lobby on windows, or, at least windows 10. Even if you put it in windowed mode, it will not work. It is not the firewall either. Even if you run it in administrator mode, it will not connect to the network. This is a pretty big issue, considering that most people on windows are using the latest beta for controller support.

[ccallahan]

I can confirm that the bug is present in the latest successful nightly (A1-XMCP-7). The error that is shown is "There is a problem connecting to the server that tracks Internet games. Please try again later (error 0)". I'm attaching a screenshot along with an Wireshark dump. I don't know enough about networking to make much sense out of it, but there is probably someone smarter than me here who can figure it out. =)

Documents.zip

[treellama]

This is probably a build issue. 1.3b2 doesn't work, but my own build of git master connects just fine.

[ccallahan]

Did you try on Windows or something else? Maybe it's a Windows-being-silly kinda glitch?

[treellama]

Windows 10

[ccallahan]

It might be Windows Firewall and Co being stupid then, give me an hour or two to wake up then I'll go look.

On Fri, Mar 15, 2019 at 8:53 AM Gregory Smith notifications@github.com wrote:

Windows 10

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Aleph-One-Marathon/alephone/issues/142#issuecomment-473274336, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQEZYvSU5LA0Z0C1XcuX861khLayNbLks5vW5fIgaJpZM4aR-g6 .

-- Chance Callahan Discord: hyp3rdriv3#7326 Reddit: hyp3rdriv3 Amateur Radio: KD0MXN General Mobile Radio: WQYN309 Have a nice day!

[SpookyMarathon]

Thanks for looking after this issue sorry I can't be of more help I'm not a Windows user myself.

Kindest Regards, Spooky

[Hopper262]

Like Treellama, I can replicate the issue with 1.3b2 (which I built), but not with a new build after I upgraded and rebuilt MXE (the Windows build environment). @ccallahan can you try building with https://github.com/Hopper262/mxe and see if you get different results?

[ccallahan]

Yeah, I'll try it in the morning. I'll keep you posted.

On Sat, Mar 16, 2019 at 9:55 PM Jeremiah Morris notifications@github.com wrote:

Like Treellama, I can replicate the issue with 1.3b2 (which I built), but not with a new build after I upgraded and rebuilt MXE (the Windows build environment). @ccallahan https://github.com/ccallahan can you try building with https://github.com/Hopper262/mxe and see if you get different results?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aleph-One-Marathon/alephone/issues/142#issuecomment-473608405, or mute the thread https://github.com/notifications/unsubscribe-auth/AAQEZZRm_IVVkkqUtexzSZt2Vtg7en6kks5vXaB4gaJpZM4aR-g6 .

-- Chance Callahan Discord: hyp3rdriv3#7326 Reddit: hyp3rdriv3 Amateur Radio: KD0MXN General Mobile Radio: WQYN309 Have a nice day!

[ccallahan]

Sorry about the delay, I got slammed at work. Recompiling MXE has fixed it, builds are passing now. Thanks!

[ccallahan]

In regards to the multiplayer issues, it is still present in the latest build from our Bamboo.

[Hopper262]

@ccallahan I just downloaded and tested your latest builds. On my machine, the 64-bit gave the network error but the 32-bit connected to the lobby. My own build is 32-bit.

[ccallahan]

Ah ha! I've been testing the 64 bit builds out of habit, so that explains the breakdown in comms we were having, though this does open a new can of worms. Any thoughts on what could be causing 64 bit to break but not 32?

[Hopper262]

No idea. Mac and Linux have been happily using 64-bit builds for years. It's consistent and not a problem specific to your Bamboo -- 64-bit builds on my Mac and Fedora machines both fail, while the 32-bit builds are fine.

[treellama]

I don't think this should block 1.3, since we don't distribute 64-bit Windows builds.

[ccallahan]

@Hopper262 Well, the builds appear to run just fine beside networking, but I haven't looked in depth. Tomorrow evening I can go through and get you a proper answer once the final parts come in to fix my rig.

@treellama I agree on not blocking, though it might want to be a goal for a future release of 1.3 or even 1.4 to fix this. I'll see if I can rope tbcr into helping me over the new few days figure out what is broken on 64-bit Windows and post it on our JIRA. May I email you a link once we have it together?

[raptor200221]

I can confirm that this issue is fixed now with the new beta 1.3b3