Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.5f1, 6000.2.0b3, 6000.3.0a1
Votes
8
Found in
6000.0.48f1
6000.1.2f1
6000.2.0a10
6000.3.0a1
Issue ID
UUM-104536
Regression
Yes
"nameFileIdTable" entry changes in the .meta file when reimporting a texture while the "Default Behaviour Mode" is set to 2D
Reproduction steps:
1. Open the attached “IN-100296.zip” project
2. Drag any texture/.png file into the Project Window
3. Right-click on it and press Show In Explorer
4. Open its .meta file with any text editor
5. Find the “nameFileIdTable” property
6. Observe that it is empty
7. Right-click again on the texture and press Reimport
8. Observe the “nameFileIdTable” property again
Expected result: “nameFileIDTable” remains empty
Actual result: “nameFileIDTable” is updated with one entry
Reproducible with: 2023.1.0a16, 6000.0.48f1, 6000.1.2f1, 6000.2.0a10
Not reproducible with: 2022.3.61f1, 2023.1.0a15
Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: no other environment tested
Notes:
- Also reported in Discussions: [https://discussions.unity.com/t/recurring-namefileidtable-changes/917141|https://discussions.unity.com/t/recurring-namefileidtable-changes/917141|smart-link]
- In the real world, this issue is causing Version Control issues. The 7th step is not usually somebody reimporting the file, but somebody pulling the file (and its .meta file) down through Version Control
- Also reproduces on a new project if the Default Behaviour Mode is set to 2D in the Project Settings
- The new entry has the same information as the entry inside “internalIDToNameTable” property
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
GabrielWink
Jun 23, 2025 11:28
Hi!
I'm using 6000.1.5f1, and sadly I still have the bug, reproducible with the same steps that in the ticket :/
Is it possible that the fix is in a later version of Unity that 6000.1.5f1?