CrossOver Support - Community Forums

I'll post this here, as it appears no longer to be impossible to directly respond to the 20 October blog post 'We wish we were squidding: a bit behind on the next CrossOver release'.

The blog post explains why Crossover 21.1 is delayed - yet it only mentions problems specific to MacOS - to such an extent that it appears as if Crossover is a Mac-specific application.

If any Crossover employee is reading this: can we please get a Linux-specific post, or one that genuinely encompasses all three versions (Mac, Linux, Chrome)? Crossover 21 does not include a number of important new technologies, most important of which may well be its improved Direct X 12 support. The further behind it gets, the less reason there is to use this version of Wine over other incarnations.

Personally, I am seriously wondering if I should renew my subscription as, currently, I might be better off using the Steam runtime or 'regular' Wine. I know paying the subscription helps Wine development, yet there is no immediate benefit for me as a customer if Crossover is not updated regularly.

In short, I I would like to know more about when to expect the next Linux update (hopefully soon) and about what technologies it will include. I would also like to know whether challenges specific to one version of Crossover will continue to determine the update frequency for the other versions as well.

Hi Geert,

I want to assure you that our 21.1 release is not geared only toward our macOS users, and there will definitely be changes that are relevant to our Linux and Chrome OS users. I wrote that blog post because we were getting a huge influx of questions from our Mac users about our timeline for Monterey support, and it was helpful to our support team to have a resource to share with inquiring macOS users. I definitely did not mean to imply that the upcoming 21.1 release was only relevant to macOS users, and I regret if it gave that impression.

CrossOver 21.1 is currently in beta, and will be released in the near future. When it is released, we will be sharing details of what is included for our Mac, Linux and Chrome OS customers in multiple places, including our blog and the CrossOver Announcements forum (https://www.codeweavers.com/support/forums/announce/?t=24).

We are also working on a blog post sharing details about timelines for DirectX 12 support on both Mac and Linux, so please keep an eye out for that.

Let me know if I can answer any other questions.

Best,
Meredith

Thank you for your reply - I greatly appreciate it, and look forward to learning more about the next update.

CrossOver 21.1 is currently in beta, and will be released in the near future.

"near future" is vaguely pointless. I understand it will be released when "it's ready". But until it is I know you're aware Quicken as been rendered useless. Knowing this, you have paid users have to ask, then wait for access to a beta version. (I've had issues sometime in the past, have been through this). Knowing there is a popular (I presume) application non-functional -- really, there's not much more that can be done? The "it's on the way" has been posted for a couple weeks now.

I suppose there's reason for no optional beta version available for download in my account -- maybe you could use extra large letters warning users not use beta blah, blah, blah how much more would I have to pay for that?

Hi Doug,

To access a build that has the Quicken fix, all anyone needs to do is ask by opening a support ticket. We have been giving users who would have upgrade entitlements access to nightly builds and the beta build ever since we had a verified fix, which we were able to start delivering 48 hours after it was first reported to us by an affected user in a ticket.

We don't want to give blanket access to nightly or beta builds to all users (that is a perk reserved for our BetterTesters), but we will give early access for fixes to catastrophic bugs like this one upon request. Sadly, this isn't the first time that an application update caused problems for CrossOver, and it won't be the last, but we always do our best to help out affected users in advance of an official release if they're willing to use non-stable builds. And in this case, if we weren't already gearing up for a release when this bug presented itself, we likely would have done an interim official release to address this particular issue.

Best,
Meredith