[4.13.1] Derived Data Assets disappear after unrelated crash
Build 4.13.1 Source
Previously I had most pawn code in C++ and some spread out in blueprints. This was messy, and with a recent engine upgrade became completely unstable (the blueprint pawn vehicle movement component was entirely disregarded after the first hot reload since reopening the editor). I have wanted to move to a "gameplay functionality in C++, declarative configuration data in data assets" approach anyway, but this is also proving unstable due to the data assets spontaneously disappearing.
I'm happy to supply my entire project if it helps with debugging. Please let me know. Thanks!
asked Nov 03 '16 at 11:03 AM in Bug Reports
After testing the issue, I was able to reproduce one of the data assets disappearing after performing a debug crash as the final step. However, what I did notice was that you are creating a circular dependency when you are referencing each of the data assets in each other. I believe that this is the cause of the issue that you're seeing when your data asset is disappearing, as when I did not reference one of the assets inside of the other's class, I did not see them disappear.
As a result, I do not believe that this is a bug, as I believe the circular dependency that was created is the culprit when it comes to this issue.
Let me know if you have any further questions or if you believe that I'm misunderstanding the issue and I'll be glad to continue investigating.
Have a great day
answered Nov 03 '16 at 03:14 PM
Sean L ♦♦ STAFF
Follow this question
Once you sign in you will be able to subscribe for any updates here