Elite Dangerous Forum

Hello, I have ED Odyssey (Steam) on a Macbook Pro M1 Max. Crossover 22.1.1.35679. Win10x64.
Everything was working before the launcher update. The new launcher starts but does not show a window.

1. Is it possible to go back to using the previous launcher?
2. Or advise what Windows components are required in the new launcher, unlike the old one?
   I also wrote to Frontier support. I'm sure I'm not the only one having this problem. Thanks

Hi Alex. I am running ED Odyssey (Steam) on an Intel iMac 2017. I observed the same behaviour of the new launcher.

While I did not find a real solution to the the problem, I succeeded to launch the game using the following workaround:
In Steam open the Properties of ED and set the launch options to "/autorun"
This makes the launcher start the game using the default setting (hopefully Odyssey).

I hope this works for you as well.

Thanks, Thomas, this worked for me.

I still have the problem that Elite is minimized when I switch to another application (Command-Tab) and back again; is this known and is there a solution for this?

Hi Alvarilla,

I could not find a solution to the window-minimizing problem in macOS Ventura, but it seems to have
disappeared since I installed macOS Sonoma recently. Maybe this works for you as well?

Cheers,
Thomas

The new Elite launcher still doesn't work for me, but...

On MacOS 13.4, I was able to get the game to run properly by:

1. Installing the Microsoft .NET Framework 4.8 and Microsoft Visual C++ 2019 Redistributable Runtime CrossTies
2. Adding the /autorun switch to the launch options as specified here (note: /autoquit works to auto quit the launcher when you exit the game and /edo specifies "ED:Odyssey" as the product to run)

I was initially having problems with the game auto-minimizing but when I installed the CrossTies that problem went away. I also notice that it plays a lot better on Ventura than it ever did on Monterey. I suspect Sonoma will play it even better.

I am still getting the same issue: EDLaunch.exe seems to run in the background despite including /autorun under properties -> launch options. The window doesn't seem to exist. The EDLaunch.exe process is sitting at about 5% CPU. I didn't have any issues setting up the bottle except a warning about .NET Framework 4.8 - but that seemed to install ok.

I'm running on Sonoma 14.2.1 on an M2 Macbook Air with 24GB RAM.

Does anyone have any thoughts? Thank you!

I have the same issue; impossible to launch ED even with /autorun
Anyone managed to fix this for good ? :/

I found a workaround that solved it for me:

Just install this https://github.com/rfvgyhn/min-ed-launcher and it will work

This is a launcher that replaces the original launcher

just follow installation instructions (copy files in bottle next to original launcher) then use this as launch options:

cmd /c "MinEdLauncher.exe %command% /autorun /autoquit /edo"

Enjoy !!

Edouard Camou wrote:

I found a workaround that solved it for me:

Just install this https://github.com/rfvgyhn/min-ed-launcher a small world cup and it will work

This is a launcher that replaces the original launcher

just follow installation instructions (copy files in bottle next to original launcher) then use this as launch options:

cmd /c "MinEdLauncher.exe %command% /autorun /autoquit /edo"

Enjoy !!

Thank bro.

Hello,

got it working as "Edouard Camou" explained in his post, but I did something different since I couldn't get the launch options with cmd /c etc to run

1. Download MinEdlauncher "https://github.com/rfvgyhn/min-ed-launcher/releases"
2. Unzip the Zip and copy the MinEdLauncher.exe into your Elite Dangerous folder which for me is here
   MacintoshHD/User/your Username/Library/Appliaction Support/CrossOver/Bottles/Your SteamBottle/drive_c/Program Files (x86)/Steam/steamapps/common/Elite Dangerous
3. Rename EDLaunch.exe to EDLaunch_OLD.exe
4. Rename MinEdLauncher.exe to EDLaunch.exe
5. Now you can simply start the game from inside steam. (Just a heads up the .exe might be overwritten by an update for steam, in that case you need to do step 2. to 4. again)

My Steam Bottle is Windows 10 64-Bit and started just with D3DMetal enabled.

Running great on an MBP 16" - M3 MAX 30G.

I was able to get past the mono-io-layer error by installing the latest version of mono into the bottle. Tested w/EDH, win10 bottle, D3DMetal, Mac Studio running Sonoma.