Launcher Script For Mac OS X

[Kaytis]

i fixed that by making sure that i left the portion in bold:
"account=account_username_here, pass=account_password_here, selectedServer=server_name_here"

for me it was:

account=Daarsurra
pass=********
selectedServer=Orien

Hi Daarsurra. I am not sure if you still have a question. Bear in mind that the native Mac client is broken. It will crash on launch. It is scheduled to be fixed on August 14th (tomorrow). Neither the actual Launcher, nor my script will work until the client is patched.

[Kaytis]

Dear Kaytis,
thank you for keeping this launcher alive. Actually it's the only way to play from mac (without installing windows) and I really like the "bash scripting art".
After 42.4 release the launcher fails, am I the one experiencing this issue (I don't know, due to local problems) or is it common to other users?

Last update had the following changes that does not seem to be a big deal but are launcher-related:

The launcher will now dynamically update your position in line if you are in a login queue.
The launcher will no longer bounce you between multiple login queues at random.
New splash screens are now checked and downloaded, if needed, in parallel instead of one at a time. Hopefully this will reduce the time spent on this stage.

However I get the following output before it fails:

Initializing display with title 'Dungeons and Dragons Online'...
/build/dnd/dnd_live/src/engine/client/device/osx/Device_OSX.cpp, 284: called.
Initializing the smartbox...
Initializing the user interface...
Client ready
Client::Connect() async logon begun.
Connection failed (0x00000004:0x00CD0B73) to server 0, addr 198.252.160.45:9004
./my_ddo_launch.sh: line 589:  1686 Segmentation fault: 11  ./${gameClient_FILE}/Contents/MacOS/dndclient ${gameClient_ARGS}

Seems to me that " gameClient_ARGS" could have been changed
Kind regards,
Stefano

Hi Ayeye. It looks a little bit like you did not allow the real Launcher to update the client before trying the script. However, the native Mac client is broken. It will crash on launch even after you update it. It is scheduled to be fixed on August 14th (tomorrow). Neither the actual Launcher, nor my script will work until the client is patched.

EDIT: I was concerned about the logistical changes in the Launch process. However, the script still seemed to launch the client ok. Unfortunately the client itself broke with the update, so I can’t be completely sure.

[Isys]

Gang...

Thanks for keeping this thread alive. Probably saved me an hour of futility!! So tomorrow a patch...
Does anyone know that the minimum OSX DDO will run on? I'm on 10.10.5 - Yosemite...

[Ayeye]

Hi Ayeye. It looks a little bit like you did not allow the real Launcher to update the client before trying the script. However, the native Mac client is broken. It will crash on launch even after you update it. It is scheduled to be fixed on August 14th (tomorrow). Neither the actual Launcher, nor my script will work until the client is patched.

EDIT: I was concerned about the logistical changes in the Launch process. However, the script still seemed to launch the client ok. Unfortunately the client itself broke with the update, so I can’t be completely sure.

Ah nice!
I was quite puzzled but I did not notice the problem was wide and under fixing (btw... where I work there is a frozen zone in December and another in August where you cannot touch production without a green light from the CEO, planning an update in these days it's not a great idea).

Coming back to the main subject, is Daybreak Game Company LLC aware of launcher problem for mac users? I think that shouldn't be something hard to solve, also since there is a working launcher script in this thread. After this issue with the main client it could be nice to open a couple of tickets for the launcher.

@Isys
I'm playing from High Sierra 10.13.6


Stefano

[JQP]

Devs--any update on when the Mac client will be fixed? The hot fix obviously did not happen and I see no indication of when one will occur.

[Daarsurra]

as far as i can tell, the "hotfix" seems to have fixed things that most players care about and left the Mac client standing on coals. the Mac client now crashes at the character selection screen and not after hitting Play.

[Ayeye]

as far as i can tell, the "hotfix" seems to have fixed things that most players care about and left the Mac client standing on coals. the Mac client now crashes at the character selection screen and not after hitting Play.

Fixed today.
You could have followed the discussion on the "service notice" page of the forum:

https://www.ddo.com/forums/showthrea...stern-(-4-GMT)

Checkout the post from MacnCheese guy.

*Edit: Well, mine works correctly, also "Play" mind the downtime times are close to this time*

Stefano

[Daarsurra]

Fixed today.
You could have followed the discussion on the "service notice" page of the forum:

https://www.ddo.com/forums/showthrea...stern-(-4-GMT)

Checkout the post from MacnCheese guy.

*Edit: Well, mine works correctly, also "Play" mind the downtime times are close to this time*

Stefano

actually, the "legacy client" for Mac still doesn't work for me, and i think that you meant to post a different link; i've followed that thread (still explains nothing) and about 8 others related to Mac issues; while there's a more updated thread for August 15th downtime, i think this one might be more helpful to the Mac community:

While the legacy Mac client continues to work (after today's patch), we are moving away from that client to the WINE client that debuted earlier this year. So, make sure to download it here if you ever run into any issues with the legacy client: http://live.ddo.com/sites/clientdl/ddo/ddolive.dmg

We don't have a firm cutoff date (yet), but people who play on Mac should consider upgrading to the newer client regardless if they can.

[Mc-Iver77]

I followed the instructions and saved the SH file in my user Application folder and realized that it should be in the Applications folder that holds the DDO client. Once I moved it there I ran the script `chmod 755 /Applications/DNDLauncher.sh` but nothing happened. If this is happening to you, run `sh /Applications/DNDLauncher.sh` Works for me now.

[t.takli]

Works beautifully!! Thank you so much. Have been unable to login after one of the updates (and patch to fix problem). You are amazing!

[t.takli]

I followed the instructions and saved the SH file in my user Application folder and realized that it should be in the Applications folder that holds the DDO client. Once I moved it there I ran the script `chmod 755 /Applications/DNDLauncher.sh` but nothing happened. If this is happening to you, run `sh /Applications/DNDLauncher.sh` Works for me now.

Obviously. You had to run the chmod line first BEFORE running the launcher.

[Mc-Iver77]

Obviously. You had to run the chmod line first BEFORE running the launcher.

You're right, i only read half of the instructions.

[Aredharr]

Hi Guys,

First thanks all for this super cool thread.

Knowing that DDO will move to the WINE client at some point, I decided to install it alongside the old DDO client, meaning I have 2 DDO installed currently (didn't want to delete the original/old one yet as I didn't want to be left without the game). One is the original, called DNDclient (default) and the new one, which I named DDOWINE when I installed it.

Every time I try to open the WINE client with the game launcher, I get the trigger to the resource folder and the whole thing goes to hell, which brought me to this thread.

I've setup the script as described and I was able to launch my original mac client quite easily (actually very cool). Then, I figured I could change the destination of the app and launch the WINE one. Sadly, I get the same code response from the terminal (log in, etc), but nothing launches after the scripts has ran...

Since I'm not super familiar with this stuff I figured I'd ask if this is something that can be done or if I'm just dreaming.

Thanks in advance!

[Kaytis]

Hi Guys,

First thanks all for this super cool thread.

Knowing that DDO will move to the WINE client at some point, I decided to install it alongside the old DDO client, meaning I have 2 DDO installed currently (didn't want to delete the original/old one yet as I didn't want to be left without the game). One is the original, called DNDclient (default) and the new one, which I named DDOWINE when I installed it.

Every time I try to open the WINE client with the game launcher, I get the trigger to the resource folder and the whole thing goes to hell, which brought me to this thread.

I've setup the script as described and I was able to launch my original mac client quite easily (actually very cool). Then, I figured I could change the destination of the app and launch the WINE one. Sadly, I get the same code response from the terminal (log in, etc), but nothing launches after the scripts has ran...

Since I'm not super familiar with this stuff I figured I'd ask if this is something that can be done or if I'm just dreaming.

Thanks in advance!

Hi Aredharr.

Work has kept me busy lately. I have glanced at what it would take to get the script working with the Wine client. It shouldn't be too difficult, but don't hold me to that. I noticed that folks using Wine on Linux claim to be able to use the "pylotro" script as their game launcher. That is interesting. If it works on Linux, it can certainly work on Unix (Mac).

The biggest problem right now is that macOS 10.15, only a few weeks away, removes 32-bit support. The "legacy" client is 32-bits. So it won't work. Period. There is a beta version of a 64-bit Wine emulator available for the Mac. It can, in theory, run the 32-bit Windows client but I have not tried it. It is said to be very buggy at this point.

There's a bit of train wreck coming. If you want to keep playing DDO, don't upgrade to macOS 10.15 until a stable 64-bit solution becomes available. SSG will either need to rebuild the existing legacy app using the 64-bit version of Qt (the cross platform SDK they used), or try to ensure that the Windows client works ok in the 64-bit Wine emulator on Mac.

[jkalten]

Kaytis,

Is your script needed for the new wine client beta, or is it only needed to launch the legacy native client?

I'm just curious as from a quick read of your script I should be able to create a UI for it pretty easily with swift if this is going to still be needed for the wine version.

Currently downloading the wine client currently on my MBP just to try to see what the condition of things is like.

[Kaytis]

Kaytis,

Is your script needed for the new wine client beta, or is it only needed to launch the legacy native client?

I'm just curious as from a quick read of your script I should be able to create a UI for it pretty easily with swift if this is going to still be needed for the wine version.

Currently downloading the wine client currently on my MBP just to try to see what the condition of things is like.

Technically, the script was never needed. It is an alternative to the DDO Launcher. The only real advantage is that it can launch the DDO Client much faster than the DDO Launcher can. The only time it might have been "needed" was when the DDO Launcher stopped working in Mojave.

The script will only work with the legacy DDO Client at the moment. It is not set up to launch the Wine DDO Client. I have taken only the briefest of glances at what the running Wine DDO Client command line looks like, but it follows an identical pattern of parameterization. Launching the Wine client should be a matter of reforming the command itself. The hard part of determining the launch parameters is already done.

Putting a swift shell around it sounds like a fun project. The script is super naive about its own parameterization. It expects either one (a toon name) or none. The presence or absence of that one parameter drives everything else. It's actually a pretty lame way to do it. But it makes invoking it super easy. A better way to do it would be to do a full on flag driven kind of thing. Something like:

./DNDLauncher.sh -u _username_ -p _password_ -s Orien -c Kaytis

Doing that would make the script generic and require no end user modifications. At the cost of having to type all that every time (admittedly I just use the up arrow in the Terminal, so there wouldn't be any cost).

It would still be possible to allow handcrafting of the script to specify all the rest of the details when only the toon name is provided. I probably should have done it that way really. Hmm.

The biggest problem right now is the lack of Wine support. I would have to look at that first because that does seem to be the direction SSG is headed.

[Eudoxus]

THANK YOU for this!

I just subscribed to VIP for a year, then the latest patch came out and BLAMMO I couldn't play any longer.
I contacted support and they said "we don't support MAC" and pointed me to the main community thread.
I shot them back an email that says "if you don't SUPPORT MAC, then please provide me the rationale for having a MAC DMG download on your website where you sell subscriptions and products"

I'll see what, if anything, they say in response to this.

[piercia]

Kaytis, thank you for the script for the previous Mac client. Just wondering if you have had time to adapt the script for the new Wine client yet?

[Kaytis]

Kaytis, thank you for the script for the previous Mac client. Just wondering if you have had time to adapt the script for the new Wine client yet?

I just got it working. I am going to clean it up, add a feature that people were asking for, and post it soon™

Edit: Posted. The OP has been updated.

[Dassex]

So, right off the top - I am NOT tech savvy in the least.
My question is about the DDO Launcher.
While I can launch the game more times than not, the text in the small window for the launcher is complete gobble-gook (I believe that is the technical term.)
Can't make out which server I'm clicking on (though, I have done a bit of process of elimination calculations by deciphering some of the "gobble-gook."

Any thoughts about how to address or even possibly fix this would be appreciated.
Pretty exasperating on the whole.