Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
3
Found in
2018.3.0a6
Issue ID
1065694
Regression
No
[Nested Prefabs] "PPtr cast failed when dereferencing! Casting from PrefabInstance to Prefab!" after upgrading Corridor scene
To reproduce:
1. Download "Corridor Lighting Example" from the Asset Store to 2018.3.0a6 (or any older version);
Observed this issue in 2019.1.0a11.
Steps To Reproduce:
1. Open Unity version 2018.2.0f2.
2. Download and import Tower Defense Template.
3. Load the Menu scene and Run
4. Exit and Open the same project in 2019.1.0a11
2. Close the project and open it with 2018.3.0a7;
3. Open "CorridorDemo" scene;
4. Enter Play mode.
Expected result: Prefabs are upgraded successfully, without any errors.
Actual result: Errors are spammed to the Console: "PPtr cast failed when dereferencing! Casting from PrefabInstance to Prefab!", moving and emissive spheres fall off the screen, the whole scene is dark, even after Generating Lighting.
Reproduced with: 2018.3.0a7, where Nested Prefabs were introduced.
Not reproduced with: 2018.3.0a6.
Fixed in: 2019.1.0a4
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
ClayChi
Sep 13, 2018 14:11
I tried upgrading my project to 2018.3.(first public beta) it gave PPTR cast failed errors of bunch. When I click to error to see where it's pointing, it was the models directory or model prefabs directory (not the asset itself), but not for all models I believe, some model prefabs only giving same error over an over.