Massive Issue With 2D PSD Importer in Unity 2020.3.38f1

Unity Engine
,
1

I’ve already submitted a bug report, but I want this to be seen ASAP.

I think this is the ID: IN-15045

Simply importing a PSB file in a blank 2D template project leads to multiple NullReferenceException errors and hidden inspector properties making the package completely unusable, save for any workarounds (I don’t know of any yet).

This is what it looks like:

8397810--1108512--Example_Image.JPG
8397810--1108512--Example_Image.JPG1917×978 102 KB

Notice the hidden inspector properties on the right, and the multiple NRE errors.

So, I don’t want to complain too much here, but I’m losing faith in Unity’s 2D skeletal animation. I’ve been waiting for 2021 fixes for a really long time, and now even 2020 doesn’t work anymore. Very sad :frowning:

1 Like
2

Thanks we are already looking into this. Fix for 23.1 and 22.2 are on the way. We are working on making the fix back to 20.3, 21.3 and 22.1.

2 Likes
3

I also want to add that we are working on the other issues you have reported (slow triangulation and faulty weight generation in 21.3 and newer), we have a fix that we are testing, but unfortunately, our new bug reporting is less transparent than the previous system we had.

If these issues are preventing you from working in 21.3, do send me DM and we can try to sort it out.

1 Like
4

take your time, is not that people want to make games with your engine.

two months to fix nothing, that is some hard work there.

5

This was fixed a while ago, just update to the latest LTS.

6

yeah, is a bit more complicated than that

https://discussions.unity.com/t/892294/28

7

Not really, you were having trouble installing the version with the fix, but you figured it out.

8

yes really, probably you should check my posts there. I’ve had no trouble installing anything. They all installed just fine but they have switched on using an older version without telling me. which is not good design. probably why you can’t grasp the meaning of what I’m saying.

9

I did check your posts there, and I can grasp that you don’t understand what happened (it is confusing so I won’t pin all the blame on you).

In the following screenshot, (1) is the current latest version of the package, and (2) is the version you currently have installed. The package never regressed to an older version, you just mistakenly thought you had the latest version installed when you in fact did not.

8574806--1148351--Example.JPG

The package manager doesn’t randomly regress packages to older versions. Even if you install a new version of a package that isn’t compatible with its dependencies, the package manager will either update those dependencies, or Unity will throw errors (that has been my experience, and it aligns with everything you showed).

10

not sure how to explain this more clearly to you but I will try. but this is the last time, i don’t just want to repeat this and spam this thread forever obviously.

first you are not actually trying what I’ve done, I mean, download that stuff and try and see what happens. You are just using some information from your knowledge of unity that doesn’t apply to this topic.

I’ve downloaded the latest unity version and then created a 2D project which had the 2D package (with 7 packages included)

according to the package manager everything was updated to the latest version.

the 2D group packages doesn’t show all the info of the packages. only if you check them you see that it doesn’t use the latest ones. It tells you that if you know where to look into

11

Yeah, it’s confusing to use, that’s what I’ve been saying. You didn’t have the latest one and you realized that when you checked properly. I’m glad we agree, let’s end it here.