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
- Shader graph node does not update to red when there is a precision mismatch between the base graph and the subgraph
- Gaps between fields cause accidental element selection when pointing slightly above or below "Element ..." text in a list of elements
- UI flickering in Unity Version Control when the merge options are opened
- Build for iOS with UnityAds fails with linker failures when performing a CocoaPods build
- NavMeshManager.LoadData takes a long time and causes performance spikes when enabling a NavMeshSurface with already instantiated NavMeshLinks
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a6