CCP_Antiquarian

Hey all…we’re looking into the wine64-preloader issue now. There are a few things happening.

1. The crash monitoring process is not closing gracefully on exit. So the preloader apologizes in a “Program Error” popup window. People who see that window simply close it and all instances of wine64-preloader close. Click click, we’re all fine here (except for the aforementioned lack of grace and subsequent crashmonitor crash, oh the irony).
2. On some Macs, however, the popup is not properly displaying and instead appears like a tiny cursor under the menu bar. The other indicator is an wine64-preloader exec icon in the dock for the (not visible) “Program Error” window. You must quit these manually to end the processes.

We are investigating immediate solutions to both issues now, but this will be the situation at least into next week. Until such time as we can ferret out the core problems, please manually close those windows from the dock on exit. We know thi...

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.

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.

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?)

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...

Hey All,

We’re looking into Mac issues with the September update now.

For this current release, please contribute feedback here: September Release - Known Issues & Feedback (Mac)

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 3...

That’s entirely my fault, E6o5.

We’ve been digging into the code on this and I update our internal resource, but neglected this thread.

Announcements forthcoming, but the results from our 2nd mass test looked pretty good and initial public Mac 64 usage is returning helpful data. The ball is rolling!

Thank you all for your comments and contributions here. It’s super helpful to have a vocal user base and really great to show engagement to the decision makers.

We have updated the post above, and added a special page offering instructions to those wishing[1] to experience all the glory of the 64-bit Client.

[1] and by “wishing” we mean log in to Singularity at all, as 64-Bit is mandatory, citizen.

Hello Bleeding Edge Capsuleers,

Last Time, on EVE Online 64-Bit Progress:
The March 5th mass test revealed some interesting memory and FPS concerns with the initial implementation. Devs scrambled to find the causes and modify the code to prevent further disruptions.

And now, the continuation:
Our Engine and Build teams have tackled a fair number of interesting issues in the 64-Bit client. We resolved a unique quirk of EVE memory all...

I’ve spoken to a few people about having an MT scheduled to include players in the UTC-4 to UTC-8 range to make it more convenient for most residents of the Americas.

There are no plans at present, but I have hopes for the future. Plus staying at work til 1AM means I might get food out of the deal. We’ll keep you all posted.

You already have the client (we’ve been packaging the 64bit folder for a while now), but it will only be made active through the launcher during the window for this test.

At present, that window opens on Monday the 6th.

Hey @Xaviar_Onassis and @Vincent_Athena, here’s the best walk through I can offer. Will clarify if anything isn’t immediately grokkable, though. Just ask:

1. You can see what the mappings would be right now by choosing “winehq-master” as the dev branch and “Latest” as the wine version in the Preferences menu of the EVE Launcher (accessed through the menu bar, not the Launcher settings cog).

2. We can’t 100% claim that winehq-master will always have the same keybindings (we don’t maintain winehq-master) it has at present, but the current set up is as follows (mos...

Thanks everyone for the replies and comments.

We’re about to have the implementation of this in a testable state, so I may soon be (potentially able to begin planning to think about the consideration of a slight possibility of maybe) providing some answers on resulting functionality and what exactly happens when we remove ccp-master from the equation.

Until then, please continue to comment and of course keep flying.

Thanks, Rixx.

I suspect a lot of Mac “powerusers” are in a similar boat.

We’ll do what we can to keep you guys cruising along.

You wouldn’t expressly lose the Magic Mouse, but you likely would want to activate Secondary Click in the settings so that the right side functioned like a right mouse button (As it turns out, many Mac user have already enabled this functionality).