Recurring nameFileIdTable changes

Unity Engine
,
1

I’m seeing random PNG texture files in my projects get their .meta file updated with changes like the following:

nameFileIdTable:
background_0: -7443756053782179069

This is on Unity 2023.1.0b15, using 2D URP if it’s relevant.

If I revert the changes using source control they come back the next time I play or build the project.

I found the following which sounds like it might be similar, but suggests the issue was fixed in 2023.1.0b3:

What is causing these changes? Can I just ignore them and let the updates go into my source control? If this is a bug I have no idea how to report it as although it has happened 2 or 3 times over the past couple of weeks I have zero leads on what the trigger is.

2

Anybody have any ideas?

3

Experiencing the same here. Big project with lots of animation clips breaking because internalIDs keep changing on a lot of sprite sheets. Surprisingly it doesn’t happen for every sprite, only a few

4

I’m on 2023.2.10 and having this issue!

5

Having the same issue here, also 2023.2.10. Any updates?

6

Same Issue with Unity 6 Preview 6000.0.2f1

7

Just looked at the Issue Tracker and it’s apparently not fixed for Unity 6

8

Hello!
Sorry to resurrect this topic, but I have the same problem in Unity 6000.0.25.
When one of my coworker add png files in the project, the .meta created as a “{}” value for nameFileIdTable. But once I get the files through source control, the .meta file is immediately changed to add a value to this field, and it is added again to source control. Here is an example :
image

And if he update the .png later, Unity will finally update the .meta in the same way than mine. But if he already pushed the first .meta file on version control, it will create a conflict between its meta file and mine (even if they are identical).
The problem seem to be the fact that its first .meta file have a void nameFileIdTable field for some reason.

Is there a fix for that, or a way to be sure everyone will create the same .meta files ?

Thanks in advance.

9

Ok, after additional tests I can be more precise.

When I (or a colleague) add a png asset in our project, the .meta file created has an empty “nameFileIdTable” field (and this seems to be the issue).
But if I update it, reimport it, or if someone else get it through version control, the .meta file will update to add a value in the nameFileIdTable field.

This is problematic, as it creates conflicts in version control (as every people getting the png will update the .meta file on their side).

Our Unity version is 6000.0.25

Thanks in advance

10

I have reported this as a bug (CASE IN-99890)

It only happens if the editor has the Default Behaviour Mode set to “2D”, so the texture is imported as a Sprite. For default mode textures, the effect doesn’t happen.

I’m also a bit suspicious about the whole existence of the nameFileIdTable - it’s just a copy of the internalIDToNameTable on the top of the document, with the same names and IDs laid out in a different order, so one of them could probably go.

2 Likes
11

It’s on the bug tracker now: Unity Issue Tracker - "nameFileIdTable" entry changes in the .meta file when reimporting a texture while the "Default Behaviour Mode" is set to 2D

2 Likes
12

Hello!
Thanks a lot for creating the ticket.

But I see that it has now been updated as “fixed” in Unity 6000.1.5f1.
I’ve installed Unity 6000.1.5f1 a few weeks ago, and sadly I still have the bug, reproducible with the same steps that in the ticket :confused:
Is it possible that the fix is in a later version of Unity that 6000.1.5f1?
Thanks again