Quantcast
Channel: General - Epic Developer Community Forums
Viewing all articles
Browse latest Browse all 9425

Raising awareness for Struct/Enum modification bug / workaround

$
0
0

Wanted to post this to raise awareness for those creators that may use BP generated structs and enums in your projects.

TLDR: When you need to modify a BP generated struct or enum follow these steps

  1. Save your current work
  2. Make the change to the struct/enum (rename or add property/entry)
  3. Save the struct/enum
  4. Exit the editor WITHOUT SAVING anything else
  5. Relaunch the editor to resume working

More info:
When you modify a Struct or Enum that is already referenced in loaded BP classes, those referencing classes will be marked dirty. If you (very reasonably) Save All at this point, these referencing BPs will become damaged. You won’t see any errors in your BPs when working. However you will see errors in your output log when loading these BPs and your game will not package until they are resolved. Up until now this was a tedious process of renaming the struct/enum and then opening all referencing BPs and compiling / re-saving them.

Further, if you continue to work while your BPs are in this damaged state, it’s possible to fully corrupt them resulting in being able to no longer open them or other classes that reference them. I have had this fully brick projects where the asset reference chain would load corrupted BPs crashing the editor on launch.

For years I have run into this bug over and over in many engine versions and could never understand what the cause was. I recently found this youtube vid (not mine) that finally explained the cause and provides the workaround.

I reported a bug with full repro steps and logs on UDN so hopefully we can finally get this fixed.

2 posts - 2 participants

Read full topic


Viewing all articles
Browse latest Browse all 9425

Trending Articles