Skip to main content
J
jeffington
Participant
October 10, 2014

P: Extract Asset file format dropdown non-functional / buggy on MacOS 10.9

  • October 10, 2014
  • 6 replies
  • 265 views

More complete discussion here: http://graphicdesign.stackexchange.co...

The file format dropdown in the new 'Extract Assets' feature works only occasionally and (apparently) randomly, generally being stuck on the default png-32 setting. Would love to be able to produce SVGs with this feature! I'm running a fully updated version of CC 2014 (as of 10/10) and Mavericks OS. Otherwise its an awesome feature.

    This topic has been closed for replies.

    6 replies

    J
    J453
    Legend
    December 11, 2014
    This should be fixed in the 2014.2.2 update. Select Help>Updates... to install.
    divyamanian
    divyamanian
    Participating Frequently
    October 30, 2014
    OHHH. I see! Very interesting. Thanks for bringing it up! We are investigating.
    J
    jeffingtonAuthor
    Participant
    October 30, 2014
    Hi Divya,

    Hah, that's totally it! I use a non-retina Thunderbolt display primarily but it's powered by a retina 15-inch macbook pro. The Extract Assets dropdowns all work on the retina. Because I'm so used to having dialogs split between the two screens I somehow overlooked that there was a pattern here.
    divyamanian
    divyamanian
    Participating Frequently
    October 30, 2014
    Hi Jeff what display do you have? I wonder if it has something to do with retina screens vs non-retina? Basically want to know the screen resolution and DPI.
    J
    jeffingtonAuthor
    Participant
    October 14, 2014
    Hi Divya,

    I downloaded it from Creative Cloud and am pretty positive that it isn't a beta release or anything like that, just the standard.
    divyamanian
    divyamanian
    Participating Frequently
    October 14, 2014
    Hi Jeff! Thanks for reporting this issue. Have you by any chance installed pre-release versions of Photoshop with this feature? The reason I ask is we had this problem but we thought we fixed it in the release. If that is not the case, we certainly should look into this! Thanks for bringing it up.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices