You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unchecking "exports clipped to doc bounds" was a critical part of my workflow in exporting assets from storyboard PSDs for animation, and unfortunately no longer works. All layers are still cropped to document/masked bounds by default when generating PNGs. I just recently updated to 22.5.1
I'm sure there are other malfunctioning settings, but this was the most critical to my daily workflow.
The text was updated successfully, but these errors were encountered:
When you say "unchecking", are you using the Generator Configuration extension? Maybe that is malfunctioning. I tried to reproduce the issue using the extension, but the option was set correctly.
Let's check the generator.js file (in $HOME on Mac, %USERPROFILE% on Windows).
You should see "clip-all-images-to-document-bounds":false,
Next check the generator log: ~/Library/Logs/Adobe/Adobe\ Photoshop\ 2021/Generator/generator_latest.txt %USERPROFILE%\AppData\Roaming\Adobe\Adobe Photoshop 2021\Generator\logs
At the top, you should see what options were loaded. If that doesn't match what you saw in the generator.js file above, then you likely have another settings file blocking.
Unfortunately that all checks out. The other generator settings seem to be working properly (though my use is limited of those). The clipping to doc bounds set to false, however, continues to clip the images. Again, this only happened as soon as I updated to 22.5.1.
Unchecking "exports clipped to doc bounds" was a critical part of my workflow in exporting assets from storyboard PSDs for animation, and unfortunately no longer works. All layers are still cropped to document/masked bounds by default when generating PNGs. I just recently updated to 22.5.1
I'm sure there are other malfunctioning settings, but this was the most critical to my daily workflow.
The text was updated successfully, but these errors were encountered: