EDO on a Mac mini M4

So, let's get it straight. Apple decided not to keep their opengl support up to date and update to 4.5/4.6. They decided as Apple does, that supporting a standard was not worth their while.

So when frontier started to use compute shaders, because they had to, mac support had to end.

If you use a computer which does not keep up to date with common standards that's what happens! Picking Apple always has consequence
If memory serves, Frontier would have needed to recode to Apples new (at the time) Metal API?
 
So, let's get it straight. Apple decided not to keep their opengl support up to date and update to 4.5/4.6. They decided as Apple does, that supporting a standard was not worth their while.

So when frontier started to use compute shaders, because they had to, mac support had to end.

If you use a computer which does not keep up to date with common standards that's what happens! Picking Apple always has consequence
most switched to vulkan tho, so dropping support for openGL isn't as dramatic as you make it out to be. It's mostly kept around for legacy purposes nowadays.
and NMS did build a native macOS client so... eh?
 
Hello. i got mac mini M4 (new), moving from pc. When i launch ED in steam through Whisky app, i got error "unhandled exception mono-to-layer error''... any help plz ? i'm new on MacOS.

Hi, I'm trying CROSSOVER, it works using /autorun, but I can't get XBox pad detected , any help plz ? seems not detected in Crossover bottle. Got good FPS at feet in station, M4 Pro + 48 GB memory, game in 4K High Settings.
 
Last edited:
most switched to vulkan tho, so dropping support for openGL isn't as dramatic as you make it out to be. It's mostly kept around for legacy purposes nowadays.
and NMS did build a native macOS client so... eh?

Hi Ploki, are you musician ? i know a Ploki from audio forums...
 
Hello. i got mac mini M4 (new), moving from pc. When i launch ED in steam through Whisky app, i got error "unhandled exception mono-to-layer error''... any help plz ? i'm new on MacOS.

Hi, I'm trying CROSSOVER, it works using /autorun, but I can't get XBox pad detected , any help plz ? seems not detected in Crossover bottle. Got good FPS at feet in station, M4 Pro + 48 GB memory, game in 4K High Settings.
iirc you need to instal .NET 4.8.
Or just use miniED launcher instead - you can bypass steam and just login with frontier.
As for the controller, can you check if it works in crossover game configuration? There's nothing in ED launcher for controller setup, only which version to launch.
My VKB (wired) works fine in crossover and ED.

Hi Ploki, are you musician ? i know a Ploki from audio forums...
guilty :)
 
iirc you need to instal .NET 4.8.
Or just use miniED launcher instead - you can bypass steam and just login with frontier.
As for the controller, can you check if it works in crossover game configuration? There's nothing in ED launcher for controller setup, only which version to launch.
My VKB (wired) works fine in crossover and ED.


guilty :)
lol for music !! you're a great musician !! i like very much "mirrors" (i think it's title...), i added a comment in past. (yoshi)

for Elite, i finally play streaming game from pc with steam, i bypass launcher with /autorun as game command, works fine, gamepad too, it needed xbox profile... thx for answer.

edit: Source: https://soundcloud.com/ploki/smoke-mirrors


comment disappeared, probly with old account... GREAT TRACK.

edit: Ploki, add me friends on steam plz, "4L13n"
 
Last edited:
Hi, I have a full fat M3 Max (16/40) MBP 16" and I installed EDO using Crossover 24.0.5. I have Advanced Settings - D3DMetal set.
Game loads fine, but the game resolution is awful, something like 1400x900 in the settings with no option to go higher. If I enable Advanced Settings - High Resolution Mode, all that happens is that the game screen becomes massive and only about 1/4 of it (top left quadrant) shows on the screen.

Any advice to sort this out?
Thanks.
 
Hi, I have a full fat M3 Max (16/40) MBP 16" and I installed EDO using Crossover 24.0.5. I have Advanced Settings - D3DMetal set.
Game loads fine, but the game resolution is awful, something like 1400x900 in the settings with no option to go higher. If I enable Advanced Settings - High Resolution Mode, all that happens is that the game screen becomes massive and only about 1/4 of it (top left quadrant) shows on the screen.

Any advice to sort this out?
Thanks.
Use supersampling @1.5x or @2x.
 
Try adjusting my settings and the screen without a border.
 

Attachments

  • Bildschirmfoto 2025-02-21 um 18.27.39.png
    Bildschirmfoto 2025-02-21 um 18.27.39.png
    1.4 MB · Views: 34
Last edited:
Has anyone tried the new GPTK 2.1? I think it's available on Crossover beta. If anyone has it, can you check if the RAM/VRAM memory leak has been fixed? I tried using GPTK 2 via Whisky and the memory leak is definitely still there. But with GPTK at least it doesn't stutter BADLY every few seconds like how it was when I used DXVK
 
Hi, I have a full fat M3 Max (16/40) MBP 16" and I installed EDO using Crossover 24.0.5. I have Advanced Settings - D3DMetal set.
Game loads fine, but the game resolution is awful, something like 1400x900 in the settings with no option to go higher. If I enable Advanced Settings - High Resolution Mode, all that happens is that the game screen becomes massive and only about 1/4 of it (top left quadrant) shows on the screen.

Any advice to sort this out?
Thanks.
I still can't get past the invisible launcher window issue with the same hardware :(
 
Codeweavers are the commercial front end of an open source stack, and by all means if you have the money to spend and prefer the simplicity this is the route to take, it keeps the coders coding. However, the codeweavers team and the wine team all those involved in this amazing project are, I believe, pretty much one and the same. It is mostly the same code that will run which ever path you take to install it. Either way you will have to entrust external open source code to run with high privileges on your machine.

I could take a look at your log, but more importantly is to debug via knowledge of your situation; Which brings us to the important question:

What have you installed so far? ... It is quite likely that you are missing Rosetta2, the apple written translation layer that is installed when you need to run Intel Mac x86 code on apple silicon. The version of wine that we will need to use, is x86 still unfortunately. (Don't panic though, it is installed and set up automagically)

Now if you choose to take this into your own hands, you do so entirely at your own risk, I'm only saying this to distance myself from any issues that you cause whilst manipulating your machine, not because there are any particular great risks involved, but for my own piece of mind. You can not blame anyone other than yourself, if you loose any data or damage part of your current operating system's installation, you make the decision to install software that is not in the App Store entirely at your own risk.

I recommend that you install brew and learn how to use wine, it is really handy software. However for this current use case, use either Kegworks or wineskins.

Brew is short for homebrew named after the computer club that gave both to both the first apple and also Bill Gates inspiration for windows. Basically back in the day it was the hackers nerd club that Jobs and Gates both hung out at, now by name, it is an Open source environment that makes use of the BSD (Berkley Software Distribution) which is the original open source version of UNIX on Mac computers. This is software is from the very roots of computing and is the foundations of macOS today.

The nice thing about this Mac/BSD setup is that the OS is very well isolated from its UNIX kernel, which is superb for security, things installed with Brew are very separate from the OS, they really can not touch it (so far as I am aware anyhow). As long as you are sensible in your use of brew, then there is little cause for concern. You will have a UNIX terminal with a package manager that is very similar to the package managers used by Linux, if you choose to follow this path.

Should you do have any issues, Mac customer support are superb. I would put my money into Mac customer support first, before codeweavers if you have not already done so. I was in contact with them about my machine having the kernel panic whilst running elite, and the service was the best that I've ever experienced and I bought my machine second hand! After I highlighted the bug in my stack, and contacted the developer of Kegworks as well as apple support, the bug was gone in the next apple patch.

Now if you install brew, it is as simple as running a few command from your computers terminal, or rather, terminal emulator (satisfying any pedantry concern for acuity).


You will need to install the MacOS translation layer called Rosetta2, this is written by apple and basically what it is and does is to make an interface between the arm64 instructions that your CPU can read and the intel x86 instructions that Intel Macs used. You can and should install this from the command line manually before attempting to instal elite, the lack of the appropriate GUI scope is a suspect for the cause of your hanging installer, there could well be a call for the Rosetta2 installation code, native to macOS falling into the void right now, because there is a error being overlooked or not dealt with appropriately in the stack somewhere. This is why you are now looking to generate a log, which is all well and good, but by far the best way to debug is to think until you understand what is happening, at least I find that is so.

You will also need wine, wine can be installed via brew, brew has what is known as a package manager, it is the same thing as the App Store except that it lives in the terminal text environment and not the GUI that you are more used too. The text terminal is surprisingly nice to use once you become familiar with it, but scary at first. I can't overstate how enriching it can be to learn it though.

Wine is a translation layer that takes windows system calls and translates those into UNIX calls, remember that BSD the underlying platform of MacOS is a UNIX, linux too is also a UNIX, this is the name of the terminal interface and its underlying system calls that you are now using. So getting back to wine, there are several versions of wine, If you don't install the correct one for your needs there can be an issue at this point. This is due to windows existing with interfaces for both 32 bit and 64 bit and the requirements of different software.

For the most part, games still use the 32 bit interfaces even when running in 64 bit environments, because it is faster. There is also an Arm version of wine, the difference being the type of system that the wine translation layer is targeting. Remember that we have the requirement Rosetta2? This accepts x86 instructions and is what we will be targeting. So we need either the 32 bit or the 64 bit version of wine, depending upon the system that we have installed.
For us on Mac it is the 64 bit install, now I've gone into detail here just for your information. But we are using a piece of software that will help you to get this working with relative ease.

Now it is possible to set up wine, and install into your wine bottles (the name of an environment that you create with wine) all of the requirements for your target software to run, of course depending upon your having installed the correct version of wine for your use case and software requirements.

This is where Kegworks, AkA wineskins, (the name changed recently because I am using a fork) comes in. What it will do is install wine for you along with the GPU translation layers that are also required for your target software and environment, in this case 'elite dangerous' on arm64 hardware that has an x86 interpreter. Kegworks wraps wine and all the dependancies into an application bundle that your MacOS sees as an application, so it can be run from icons and used with the OS in a familiar way. Without this, unless you make your own application package, you can only run the software by way of a call in the terminal command line.

Here is the Kegworks GitHub page, you do not need to access the software source code, but it is available here, I am linking because they provide the brew installation instructions. I should add that Kegworks is a fork of wineskins, I was previously using wineskins but have found that Kegworks is more uptodate and functional, opinions will vary, so I link both, the wineskins homepage does not appear to be functional right now.


The DirectX to Metal translation that Kegworks uses by default at the time of writing this is GPTK 1.1, this is the translation layer that is managed by apple to translate DirectX API calls into Metal calls, it is used in the apple game porting toolkit. Activating this layer is as simple as selecting a check box in the Kegworks user interface.

Once Kegworks is installed and you run it, you get the option of installing its engine, this is where you will select the default engine, at this time using GPTK1.1
Once Kegworks has its setup, you can use it to create applications, you run it and wait whilst it creates your application, and when it has finished. You close this Kegworks application, and run the application that you have just made.

This application is a Kegworks wrapper that should now appear in your applications folder, when you run it the first time, it will give you several options, you need to select advanced, and then select the Metal translation check box that appears at the top of the first page. Then click install software and click yes to agree to all default during instillation, unless you know why it is that you want to use something else.

The next time that you run the application that you have made, the launcher will run, there is a way to re-run the wrapper to access its settings, by navigating into the folder where the application exists, right clicking upon the application and selecting 'Show Package Contents' there within you will see a wineskins.app (still using the old name), when you run this, you get access to wine, wine tricks, and wineskins/kegworks configuration.

Now this is a wall of text, for which I apologise, the short hand is quite simple though:
  1. Install brew
  2. Install rosetta2
  3. Install Kegworks/wineskins using brew
  4. make application wrapper by running kegworks/wineskins
  5. run new application to set up GPU translation
  6. install elite
  7. become elite, popping pirates whilst seeking gold in forlorn places!
Hi there. Since you're using GPTK to run ED, have you noticed any weird VRAM bug? So far from what I've tested, even with GPTK 2.1 it will be smooth at first. But then it will keep caching the stuff in the VRAM and it won't release any unused memory. To the point where it will reach a limit where FPS drops to like 2-3 FPS. It doesn't happen when I'm using DXVK, because I can see it freeing the VRAM when it's no longer needed.

The only issue that I am having with DXVK is the fact that it STUTTERS HORRIBLY every few seconds when you're on a planet (I am currently on Horizons). So when I am landing on a settlement, it will stutter every few seconds and it's so bad. It doesn't happen with GPTK.

I noticed that it doesn't seem to be a VRAM leak (GPTK). Because if I go back and forth to the same exact place (say I go to this planet and then back to the same station back and forth) it won't increase the VRAM usage. Which means it's probably using the cached texture data in the VRAM.

If your GPTK Wine system doesn't have that issue (your VRAM is actually being freed when it's no longer needed), could you tell me the exact Wine version and GPTK version you're using? Thank you
 
I still can't get past the invisible launcher window issue with the same hardware :(
I had to install a newer version of Mono to solve a problem I was having but I'm not sure it was a launcher problem TBH.

My main Odyssey platform is to use Geforce Now, this was more of an experiment to see if I could get it running well locally.
 
New version of Crossover (25.0) runs Elite perfectly with no extra steps on my M3Max MBP
GPTK/D3DMetal or DXVK? Do you still get the VRAM not freeing bug in GPTK? if you are using DXVK, do you still get the stuttering on planets (on-foot or landing on any planets)?
 
Back
Top Bottom