CCP_Caffeine

Try enabling hardware acceleration if it’s not on already.

You will simply need to be on the latest version of the launcher, and then select Singularity when the test has started

They are handled by 2 seperate teams

If all goes to plan, there should be a news article in the next week that has more of an update

Rest assured, I will post updates as soon as I can . A lot of the time there isn’t anything to report, as it’s just ongoing development work - which will be the case for a while.

While I know macOS users are super excited about this, keep in mind that the first playtest is going to be for finding the more serious problems (crashing, performance issues etc.). A total move from Wine to a Native Mac Client is going to take a while

Ahhh, I knew someone would remind me in here

I’ll be upfront with everyone: We’re not going to get the public test out this month, even though that was our original intention. We had some stability issues that would have limited the purpose of the test (as well as giving a bad experience). These are pretty much resolved now.

I have estimations for a new date which I hope to share with everyone soon™ in the form of a devblog.

When it comes to the public test, we need to ensure we get as much valuable data from it as possible (performance measurements, crash reports, etc.). While I know a delay is annoying, it simply allows us to build a better client as a re...

Some of the input issues are due to OS shortcut clashes, which then cause issues with Wine. This means it has difficulty in realising the true status of a key (sometimes the ‘stuck’ issue being reported).
Other issues are just due to the OS / Wine / Game layers that get crossed - if any of them has an issue, it gives a poor experience. I’ve noticed this in particular when the system is under heavy load.

We’ve been doing a bit of a dive into input the last few days, including rewriting some core bits of it (like default shortcuts).

When we have a public test, I’ll be keen to hear comments about input / shortcuts, as I know there has been weirdness with the Wine client.

Not yet - but it’s not because I’m trying to avoid the issue. We’re simply at the development phase, with plenty of work for us to tackle. Any performance measurements I give now could change based on development work. I’m sure you can understand that I don’t want to give any figures that are not reflective of what the final product will be.

Suffice to say, we...

This is a question that every producer is terrified to answer . We don’t want to get hopes up, only for us to have to push it back.

We were aiming to have a public test out in Q1 of this year. I’m still hopeful this will be the case, but there is a lot of moving parts with a project as big as this.

There isn’t a timeline for a final release - we’ll base that on how the public test goes, how many crash reports we see, performance tests etc.

There will always be some difference due to underlying OS / GPU / Driver differences, but they are much closer in the way they look now. In part this is because we can now use the post processing features that were only avaliable on DX11 in Windows previously.

Hi
When we have something that is available to test, we’ll be posting up a devblog and letting everyone know how they can join in
You don’t want to use it just yet, as development is ongoing

Hi
Not just yet - we still have plenty of work we need to do. Moving to a new OS is a huge project for us
Rest assured, we will share any news as soon as we can.

I understand the frustration when an OS doesn’t have the features you use in an upgrade, I’ve been there myself.

My comment is really aimed towards the OS versions we are likley to support. There has not been a decision yet on which these are, so don’t read into it too much. We want to support as many users as we possibly can - but it is fair to say that we’ll be making sure it will run on the latest versions of macOS.

In short: Jumping to another OS is a big move for us. Jumping to another OS on a different architecture is even bigger.
We still need to tackle many of the same challenges for both, so it makes sense for us to bring it to as many users as possible.

Comparing against Wine isn’t really something we’re doing right now, mainly because we would be comparing Metal against a DirectX 9 codepath.
We also don’t have a number of optimisations in place right now: both on the rendering side, and for the rest of the client code. That will come in time

It’s fair to say that we are aiming for parity with the Windows DX11 client in the future.

There is some assembly kicking about, yep, but it’s not just that. There is a number of areas in not only the codebase, but the systems around it that will need to be adjusted. Getting the native Intel based client working is a huge step towards the Apple Silicon version though.

I hope to do a devblog with some more details in the future.

Hi folks

We have just posted the exciting news that we have been working on a native Mac client over on our news page.

I have started this thread to discuss the news. I will try to answer questions where I can, but as development is ongoing, I will not be able to answer everything.

Here are the answers to a few common questions that I expect to come up:

Q: Why a native client?

A: The native macOS client w...

Hi

I’m glad to hear that it resolved the issue.

I would suggest looking to see if there is an update to the software first, as we tried to replicate it internally, but could not. It looks like there have been frequest updates, some of which include stability fixes: https://mirillis.com/action-history

We found the fix through examining logs and asking others to give it a try. Given that we can’t replicate it internally, it may be some specific combination of driver version + software version which causes the issue.

The heart of the issue is how the software works (via attachment of a process / injection).
The specific problem is related to when we check for what hardware GPU acceleration is ...

Hi folks

I’m not part of the launcher team but have been involved in some of the discussions as we (launcher / engine) often investigate these issues together.

While this isn’t going to be the case for everyone, we have noticed a rise in 3rd party software which has started to interfere with both the launcher and the game client, causing them to stop launching.

In a log above, we can see “VK_MIRILLIS_LAYER” which likely relates to ‘Mirillis Action!’. We have seen this software inject and intercept calls that has caused issues with launcher and client launching. We have spoken to a few players who have confirmed removal fixed their issue.

While we will always try to work around this so you can get back into game if we can, we are quite limited in what we can do when external software injects into the launcher and client. There is simply no way we can anticipate what this process will be doing, or how it will interact.

For anyone that is having launc...

Hi

I’m not part of the launcher team, but I have seen this a few times when the launcher is not successfully installed for some reason. By far the most common cause is when the launcher is being run from the downloads (or similar) folder directly. It needs to be installed for the update feature to work. This usually involves dragging it to the ‘Applications’ folder on first run. This caught me out many times when I started using masOS.

Failing that, there may be a permissions issue, but why it would run when being downloaded from the website is a bit confusing.