PSB issue: How to export Sprites from Unity (and update Sprite-References) ?

Hi,

I'm facing an issue with PSD importer when upgrading to Unity's current LTS 2021, where my sprite references are all gone after the upgrade. This only affects sprites in PSB Prefabs, as it seems.

So my question is:

Is it possible to simultanously
- get the sprites out of the PSB (export sprites)
- save them in a separate asset (sprite-atlas?)
- have the project update it's sprite-references to the new asset(s)

...so that there'll be nothing referencing the original PSB file/prefab, before attempting another try on upgrading the project.

Thanks in advance!

 

Are you properly source-controlling and maintaining the assigned GUIDs contained in the original metafiles??

AFAIK it should just stay linked, unless Unity has a bug or the import process has substantively changed. Here is why:

Some info about Missing script warnings, GUIDs, renaming GUIDs, etc:

https://forum.unity.com/threads/problem-with-git-and-missing-scripts.1090876/#post-7024801
https://forum.unity.com/threads/scr...ead-after-loading-editor.998413/#post-6487297
https://forum.unity.com/threads/scr...ead-after-loading-editor.998413/#post-6488230

EVERYTHING in Unity is connected to the above GUID, which is stored ONLY in the metafile.

It is super-easy to inadvertently change it by renaming outside of Unity. Don't do that. Instead:

- close Visual Studio (important!)
- rename the file(s) in Unity
- in Unity do Assets -> Open C# Project to reopen Visual Studio
- now rename the actual classes, and MAKE SURE THE FILE NAMES DO NOT CHANGE!

If you are NOT using source control while you do this, renaming files is an EXTREMELY dangerous process. Use source control at all times so that you can trivially revert if you miss a critical step and damage your project.

If you are not already doing so, please consider using proper industrial-grade enterprise-qualified source control in order to guard and protect your hard-earned work.

Personally I use git (completely outside of Unity) because it is free and there are tons of tutorials out there to help you set it up as well as free places to host your repo (BitBucket, Github, Gitlab, etc.).

You can also push git repositories to other drives: thumb drives, USB drives, network drives, etc., effectively putting a complete copy of the repository there.

As far as configuring Unity to play nice with git, keep this in mind:

https://forum.unity.com/threads/prefab-links-keep-getting-dumped-on-git-pull.646600/#post-7142306

Here's how I use git in one of my games, Jetpack Kurt:

https://forum.unity.com/threads/2-steps-backwards.965048/#post-6282497

Using fine-grained source control as you work to refine your engineering:

https://forum.unity.com/threads/whe...grammer-example-in-text.1048739/#post-6783740

Share/Sharing source code between projects:

https://forum.unity.com/threads/your-techniques-to-share-code-between-projects.575959/#post-3835837

Setting up an appropriate .gitignore file for Unity3D:

https://forum.unity.com/threads/removing-il2cpp_cache-from-project.1084607/#post-6997067

Generally setting Unity up (includes above .gitignore concepts):

https://thoughtbot.com/blog/how-to-git-with-unity

It is only simple economics that you must expend as much effort into backing it up as you feel the work is worth in the first place.

"Use source control or you will be really sad sooner or later." - StarManta on the Unity3D forum boards

 

@Kurt-Dekker thank you for your Post, man! I'm using Source Control (and Git as well, via Terminal since I'm working on Ubuntu, and thus I'm using Rider as my primary IDE) so I feel a little bad that you went all the way referencing the way to set up SC just for me - but I do appreciate it. Also, I assume your infos reference Assets in general, since you talk specifically about classes/scripts? I'll checkout the posts you've linked and see if I can solve my issue with that information, and then I'll post the results here after. Thanks again!

 

@Ted_Wikman

The Issue (broken sprite references in Sprite-Renderer components) occurs after Upgrading from 2020.3.32f1 (Personal, Ubuntu Linux) to 2021.3.0f1 (Personal, Ubuntu Linux). The Upgrade from the previous version to 2020.3.32f1 on the same system went smoothly.

Regarding the 2 PSB files, they're just sketched prototypes - I'll pm them.

FYI, if it's useful to you. Some history regarding file creation / etc, as far as memory serves...

Draw in Sketchbook (Android) => export PSD => transfer to Ubuntu System => import & save in Krita-Format & edit with Krita => export again to PSD => rename to PSB & copy into project assets.

Can't guarantee the above process to be exact, though.

 

I am running into a similar issue. I am trying to create a new 2020 project and pull assets from my alpha 2022 project as I was doing some experimentation with ECS. But I am seeing that when I export my sprites from 2022 and import then into 2020 any other assets that are included in that same package that referenced those sprites lose their connection.

Is there a procedure here I am missing?

 

Ah, it appears to only be sprites that are Multiple frames. Appears that there is some kind of incompatibility with multiframe sprites from more recent unity versions with older versions. Man that sucks. Doesnt seem like the converstion should be that complicated. Would be nice if the Package Exporter had a target Unity version option to it and could do that.

 

No that doesnt make any sense. In looking at the file contents of the .meta files they are nearly identical. Same fileformatversion, same GUIDs for the sprite sheet entries. Doesnt make any sense!