P: Generate Image Assets doesn't honor document's ppi anymore

[thane]

In Photoshop CC 2017 when I create document and set in Image Size its Resolution to 150 Pixels/Inch and I generate image assets all generated images also have 150 ppi.

In Photoshop CC 2018 when I open the same PSD file and generate Image Assets, all newly created files loose source project's ppi, and are saved as 72 ppi.

In my everydays work I heavy rely on generated images ppi, and because of that, for me Photoshop CC 2018 is unusable.

Some screenshots.

Source PSD. Resolution set to to 150 ppi:

RackMultipart2018011147900y05c-7e90a800-9adc-4e01-80bf-723be71ed3e7-2111600474.jpg


JPEG generated in Photoshop CC 2017. Still 150 ppi as it should be:

RackMultipart20180111813671fcp-4b268842-d5f9-4a28-aa53-f218102a0043-1364257183.jpg


JPEG generated in Photoshop CC 2018 from the same source PSD file. 
Assets generator changed ppi to 72 by itself:

RackMultipart2018011150180dbd7-b5567e79-e3f9-4daf-ab5b-8d50b5447744-1067541571.jpg

Please, change it the way it was in CC 2017 when I can determine what ppi of generated images I want it to be.

[FeedbackCommunityMember]

I learn something new here every day. Just a question, though. Since the feature was designed for the web, not print, why do you need the resolution to be non-standard? I'm just curious what you're doing with the feature that needs this, how it works in your workflow,  not arguing about having the feature do what you say it should do.

I occasionally use Export As or SFW, not Generate Image Assets, to export primarily PNG files that I will be placing in a document intended for print, so keeping the resolution would be nice in my workflow, at least for either Export As or SFW. I assumed my use was unconventional, so the change in resolution didn't bother me. It is the same in 2017, btw, for SFW and for Export As. I haven't tested generating image assets.

[Hannah Nicollet]

Hi Kuba,

Thanks for the report. We logged a bug on the asset generator but it is still under investigation. We'll keep you posted on the progress of the issue. 

In the meanwhile, when you say that CC 2018 is unusable for you did you go back to CC 2017 and start using that again?  

Regards,
Hannah

[thane]

Sorry for the delay, I was on holidays and couldn't reply earlier.

@Cristen Gillespie: I've created a workflow, where I design slides for presentation in Photoshop, then generate image assets, combine them, and animate in seperate software.

@Hannah Nicollet: Thanks for being interested in my problem. Looking forward to see your investigation results. And yes, I had to move back to CC2017 as my daily driver.

[FeedbackCommunityMember]

Thanks for the reply. That's an interesting use I hadn't thought of. Now I will.

[thane]

Hi Hannah,

Any luck on investigating and confirming the bug?

[Hannah Nicollet]

Hi Kuba,

When the fix is in a pending update I'll post to this thread to let you know it's coming. In the meanwhile it's in progress.

Thanks,
Hannah

[FeedbackCommunityMember]

Has this been resolved? Or is there a rollback from CC 2018 to CC 2017? I am experiencing the same issues.

[thane]

As far as i know nothing has changed, we still have to wait, right @Hannah Nicollet: ?

[FeedbackCommunityMember]

I've relied on this as well and have had to switch back to 2017. I design graphics for print use. I build coordinated graphic sets for products such as planners and scrapbook pages. I like to have the bits all together on one artboard the size of a finished project to see how they go together. The generator saves so much time. but in 2018 it's useless for me. is there a fix coming?

[Kukurykus]

Can some of you who moved back to CC 2017 check is that broken also when you choose 'Export As...' or 'Quick Export as PNG' from 'Layer' menu. So is exported layer created with other resolution than document it was exported from? In CC 2018 it is always 72dpi irrespectively of current document res. Reading this topic I assume that wasn't intended by engineers, so described bug in this topic is a bigger problem.

Additionally I found a note that says it's a bug they can't fix it yet in this file (you open in edit mode):

C:\Program Files\Adobe\Adobe Photoshop CC 2018\Required\Plug-ins\Generator\assets.generate\lib\dom\document.js

Look for a part starting with: "TODO:" (without double quotation marks)

You can also read my post in related topic:

https://feedback.photoshop.com/photoshop_family/topics/quick-export-keeps-crashing?utm_source=notifi...