Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2018.3.0a6
2018.3.0b4
Issue ID
1086969
Regression
Yes
Prefab loses object references when upgrading from 5.5 to 2018.3
Prefab loses object references when upgrading form 5.5 to 2018.3 - managed to get it down to a package that has only one VFX.
Repro steps:
- download the package mentioned in the comments
- open it with Unity 2018.3.05 or trunk
- Look at the effect4 prefab in Prefabs/Effects/PC/Effect4
- notice that the Effect on Collision object is none
- if you import this in Unity 2018.2.0a11 or older, it will reference the Effect prefab in the EffectParts folder
Reproduced with: 2018.3.0b5, b1, 2019.1.0a4 (trunk)
Cannot reproduce in: 2018.2.1f1, 2018.3.0a11,
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
- Crash on memcpy when opening a project that loads TSS files
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
JoeGrainger
Oct 09, 2018 09:10
Every single prefab that was upgraded from 2017.4 to 2018.3 has had it's references broken - everything is 'Missing' and I have to manually iterate through EVERY prefab to re-reference them. This is literally insane.