Multiplayer bug
Benjen
Member
in Bug Reports
I feel awful because I'm posting tons of bug reports, but for the past couple days (around the same time I tried switching to dx11, though this happens when I'm not on dx11), I've been unable to join multiplayer matches, and I assume this affects my ability to host as well, as nobody seems to be able to view my hosted games.
Whenever I try to enter a game lobby, the game shows this notification... and leaves it there until I close it, while failing to do anything else.
I'm on University wifi, so my speeds are pretty good, but I'm running steam on my MacOS so that could be a factor?
I'm fairly certain the Uni doesn't have any blocked pages or anything on their wifi, so I don't think the internet is the issue; I was able to play Civ V just fine with a friend the other night.
Whenever I try to enter a game lobby, the game shows this notification... and leaves it there until I close it, while failing to do anything else.
I'm on University wifi, so my speeds are pretty good, but I'm running steam on my MacOS so that could be a factor?
I'm fairly certain the Uni doesn't have any blocked pages or anything on their wifi, so I don't think the internet is the issue; I was able to play Civ V just fine with a friend the other night.
Comments
We appreciate the bug reports, don't you feel awful.
I think this is going to belong under help, rather than bug reports though.
First thing I would try is this article; https://sauropodstudio.zendesk.com/hc/en-us/articles/218389798-How-to-do-a-fresh-reinstall-of-Castle-Story-Crashes-Crash-
Let me know if that helps any. Don't use the DX11 build to test, by the way.
Conclusion: the issue is probably not related to my OS
How are you installing the game? Steam or Humble?
Don't switch to the DirectX branch on Mac, there is no DirectX on Mac.
I haven't tried to run DirectX11 on my Mac since September 7
I did use it on the Windows 10 partition through bootcamp, though, because that's not OS X, its Windows. That worked fine, except that the multiplayer issue I was encountering on my OS X (with and without DX 11, and after multiple reinstalls) persisted on the windows side as well - in and out of DX11 beta.