[2019] September Release - Known Issues & Feedback (Mac)

Please use this thread for general feedback on the mac client as well as discussing and reporting known issues on mac.

Quick Info:

• Full Patch Notes - EVE Online Website

Other Information Threads:

• General Feedback Thread
• Known Issues Thread

Additional Release Information:

The September release brings changes to cynosural fields generators - reducing the number of hulls they can be fitted to in order to make hotdropping a more tactical choice.

Similarly, this release sees the introduction of the new Industrial Cynosural Field Generator that can be fitted by Industrials, Blockade Runners and Deep Space Transports. New industrial cynosural fields can be used by jump freighters, so as to reduce the impact of the cynosural field changes on logistical supply runs to more remote and dangerous areas of space.

Brand new wormhole graphics and audio also come with this release, with clearer visual representation of a wormhole’s remaining lifespan and mass handling capacity. Check out this devblog for more details.

This release also sees the introduction of a whole host of visual and gameplay fixes and changes, including restriction on the Venture to prevent it from capturing lowsec faction warfare complexes, and a substantial number of UI and UX improvements.

Heads up, all:

We had a few conflicts with some deprecated code that affects some (but not all) Mac users with the switch to default 64-bit.

That said, we’re pretty sure about nature of the the problems and have been testing to resolve some additional potential conflicts. Provided nothing explodes, you should expect to see it hit Tranquility early next week.

Apologies for the inconvenience.

In the meantime, though, please do confirm that you have the latest WINE version selected in the Launcher Preferences. The Wine version should be either:

Latest

or

wine-4.15-Staging-winehq-binary-207

(After starting the Launcher, click on “EVE Launcher” in the Menu Bar and select “Preferences” in the dropdown menu. In the Wine options box, observe the Wine version and if it isn’t one of the option identified here, change it to one of them.)

And for anyone experiencing a freeze in warp, the current workaround is running the client in 32-bit mode which can be enabled either through the Launcher preferences as above, or through the Launcher’s cogwheel menu.

Thanks for bearing with us.

Players who experience issues that are persistent after selecting the latest Wine version and choosing 32-bit can file support tickets to request compensation. Evaluating those requests is not my area, so I’m really uncomfortable making promises on behalf of that team, but I can say that the failure to start up in 64-bit is 100% reproducible on the old Wine master (it only supports the 32-bit client), and the reported warp crash is 100% reproducible on 64-bit, but that neither has been reproducible in house with the Latest Wine version running 32-bit.

So I’d recommend trying that configuration out before giving up on your production schedules. And as always we invite players to file bug reports (mentioning Mac, 64-bit, and even my name in the description if you like) should you find that doing so does not resolve the issue. If convenient, I’d request that you identify your selected Wine version and bitness in the reports, so that we can eliminate unnecessary investigation and speed up the process of finding a fix. I am trying to keep up with the forums and other comm channels, but Bug Reports filed from in client remain the best way to get necessary/useful information across.

Yeah. That is definitely a separate issue, then.

Hm. What was the bug report number (starts with “EBR”)? (I’m not seeing one with this toon name, but maybe it was filed from an alt?)

Hey Ken, If I understand what you’re describing correctly, this is part of the change to standard (upstream wine). The previous Wine version had bespoke keybindings that are no longer present.

Thanks, Pope. Using your nomenclature:

“UNDOCK CRASH” - so far we see this almost exclusively on 64-bit Mac clients and are investigating further with that it mind.

“BLACK DEATH WINDOW” - this is not Mac specific, but seems related to post processing (the reason Performance Mode works around it is by disabling some elements of the feature) a fix is underway.

“BLACK SUB WINDOWS” - this is the first report I’ve seen of that, and I haven’t seen it on my own High Sierra machine (significantly older and less beefy that your machine). Will look for additional info in existing bug reports.