Official 2D PSD Importer 7.0 released for Unity 2022.1

Can I make a PSB. file appear merged in Sprite Editor, but each layer separated and sliced into sprites, like this:

Locks_0, Locks_1, Locks_2, Locks_3
Top_0, Top_1, Top_2, Top_3
Bottom_0, Bottom_1, Bottom_2, Bottom_3
Lock_0, Lock_1, Lock_2, Lock_3.

 

Can I have a PSB be split into sprites per layer, but appear as a flattened image in Sprite Editor?

 

I think I found a bug:

I think it has something todo with the facat that it wont name the slices after the layers if you do the slicing in the sprite editor.
As you can see, I can "fix" the issue by selecting another importer and reselecting PSD importer. But in this case all bones are gone.
Also checking "Automatic Reslice" fixes it most of the time.

I am using Unity 2022.2.0b7 and the following packages:


Another issue I observed was that I cant click any checkboxes in the PSD file Inspector.

 

Done

 

PSD Importer 7.0.1 and 7.0.2 is not working anymore on Unity 2022.1.14, 2022.1.15 and 2022.1.16

 

I can't seem to log into the issuetracker for some reason...but it's also happening in 2021.3.9f1.

 

I have an interesting problem where I cannot click on the PSD Importer Inspector. I recently upgraded my project from 2020.2 to 2022.1. All of my previous PSB Animation Rigs are still working as before, the only difference being I cannot edit them in Inspector. Same with newly imported PSB/PSD files. Should I make a back-up and try reinstalling the PSD Importer package?

Edit: I saw the Tracker, I will be checking it periodically! Thanks!

 

Thanks Ted, any update for Version 7.x in Unity 2022.1?

 

How's it looking, friend? I'm eager to get back to work ^-^

 

Fantastic plugin!

To improve normal map workflows for sprites is it possible to add a few things?

1) Normal map compress mode for sprites to enable normal map packing? Currently we are forced to use linear set none packed sprites for normal use. And can't use normal unpack.

2) The ability to tell a psb file to copy the sprite texture layout of another psb? That or the ability to assign a psb in the secondary texture slot of a sprite, and have it auto atlas like the parent texture.

This would help solving packing other data maps such as normal maps to follow the layout of the diffuse.

Currently as it stands, to use normal maps we are required use a separate psb and make sure the textures name, alpha size, and total exported textured match the diffuse so that they both pack the same. This can be tricky If the alpha is off a little. It's be nice to be able to just move and crop normal map textures based off it's name using the data from another texture (such as the diffuse)

Is this by any chance possible? It's tremendously help workflows.

Also does virtual textures work with sprites?

 

Thank you, I appreciate it!

 

I upgraded 2D PSD Importer from 7.0.2 to 7.0.3 and it broke my game.
I have Unity 2022.1.20f1 on Windows 10.

Check my pipe PSD.
Its moved 40 pixels down and now all my animations aruined.
How can I fast fix this?
New Incident created: IN-20061.

Can I downgrade?

 

I just tried installing the psd importer from the package manager in Unity 2022.1.4f1 and I am greeted by a bunch of errors like this one:

Code (CSharp):

1. Library\PackageCache\com.unity.2d.common@7.0.3\Editor\InternalBridge\TexturePlatformSettings\TexturePlatformSettings.cs(147,23): error CS1061: 'TextureImportPlatformSettingsData' does not contain a definition for 'crunchedCompressionProperty' and no accessible extension method 'crunchedCompressionProperty' accepting a first argument of type 'TextureImportPlatformSettingsData' could be found (are you missing a using directive or an assembly reference?)

This does not happen when you install the 2D feature package because it installs different versions than directly selecting the psd importer package.

The 2d feature package installs
"com.unity.2d.common": {
"version": "7.0.0"

"com.unity.2d.animation": {
"version": "8.0.1",

"com.unity.2d.psdimporter": {
"version": "7.0.0",

I know that 1.4f1 is not the most up to date sub version and I guess the issues might be related to that but apparently the 7.0.3 2d common and psdimporter packages don't work with this version. Therefore for anyone interested (as this didn't come up in any search) either specifying these numbers manually in the packages-lock.json and manifest.json or installing the 2d feature package are good workarounds.

 

@Ted_Wikman
hi Ted, thanks for responding so quickly . Yes this is discussed above but

plus in the bug ticket it even says verified as fixed in 7.0.3 leads me to believe 7.0.3 should not cause these errors. However the default package installed by 2022.1.4f1 is 7.0.3 and it still causes issues. Soooo at least for this editor version (which is not 100% up to date, yes, but there are 12 other people working on the project, can't update on my own without pulling the entire team along first) the bug is not fixed?

 

I've updated everything and still had the bug. Now for a really "lucky" event I've noticed this text hidden in the package manager. Like what the actual is this? it shows me that I have a certain version installed but the editor is using a different version. Who come up with this system? and why is not showing me the correct version that is used? Don't show me 7.0.3 if you use 7.0.2!! I really would love to talk with this developer.Find out what is in his head to include this showing a version but using another version

Ok, now what package is forcing the 7.0.2 instead of the 7.03? How do I figure this out and how do I get rid of it? It was too difficult to include what package is forcing this?



This is unity version 2022.1.20f1 with the 2D 7 packages pack added

I have also.



which of the above packages is the one that forces that package to not use the last version?

 

anyway, oh my god how I hate me doing this. here is a solution till they figure out how to untangle this mess.

click on the the "2D 7 packages tab shown above" click on the blue "Go to package view"

then click on the packages shown in the image bellow. use control to select all or do this for each one separately. click Unlock



then for each update to latest version as in image. unity will not gonna like it and throw a bunch of errors in the console. ignore them. they will go away once all three packages are updated



selecting the psb now works fine.

i just wanted to test something in unity and yet I'm back again working as beta tester and figuring out solutions.

 

Granted, this bug was present in LTS versions of Unity, but you are basically a tester if you're using non-LTS versions of Unity like 2022.1, and you're definitely going to run into more bugs.

However, I do agree that the new package manager is confusing (it's in 2021 LTS versions so it's not in testing). The "grouped" packages are really annoying to deal with, and I've only had headaches because of them. Updating packages isn't intuitive and was a pain to figure out.

For some reason, updating packages doesn't seem to update their dependencies anymore. I get a message saying "Changing a package that is part of a feature can lead to errors. Are you sure you want to proceed?" - this makes no sense, and this issue doesn't exist in 2020.3.

Something I used to like doing was deleting useless packages, but now that's a huge pain because they're grouped with useful packages.

This is the wrong place to complain about this, but we have to manually update 2D Animation and 2D PSD Importer so often that it may be kind of relevant haha.

 

I've downloaded the previous 2021 latest LTS version, was the same bug so I've uninstalled that one and tried the 2022 version, still the bug, then fortunately I've figured out a solution that works for me.

you are not protected against bugs if you use LTS.

LTS just means unity saying "we are done working on this, if something is really broken we will fix it eventually but we are moving to the next version"

not sure why people think LTS means is a polished product. Go figure.

 

Big respect to @MelvMay , @Ted_Wikman and other Unity devs for tolerating someone like deru, who does pretty much nothing but talk S*** about your work here around...

@dorusoftware Please stop provoking such a hostile atmosphere.

 

that is exactly what I wanted to say. My experience with unity was negative in the past two years. This doesn't apply to everyone else and I'm the first to recognize this, some have positive experience which is fine by me and I'm not annoyed by this. Not like other users here which don't like any criticism at all.

my "hostile behavior" as you called included,

• finding an unexpected bug
• searching forums, bugfix tracker suggest it was fixed.
• downloading the "fixed" versions
• didn't work
• had no idea what is going on
• got a lucky break and finding that the package manager will tell you that a version is installed but then it will use a different version, never knew about this and I'm using unity for 3 years.
• pointing out this is really bad design.
• providing solutions with screenshots for other users which had and will have this bug in the future.
• linking my solution in the bug tracking page https://issuetracker.unity3d.com/is...n-selecting-a-psb-file-in-the-project-browser where different users appear to have the same thing I've had but didn't had the luck to find that the package manager hides the version it uses from you

All the above while I'm really still quite angry with unity as a whole.

So if this is hostile from me. Go figure.

 

The Merge function in the Layer management tap is still fundamentally broken, as far as my testing goes
"REDIZIT, Dec 31, 2021" posted about this problem way back,
For more detail look at his post:
https://forum.unity.com/threads/2d-psd-importer-6-0-released-for-unity-2021-2.1187767/

Any news on this?

It would rly simplify the 2D workflow and logistics, and I would love to see a proper implementation of this

Update!
Turns out it has been fixed! That was not clear looking at the change log.
Did a test on a completely fresh/newest install and it works. 2022.1.23f1

Update 2x
But now I see the invisible bug that people have been talking about. It likely was a real bug at some point, but what I ran into was a bit different.
If multiple layers exceeds the original canvas size when merged the sprite is generated from the bottom most left pixel of those layers, and while it can merge into a wider sprite then the original canvas size, it will do so incorrectly. This is still the case if the offending layer is deactivated in the import settings
This is most likely to happen if you have pixels outside of the canvas in photoshop for whatever reason.

 

I just upgraded to the newest version of psd importer, and noticed that some characters look wrong, some part of their sprite are missing. I investigated the skinning editor and see that some geometry are not in the same position as I made them 7 months ago, they moved a little bit, so part of the sprite is hidden. This bug seems to be very inconsistent, because not all layers behave like this.
The only good part is that it seems other people are also experiencing some issues. So I am not alone in this,

 

by saying newest version, I mean 6.0.6. That is the newest version shown in my package manager

 

I know the psb importer kinda arranges the psb layers in a way that has smaller file size. This might cause the rig to look different every time you upgrade the importing solution.
Please make a import setting that is 100% safe and consistent. My file size is very small, so I don't need to optimize the layers arrangement.

 

Thanks for the fast reply. The most important thing is safety and consistency. Please fix it asap. New feature is not as important as that.
I quoted your words because I wanted to @ you. I will use @ next time

 

@Ted_Wikman I upgraded psb importer from 6.0.5 to 6.0.6, I can open the sprite editor again but it changed the rig. Some geometry are not in the same position as I made them 7 months ago, they moved a little bit, so part of the sprite is hidden.

 

@Ted_Wikman @MelvMay Sorry, how do I roll back to previous version of psb importer? I only see 6.0.5 and 6.0.6, which have critical bugs(6.0.5 looks fine but can't open the sprite editor, 6.0.6 can open the sprite editor but the previous geometries are moved).
Or how do I make it works again?

 

You can edit the manifest and packages-lock files Project\Packages\ with a text editor and replace the version number of the psb importer to the version you want. At the next refresh unity will load that version if possible.

 

I have many manual backups. But I haven't touched my 2d animation rigs for many months, I was working on other features. So when I updated my unity editor in the previous months, I didn't see any problem because the bug in psd importer 6.0.5 was only visible if I try to open the sprite editor.
I notice the bug now because the bug in 6.0.6 is visible in my characters.

 

thanks!

 

@Ted_Wikman @MelvMay I just check psd importer 7.0.3 with unity 2022.1.23, and the geometry of my rigs are also moved.

 

I know is too late for some of the users here but one of the most important advice I can give, which I've learned the hard way, same as you.

never update a project if you don't have a backup, and never update if you don't have a reason to update.

Did a new feature is something you absolutely need? maybe an annoying bug was fixed? Then try to update.

But if all works fine, don't do it. Do not touch that project. Is already a miracle it works, don't push your luck