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?
Yes, that’s what source control is for. 
Thank you for letting us know @giorgos_gs
Like Melv said, your best course of action is to revert using source control to get back to a working state.
Regarding your ticket, I had a quick look, and it is lacking any way for us to reproduce this issue. Without this crucial piece of information, we will not be able to help you with your issue. Would you mind having a second look at your bug report and add the missing information?
Thanks!
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:
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.
Thank you for highlighting this issue and sharing your solution.
If you look a few posts up, you will see this exact issue being discussed. The issue has now been fixed in all supported versions of Unity. My advice to anyone experiencing this issue is to upgrade the editor and its packages to their latest versions.
If you are curious about the bug, here is the bug ticket. The ticket is still marked as being “In Progress”. This is because we haven’t shipped our latest 2023.1 packages yet. If you are using Unity 2023.1, you will automatically use Unity 2022.2’s 2D Packages, which has a fix for this issue.
@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?
In order to have the bug fixed, you need to update both the editor and the package. By just updating one of them, you will still have the issue.
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.
Sorry to hear that you had such a tough time to get the latest fixes. It seems like most issues you encountered are related to Package Manager, and like Unrighteouss pointed out, highlighting them inside the PSD Importer release thread is not the best place to communicate these issues.
Better places for this feedback would be:
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.
It actually doesn’t mean that at all. You’re obviously entitled to your opinion but that’s a negative spin.
What it does mean is that care is taken on what changes happen to this branch because introducing regressions in an LTS has consequences. Bugs in LTS can have a higher priority too as well as it being a commitment to actually fix bugs over a support period i.e. backport them all the way back to LTS version. Years ago there was no such commitment. Of course, yes, LTS does not mean bug free.
Every new version means moving to the next version; features are never backported. Internally, a released version isn’t off the radar at all. This thread though is about a package which is outside of that, actually something to do with the package manager itself by the looks of it.
Big respect to @MelvMay , @Ted_Wikman and other Unity devs for tolerating someone like deru, who does pretty much nothing but talk shit about your work here around…
@altepTest 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,
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:
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.
The 2D team are already aware of this thread. I’m not a dev on this feature though and the quote above is unrelated to this feature.
