These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Test Server Feedback

 
  • Topic is locked indefinitely.
12Next page
 

MAC OS X - Cider Upgrade Feedback - Scrumpy vs Vinegar

First post
Author
Previous Topic Next Topic
CCP Sledgehammer
C C P
C C P Alliance
#1 - 2014-05-14 11:50:37 UTC  |  Edited by: CCP Sledgehammer
Hello wonderful denizens of New Eden!

We have upgraded the Cider version for OS X clients and as a result have fixed multiple preexisting issues that appear specifically on Mac clients.

Due to the requirements of the upgrade, OS X 10.6.8 support will be dropped as was discussed in this news announcement

Some of the issues you can expect to be fixed are as follows:

Quote:

  • Stars will no longer flicker wildly if you are being shot!

  • Warp Disruption Bubbles no longer flicker if they are being shot!

  • All ships will now have blinky lights again! (Rejoice, Police Pursuit Comet Pilots!)

  • All ships with drone bays or other openings that are protected by forcefields have their forcefields back!

    • We are currently analysing performance test results so any feedback on the FPS and RAM usage of your client would be greatly appreciated.

    As always, I am really looking forward to hearing about any issues that you guys find or just what you think in general, so please go wild in this thread as and when you see anything right or wrong or encounter anything appropriate or awry.

    Graphical QA Analyst | EVE Quality Assurance | Team TriLambda
    Vincent Athena
    Photosynth
    #2 - 2014-05-14 14:10:15 UTC
    I tried updating my sisi client, and got an exception "client update unsuccessful" at (2/4): CREATING EVE_ONLINE_781718-783070_MAC.PATCH 25.7%

    Know a Frozen fan? Check this out

    Frozen fanfiction
    Christopher Foyle
    University of Caille
    Gallente Federation
    #3 - 2014-05-14 14:41:40 UTC  |  Edited by: Christopher Foyle
    I am also getting a client update was unsuccessful error when attempting to patch Singularity.

    Stack trace/Exception: http://pastebin.com/jz5WTuMy

    Mac OS X 10.9.2
    2.3 GHz Intel Core i7
    16 GB 1600 MHz DDR3 RAM
    86G available disk

    As a work around, I moved my Singularity.app and patched a copy of TQ.

    % cd /Applications
    % mv EVE\ Online\ Singularity.app EOS.app
    % cp -r EVE\ Online.app EVE\ Online\ Singularity.app
    % open /Applications/EVE\ Online\ Singularity.app --args /server:87.237.38.50
    CCP Sledgehammer
    C C P
    C C P Alliance
    #4 - 2014-05-14 14:51:58 UTC  |  Edited by: CCP Sledgehammer
    Hey guys,

    Can I ask what version of the launcher you use with Singularity?

    Graphical QA Analyst | EVE Quality Assurance | Team TriLambda
    Christopher Foyle
    University of Caille
    Gallente Federation
    #5 - 2014-05-14 14:56:33 UTC
    CCP Sledgehammer wrote:
    Hey guys,

    Can I ask what version of the launcher you use with Singularity?


    Problematic launcher version: v2.1.684081
    CCP Sledgehammer
    C C P
    C C P Alliance
    #6 - 2014-05-14 15:00:33 UTC
    Christopher Foyle wrote:
    CCP Sledgehammer wrote:
    Hey guys,

    Can I ask what version of the launcher you use with Singularity?


    Problematic launcher version: v2.1.684081


    OK, and am I correct in saying that after copying TQ you are using 655310, and it's working fine so far?

    Graphical QA Analyst | EVE Quality Assurance | Team TriLambda
    Christopher Foyle
    University of Caille
    Gallente Federation
    #7 - 2014-05-14 15:04:50 UTC
    Quote:
    OK, and am I correct in saying that after copying TQ you are using 655310, and it's working fine so far?


    Indeed. Patching TQ to 655310 worked.

    Fixed: no more full-screen launch when it should be windowed
    Fixed: Flashy bits are flashy on ships in space

    \o/
    CCP Sledgehammer
    C C P
    C C P Alliance
    #8 - 2014-05-14 15:05:26 UTC
    Christopher Foyle wrote:
    Quote:
    OK, and am I correct in saying that after copying TQ you are using 655310, and it's working fine so far?


    Indeed. Patching TQ to 655310 worked.

    Fixed: no more full-screen launch when it should be windowed
    Fixed: Flashy bits are flashy on ships in space

    \o/


    \o/

    Graphical QA Analyst | EVE Quality Assurance | Team TriLambda
    Vincent Athena
    Photosynth
    #9 - 2014-05-14 15:12:54 UTC
    CCP Sledgehammer wrote:
    Christopher Foyle wrote:
    CCP Sledgehammer wrote:
    Hey guys,

    Can I ask what version of the launcher you use with Singularity?


    Problematic launcher version: v2.1.684081


    OK, and am I correct in saying that after copying TQ you are using 655310, and it's working fine so far?

    Huh? What do you mean? Im trying to connect to sisi with the sisi launcher tool. What does TQ have to do with it? What do you mean by " after copying TQ "?

    Know a Frozen fan? Check this out

    Frozen fanfiction
    Christopher Foyle
    University of Caille
    Gallente Federation
    #10 - 2014-05-14 15:22:40 UTC  |  Edited by: Christopher Foyle
    Vincent Athena wrote:

    Huh? What do you mean? Im trying to connect to sisi with the sisi launcher tool. What does TQ have to do with it? What do you mean by " after copying TQ "?

    Vincent,

    See the lines beginning with '%' in post #3 as a guideline for copying TQ to SiSi in Terminal.app. Be aware that your SiSi location may be different.

    I don't use the SiSi launcher tool because I could never get it to work. Instead, I copied the TQ install to a new location and opened the launcher via Terminal.app.
    CCP Sledgehammer
    C C P
    C C P Alliance
    #11 - 2014-05-14 15:35:43 UTC
    Vincent Athena wrote:
    CCP Sledgehammer wrote:
    Christopher Foyle wrote:
    CCP Sledgehammer wrote:
    Hey guys,

    Can I ask what version of the launcher you use with Singularity?


    Problematic launcher version: v2.1.684081


    OK, and am I correct in saying that after copying TQ you are using 655310, and it's working fine so far?

    Huh? What do you mean? Im trying to connect to sisi with the sisi launcher tool. What does TQ have to do with it? What do you mean by " after copying TQ "?


    Essentially, there's a good chance that you are going to be using a test version of the launcher with Sisi that has a penchant for breaking the client by forcing certain permissions on the Cider executable. By copying TQ you are getting a stable launcher, then by forcing it in terminal using "--args /server:87.237.38.50" you can connect to Sisi and patch (hopefully) correctly.

    Graphical QA Analyst | EVE Quality Assurance | Team TriLambda
    Manssell
    OmiHyperMultiNationalDrunksConglomerate
    #12 - 2014-05-14 15:53:54 UTC
    CCP Sledgehammer wrote:
    Vincent Athena wrote:
    CCP Sledgehammer wrote:
    Christopher Foyle wrote:
    CCP Sledgehammer wrote:
    Hey guys,

    Can I ask what version of the launcher you use with Singularity?


    Problematic launcher version: v2.1.684081


    OK, and am I correct in saying that after copying TQ you are using 655310, and it's working fine so far?

    Huh? What do you mean? Im trying to connect to sisi with the sisi launcher tool. What does TQ have to do with it? What do you mean by " after copying TQ "?


    Essentially, there's a good chance that you are going to be using a test version of the launcher with Sisi that has a penchant for breaking the client by forcing certain permissions on the Cider executable. By copying TQ you are getting a stable launcher, then by forcing it in terminal using "--args /server:87.237.38.50" you can connect to Sisi and patch (hopefully) correctly.



    O.k. so for those of us that are not programmers and don't touch the terminal, can you let us know when it's safe to just use the sisi launcher?
    Vincent Athena
    Photosynth
    #13 - 2014-05-14 16:16:31 UTC
    CCP Sledgehammer wrote:
    Vincent Athena wrote:
    CCP Sledgehammer wrote:
    Christopher Foyle wrote:
    CCP Sledgehammer wrote:
    Hey guys,

    Can I ask what version of the launcher you use with Singularity?


    Problematic launcher version: v2.1.684081


    OK, and am I correct in saying that after copying TQ you are using 655310, and it's working fine so far?

    Huh? What do you mean? Im trying to connect to sisi with the sisi launcher tool. What does TQ have to do with it? What do you mean by " after copying TQ "?


    Essentially, there's a good chance that you are going to be using a test version of the launcher with Sisi that has a penchant for breaking the client by forcing certain permissions on the Cider executable. By copying TQ you are getting a stable launcher, then by forcing it in terminal using "--args /server:87.237.38.50" you can connect to Sisi and patch (hopefully) correctly.

    I figured out what you meant. I have not run sisi that way for two years, and had forgotten about it. But it did work, and I did get on sisi.

    Know a Frozen fan? Check this out

    Frozen fanfiction
    CCP Sledgehammer
    C C P
    C C P Alliance
    #14 - 2014-05-14 16:35:15 UTC
    Vincent Athena wrote:
    CCP Sledgehammer wrote:
    Vincent Athena wrote:
    CCP Sledgehammer wrote:
    Christopher Foyle wrote:
    CCP Sledgehammer wrote:
    Hey guys,

    Can I ask what version of the launcher you use with Singularity?


    Problematic launcher version: v2.1.684081


    OK, and am I correct in saying that after copying TQ you are using 655310, and it's working fine so far?

    Huh? What do you mean? Im trying to connect to sisi with the sisi launcher tool. What does TQ have to do with it? What do you mean by " after copying TQ "?


    Essentially, there's a good chance that you are going to be using a test version of the launcher with Sisi that has a penchant for breaking the client by forcing certain permissions on the Cider executable. By copying TQ you are getting a stable launcher, then by forcing it in terminal using "--args /server:87.237.38.50" you can connect to Sisi and patch (hopefully) correctly.

    I figured out what you meant. I have not run sisi that way for two years, and had forgotten about it. But it did work, and I did get on sisi.


    Awesome, glad to hear that, Vincent!

    Graphical QA Analyst | EVE Quality Assurance | Team TriLambda
    Erin Crawford
    #15 - 2014-05-14 22:36:54 UTC
    Was on sisi to see the new optical flares, which are really beautiful btw, and instantly noticed that when undocking that the flashing lights are back! Outside station light, ship lights, stargate lights - they are all back and merrily blinking again - it makes a huge difference and most definitely adds more 'life' to the environment.

    Tested docking and undocking, jumping from system to system and had no issues so far. Audio also seems to be fine.

    Also, the blueish energy field thingy in the Stratios is back. Big smile
    http://imgur.com/YKR398P

    Nice optical flares:
    http://imgur.com/etIctg1

    Stations look amazing in the new lighting:
    http://imgur.com/OvlgMWU

    "Those who talk don’t know. Those who know don’t talk. "
    Lord Taca
    Lazy PPL
    #16 - 2014-05-14 22:53:58 UTC
    Hi,

    Cant play Eve, I open eve online launcher (v.2.1.655130), enter password, press play, and it wont start, it says launching then returns to play option.

    My mac details are:

    - Macbook pro retina late 2012
    - 2,5 gh, intel core i5
    - 8 GB Intel HD 4000 1024 MB
    - OS X 10.9.2

    tried to run it bypassing launcher and it still doesnt work.

    P.S.: I went to account management to get 3 hours so i could put my plex for in game time, i wont be able to do it due to this problem.

    Any other info you need just say so.

    thx
    Erin Crawford
    #17 - 2014-05-15 09:18:01 UTC  |  Edited by: Erin Crawford
    Hi Lord Taca, i had the exact same problem. I knew immediately it was due to me making a 2nd copy of EVE through which i had connected to SISI. The exact same problem you have occurred to me after I logged out of SISI and wanted to log in and connect to TQ - hitting the Launch button did nothing and it just 'timed out.'

    Here's what i did that fixed the issue for me, however, I have OSX's Time Machine backing everything up, if you don't have a backup I'm not sure you'll be able to fix your problem this way.

    I simply replaced the "EVE Online" folder in /users/(your name)/Library/Application Support/EVE Online (about 1.2Gig) with the one i had on my backup, which is unmodified my the SISI installation - in other words, it's the EVE Online folder originally used to connect to TQ and not SISI.

    I now have 2 "EVE Online" folders for the Application Support location and I replace one with the other depending on whether I connect to TQ or SISI.

    Hope this may help you.

    "Those who talk don’t know. Those who know don’t talk. "
    CCP Sledgehammer
    C C P
    C C P Alliance
    #18 - 2014-05-15 10:17:53 UTC
    Lord Taca wrote:
    Hi,

    Cant play Eve, I open eve online launcher (v.2.1.655130), enter password, press play, and it wont start, it says launching then returns to play option.

    My mac details are:

    - Macbook pro retina late 2012
    - 2,5 gh, intel core i5
    - 8 GB Intel HD 4000 1024 MB
    - OS X 10.9.2

    tried to run it bypassing launcher and it still doesnt work.

    P.S.: I went to account management to get 3 hours so i could put my plex for in game time, i wont be able to do it due to this problem.

    Any other info you need just say so.

    thx


    Hi Lord Taca,

    There's a possibility that it may have changed a key value in the config file for EVE under Application Support. Could you try the following out for me please?

    1. Open Terminal
    2. Type “cd Library/Application\ Support/EVE\ Online/
    3. Type "open config"
    4. In the resulting document (Which should be opened in a text editor), find this section:
    [Drive E]
    “Path” = “@tmp@”
    “Type” = “hd”
    “Label” = “tmp”
    “Filesystem” = “win95”

    5. Change the line “Path” = “@tmp@” to “Path” = “/tmp”
    6. Save and close the file.

    Run Singularity's launcher again and it should connect. Be sure that the " marks used are the same as other marks in the config file.

    Graphical QA Analyst | EVE Quality Assurance | Team TriLambda
    Aukake
    Imperial Academy
    Amarr Empire
    #19 - 2014-05-15 14:43:18 UTC
    The above mentioned method works! Thanks CCP Sledge! Was just about to go through the long process of deleting and reinstalling everything.
    Erin Crawford
    #20 - 2014-05-15 14:54:28 UTC
    Yup, just tried it myself, the “/tmp” does it.
    Blink

    "Those who talk don’t know. Those who know don’t talk. "
    12Next page