Yes, that is excellent news indeed!  I was also wondering if there's an ETA for the next update build (either full release or beta) with all of these MacOS fixes.  I've also been holding off on starting any new games until then. (eagerly awaiting the release, that is! :-)

AmpliMath wrote:

Hi there,

The source of the issue has been found (thanks to your information on the port usage). We are working on a fix.

Cheers,

Great! Glad to be of service. Any word on the Diplomacy screen "spinning ball of death" issue? How about the missing text elements on various screens? Exit to Desktop? When can we expect an updated Mactesting binary? Kind of reluctant to engage game further with unresolved issues hampering play...

Hi there,

The source of the issue has been found (thanks to your information on the port usage). We are working on a fix.

Cheers,

I see a comment in Steam Discussions about an internal beta being tested that addresses the ports issue?

Mac shaders fix build still crashes regularly on my machine.

Many thanks to you and the dev's for your continued diligence and efforts supporting the MacOS community!

(I know I'm chiming in a bit late here, only just found time today for 1.0.36 testing and tech sppt forum browsing.)

Thank you for your help, tvleavitt (and welcome to the Games2Gether!)

I can confirm that 1.036 still has the bug, even when invoking the Diplomacy screen via the keyboard shortcut.

I downloaded the mactesting version mentioned in another thread, but I haven't had time to drive that particular instance to the point of engaging in diplomacy with another faction. I will let you know if I have the problem on that version as well.

Folks,

Thanks for the additional details. 

The final version 1.036 will be the same as preview version 1.036... because it is 1.036. It takes a long time to certify and make sure a version is correct, and 1.036 brings huge improvements for a few minor issues, so the preview test has revealed. 

But we are working on a preview for 1.037, and we need the DeviceID of your graphic cards to understand which systems cannot run the Diplomacy screen graphics.

Please expose the same kind of information that tvleavitt did.

Thanks!

Ah. Well FWIW when I access it via the Function keyboard shortcuts it hasn't crashed. Should be fixed either way though.

Hoping final release of .036 is more stable than the preview.

Just click on the top level Diplomacy icon. That's all that's required, on my computer, to induce the spinning wheel of death.

I can, as others have mentioned, engage in diplomacy by dealing directly with individual empires by clicking on their home planet. Which makes this a non-game breaking bug, in that you usually find an opponent's home planet pretty quickly once you come into contact with them. Would be nice to be able to do diplomacy more quickly though, obviously, as well as utilize whatever other functionality enabled via the inaccessible Diplomacy Overview interface.

Dear Mac users,

You  have reported several technical issues on the Mac version of ES2. Our big problem is that we do not reproduce these issues on our development system. We have reproduced some of those on partners Macs, but it is very tedious to work with on remote. 

Anyway, can you please let us know if you have remaining issues in 1.036. We have performed some fixes which could have a positive side effect on the issues you faced in the past. Also please try to run the game with the Fastest setting, we have removing some advanced rendering stuff when running in Fastest, and which could be the cause of your issues.

Thanks!

Here's Activity Monitor screencaps from an earlier crash... 274,000(!) ports! Some kind of loop in your IPC between threads?

Here's some hardware specs for my machine:

I can confirm that the Diplomacy bug persists in the new build, even on the "Fast" setting. It, however, doesn't kernel panic my machine or require anything other than a Force Quit to deal with. Here's a screencap of Activity Monitor as it was happening.

Folks,

Can you post again you Mac information, like it was done on this thread? 

https://www.games2gether.com/endless-space-2/forums/114-bug-reports/threads/25580-mac-diplomacy-screen-freezes-the-game?page=2

When I look at the profiles, you do not seem to be the same users.

Thanks!

Hi all,

Thanks for the report,

Can you please confirm something for me : did the diplomacy screen start working when you activated the "Fastest" video option?

For the rest, I will have to check with an engineer to dig deeper. None of this happens on our Macs or those of our QA partner. 

Cheers,

I just started a battle and wound up stuck on "Loading". The game eventually crashed, after I walked away. Before it did, however, I tabbed out and used Activity Monitor and screen capped the results. Basically, as other folks have reported, an insane number of "ports" were listed as being used by the ES2 process... 273,000. The crash report sent to Apple had this nugget: 

Application Specific Information:
BUG IN LIBPTHREAD: Invalid thread port

At a guess, the system ran out of available ports.

Posting this in here as well: just had a system crash on 1.0.36 — as in game froze and brought my entire system down. Which is a first. Reverting back to 1.0.11 / last stable build for now. But still willing to beta test a new build with macOS fixes, if needed.

Hmm... now, after 4 turns on a new game in Fast mode, I saved, exited the game, tried to exit to Desktop, got dropped to the main screen and couldn't exit, so I loaded up my saved game and somehow managed to induce a CTD almost immediately... I think it was induced (in the moment) by selecting the "main menu" icon (think that's the name) in the lower right hand corner. Now, that may be total coincidence, as the game had been running for a while in the background... it CTDs on its own when I walk away from the computer for a bit (at least the previous version did).

I can confirm that the periodic CTD's are still occuring on my iMac, and I just tested and confirmed that the Diplomacy bug is still present as well.

Unfortunately, I didn't see this until well into my first game with the new beta, so I'm running on Normal speed. I'll start a new game on Fastest and see if that makes any difference.