• Bugs

  • Missing/Unread Image Files from Photoshop

    английский

I will state first that while I've used other animation programs in the past, I'm very new to this software, so this could be a user error. However, I did search this issue extensively and tried everything I could find, so this may be a bug with the program.

After exporting a sequence of png files and the accompanying JSON from Photoshop CS4 using the included script, I attempted to bring these into Spine. By using 'import data,' I was able to bring in the JSON, but the images themselves won't seem to load in, displaying red rectangular outlines in their place. I then followed the instructions to manually select the images folder with the 'images' directory on the right side, but nothing updated, and I cannot find a way to directly attach the png files to the 'missing' image locations, either. However, all imported layers are named and placed correctly, although there are no images shown. When clicking 'open' at the bottom, it will display the folder with the images in it, but I cannot seem to do anything with them.

I am running Spine 3.6.35 Professional, which I just updated today, on a Mac with OS 10.12.5. While this could just be the result of me missing something really obvious someplace, I've retraced my steps very carefully many times, and I'm at a bit of a loss on what to do from here. It is especially concerning since I've looked at other posts in which image files were missing after importing a JSON from Photoshop, but selecting the image folder manually(as they did) doesn't seem to be fixing the issue for me. Hopefully someone will be able to help with or explain this. Thank you.

Related Discussions
...

  • TTimeSeerStudios

    • Сообщение #2
    • Изменено
    • Это сообщение на английский

    • Søren

    • Сообщение #3
    • Это сообщение на английский

    This does sound like the path is just incorrect.

    Unless you've specified a Path under each attachments properties, it will use the name of the attachment as the path. For example, you could have an attachment with the name images/head. This means Spine is looking for the head image under /images/. This path is relative to the path you have set for the Images node.

    I always save my Spine file next to where I saved my PSD file. And when exporting my images from Photoshop I place them in a subfolder called images. Then my Images path will always be ./images/

    Please show a screenshot of your tree with the path for your Images visible if you still have problems.

    I'll go ahead and provide some screenshots here to see if anyone can make sense of it or spot where this went wrong. When checking the attached images(under 'root') on the right, they are all named the same as the files in the images folder. I've tried right clicking to check for additional options, but that doesn't seem to be doing anything. At the bottom, the image path looks like it should be correct. I might suspect that the spaces in the names were causing an issue, except that the files without spaces are also having the same problem.

    I also noticed that in the 'SpineBoy' that was included as an example, the images folder actually displays all the images inside within Spine itself, with a little disclosure triangle to expand or hide it. On mine, the images folder is treated by Spine as though there is nothing in it, but when I click 'open,' the png files are all shown there through preview.

    • Nate

    • Сообщение #5
    • Это сообщение на английский

    Thanks for the screenshots. Spine is going to look for these files (though people almost always use PNG files):

    images/back arm.png
images/back arm.jpg
images/back arm.jpeg

    It seems your actual filename is images/back arm? Why don't your image files have a file extension?

    The photoshop script actually exported the files exactly like that with their extensions not included in the names, though if you click on the files through preview, they still read as .png images even without a visible extension. To test this though, I went ahead and manually added .png to their filenames, and after that Spine was able to find them. I never would have thought of that, especially since I hadn't heard of anyone else having to manually alter the extensions after exporting from Photoshop. Thank you for the response, looks like this mystery has been solved after all!

    • Nate

    • Сообщение #7
    • Это сообщение на английский

    That's very strange, the export script should not lose the file extension! We'll be updating the Photoshop script soon:
    #202 Improve Photoshop export script