Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.4f1
2022.2.0b5
2023.1.0a6
Issue ID
UUM-13561
Regression
No
Prefab does not save the Input Action Reference when the button is used to assign a value
Reproduction steps:
- Open the attached project (“PrefabBug.zip“)
- Select Assets/TestPrefab
- Open “Testprefab”
- In the Inspector press the button “Assing Input Action Reference“
- Save and close “Testprefab”
- Select Assets/TestPrefab
- Observe the field called “Input Action Reference”
Expected results: “Input Action Reference” field contains a value
Actual results: Value is not saved
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.4f1, 2022.2.0b5, 2023.1.0a6
Reproduced on: Windows 11
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
This is not a bug, but a limitation in the Prefab system.
InputActionReference.Create creates a ScriptableObject in memory and SOs are categorized as Assets even when they only exists in memory, which is the case here.
The Prefab system does not support saving objects categorized as Assets to a prefab and a Prefab asset can't reference an object that only exists in memory, so the reference is removed from the final Prefab when it is saved.
A work around is to make the ScriptableObject an asset after it has been instantiated, but before saving the prefab. Simple use https://docs.unity3d.com/ScriptReference/AssetDatabase.CreateAsset.html after calling InputActionReference.Create
Resolution Note (2023.1.X):
This is not a bug, but a limitation in the Prefab system.
InputActionReference.Create creates a ScriptableObject in memory and SOs are categorized as Assets even when they only exists in memory, which is the case here.
The Prefab system does not support saving objects categorized as Assets to a prefab and a Prefab asset can't reference an object that only exists in memory, so the reference is removed from the final Prefab when it is saved.
A work around is to make the ScriptableObject an asset after it has been instantiated, but before saving the prefab. Simple use https://docs.unity3d.com/ScriptReference/AssetDatabase.CreateAsset.html after calling InputActionReference.Create