Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1141846
Regression
No
Correct serialization type flag will not be resent to Perforce if binary asset is added to text asset via AddObjectToAsset
How to reproduce:
1. Open attached project ("CreateAssetsAndTestImport.zip")
2. Click Game Object/Create Main Asset (Text)
3. Check out the project in Perforce - you should see the file added with its type set to text
4. Click Game Object/Create Sub-asset (binary)
5. Check out the project in Perforce - you will see that the file type has not changed.
Expected result: Perforce gets notified by Unity to change the file type to binary since the asset contains data that cannot be text-serialized.
Actual result: Perforce is not notified to change the file type.
Reproduced in: 2019.2.0a10, 2019.1.0b10, 2018.3.12f1
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
- Shadows flickering when a Mesh's Cast Shadows are set to Shadows Only and Camera is moving with Spotlight
- AudioMixer exposed parameters cause assertions when hidden and prevent the drop-down from functioning
- Package Manager/My Assets: 401 Response code trying to download a paid asset store package
- TrailRenderer.SetPosition will log a Index out of bounds error when index is in bounds of the positionCount property
- [URP] Graphics.DrawMeshInstancedIndirect rendering correctly after clicking an another application/refreshing Assets
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a6