Slitherine

Odd things are happening with the server.

Try to load a match and after one minute I cancel,
Try to load another, and the same.
Left the game for an hour or more then enter multiplayer and one of the matches is running the replay (no entered name and password to enter multiplayer, and no loaded nothing this time).
I do the turn, and when finished, the warning and then a crash.

Not had any other reports so I am guessing it was a local issue for you. Not sure what can have happened, though if there was some kind of weird caching happening at some stage and all the messages arrived in one go it would definitely have caused this kind of issue.

Cheers

Pip

ummmmm, now is working , now is not working, maybe it's my connection but no other issues with other app-connections.

When connected the MP page is showing empty for a while, then the lists are filled. (look at My Turn, Enemy Turn, etc.)

Maybe it's me but I reinstalled BA2 (this do not happens with BA1)
Of course, restart the MacOS.

The most often is that when open MP nothing its on the lists, later when the matches appears when I try to load one, it takes more than 1 minute and the cancel appears. I cancel, quit, open again and so on until the match loads normal...

I will ask the server team to take a look. I guess it could also be some change in the latest OSX updates that only affects BA2 because it uses newer libs than BA1 did. But it's pretty wierd. Have you tried deleting/renaming the BA2 folder in Documents/My Games to see if it is something that is cached etc.

Cheers

Pip

pipfromslitherine wrote:I will ask the server team to take a look. I guess it could also be some change in the latest OSX updates that only affects BA2 because it uses newer libs than BA1 did. But it's pretty wierd. Have you tried deleting/renaming the BA2 folder in Documents/My Games to see if it is something that is cached etc.

Cheers

Pip

Maybe it was the error.log now was 22.514.669 bytes (22,5 MB on disk)
Is not deleted by BA2 from time to time?, it seems too large.
The same file on BA1 is kept as a few bytes by BA1.

I deleted it and will take care on how it grows.

I may confirm you that error.log in BA2 is growing each time just opening and closing BA2.

Now that is odd. When it opens the error.log is tells the OS to start a new file. Maybe Yosemite has broken something in how it interfaces with Cocoa or the C runtime. I will take a look and see what is going on.

Cheers

Pip

pipfromslitherine wrote:Now that is odd. When it opens the error.log is tells the OS to start a new file. Maybe Yosemite has broken something in how it interfaces with Cocoa or the C runtime. I will take a look and see what is going on.

Cheers

Pip

As reference, BA1 works ok in Yosemite.
I have 10.10.2 (14C1510) running