Does it help Spritato to read PSDs that use fancier Photoshop features if you save the PSD in compatibility mode? That stores a bitmap for each layer in the PSD, so Spritato may be able to work.
I think this could help if it is a text layer other layer don't get to know. For adjustment layer, unfortunately, saving in compatibility mode does not auto apply them to the normal layers down below. The only work around is to encapsulate them into SmartObject or merge them directly to normal layer.
We are also unhappy with the current state of the Spine export scripts. We don't like that Photoshop is the script with the most features. We also don't like that the Photoshop script is so slow. There is a way to make it faster, but it's difficult, makes the code messy, requires rewriting the script which is a lot of work, may not work as well with older Photoshop versions, and even after all that it still doesn't help with the first issue: we don't want to force Spine users to use Photoshop.
Agree. It sucks when I only use CSP to draw but require me to have PS to do the export. The best case is to have full control of the export tool without depending on any other software like Photoshop not just because it require a monthly fee but Photoshop also limited what can be done. That's why, I decided to do it from ground up. Since I got full control of the app, I can do whatever I want when writing the app. The reason I could get the export speed so fast is because I could make use of many optimization techniques which is not possible when running a script inside Photoshop.
Beside export speed, I created the tools primarily for the Pixel Adjustment Layer feature which is very cool.
It solved an annoying export scenario that I feature requested a year ago ( Just an idea about a new tag for the PS export script ). When a normal layer of any kind of blend mode is placed across different attachments, I just need to tag that layer as pixel adjustment and it will be treated like a adjustment layer. It will auto merge with the attachments below it. This feature save me a lot of time when dealing with the export. I think it can also be done in the export script too.
As an alternative, we are considering having Spine process a folder of images. The images would come from an image editor script, but it would be very simple, only saving a full frame image for each layer and keeping the "groups" as a directory structure. Spine would see tag names in the image file names and process them similar to the Photoshop script, trim the images, and write the new images elsewhere. This means each image editor script doesn't need to do so much, as all image editors could benefit from using tags.
It will only work for some drawing software. For an instance, the Clip Studio Paint I use don't even have the option to export each layers as standalone image. The only way is to save to PSD because the (.clip) file format they use don't even have a file specification available.
) and I do believe that using Photoshop for drawing purposes (let alone animating) should be considered a crime 
