Page 3 of 3 FirstFirst 123
Results 41 to 46 of 46
  1. #41
    Community Member
    Join Date
    Aug 2019

    Default Script.log; ddolive.exe, wineprefix directory missing

    Same problem yet both files and the directory are missing:

    NO Script.log;
    NO ddolive.exe,
    NO wineprefix directory

    Quote Originally Posted by Cydrith View Post
    Thanks for following up.

    This sounds like the application is having a hard time downloading/writing the installer to disk. You can verify this with us by providing the contents of your log file.

    To check this, navigate into the Applications directory. Right click DDO, "Show Package Contents".
    Once that opens, expand the "Contents" and "Resources" directories.
    In the "Resources" directory you should see the following:
    • A file called script.log
    • A file called "ddolive.exe"
    • A directory called "wineprefix"

    Based on which of these are missing (if any), and what the "script.log" file says, we can troubleshoot what went wrong.

  2. #42
    Community Member
    Join Date
    Mar 2015


    Quote Originally Posted by Kaytis View Post
    The Launcher needs to be fixed by SSG.
    The problem is that, "Unfortunately, we do not offer technical support for DDO on MAC"
    -Swarley (Standing Stone Games Help)
    Not very impressive

  3. #43
    Community Member jwelch's Avatar
    Join Date
    Jun 2008
    Tallahassee FL


    If you want this to play right, there's probably two short-term solutions:

    1) Set up boot camp on your mac, reboot and play the windows client in windows. Max speed, compatibility, you'll have fewer problems and SSG support will probably actually talk to you. UPdating to macOS 10.15 won't cause you problems.

    2) Run it in a VM, i.e. vmware or parallels. This may not work due to VM overhead, but you're still running it in "real" windows, not the "sort of windows" WINE uses. And again, you have some hope of actually getting support from SSG. VMware and Parallels both work in the next release of macOS, which is 64-bit only.

    3) I'd say the WINE version, given how badly this transition has been handled, won't work consistently right for at least a month, and god only knows if they're using a 64-bit version of WINE. If they aren't, then you can't upgrade your mac because 10.15 is 64-bit only, 32-bit apps won't work, and you'll be unable to use the WINE version. Good luck in SSG fixing that inside of a year if ever. You'd be better off learning out to package it in WINE on your own and not waiting for SSG.

    SSG is a windows-only company. That's their choice. But I wish they'd stop half-arsing this issue. Just say "we only support windows. Period." stop the WINE dance, because that is clearly not being done well, and given their apathy towards mac players for some years now, expecting them to get a 64-bit version out once 10.15 drops is unrealistic.
    "Sorry Elminster, it was really dark, and I'd drank a LOT of coffee..."

  4. #44


    We've released a new variant of the Wine client. The update is posted here.

    This is not the same wine client as was previously being distributed in beta form. Many of the problems with the beta client have been addressed.
    Please let us know of any further issues.

  5. #45
    Community Member
    Join Date
    Jun 2013


    If I download the Wine client will it be a separate setup that won't interfere with my Steam client setup? I don't want to test it if it's going to mess up my working version I'm pretty good at troubleshooting, but don't want to waste time reinstalling if my Steam setup is going to get tromped on.

    I know that previously, I was able to run DDO directly and it was a separate setup than the Steam setup, but I want to confirm this.

  6. #46
    Community Member
    Join Date
    Feb 2019

    Default here's a "conversation" i had with Cordovan:

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

This form's session has expired. You need to reload the page.