Blueprint Nodes Transient After Restarting Editor - Renaming to Blame?
I have a blueprint transient bug to report. I'm getting a possible variant of this problem: https://answers.unrealengine.com/questions/192836/cant-save-blueprint-referenced-in-enginetransient-1.html
I have a PlayerController blueprint that includes some function calls to a blueprint function library. Those function call nodes have something wrong with them, though; depending on what I do, they sometimes show up as transients and prevent me from compiling or saving the PlayerController:
When I try to save, I get this error:
If I delete those nodes and re-add them, or if I re-compile the blueprint function library they come from, the PlayerController blueprint compiles correctly, but only for a little while. If I close the editor and reopen, they show up as transients again.
I may have at some point had a different function library with the same name, deleted it, then renamed the one I kept to the current name. Here's what I mean:
I feel like I've had a lot of problems when renaming blueprints to names I already had a blueprint named.
Unfortunately, I don't have a great workaround for now other than recompiling the library every time I need to update the player controller. I think I'm going to try completely rebuilding the blueprint function library next. Epic, please let me know if there's any more info I can get you about reproing.
asked Apr 14 '15 at 10:19 PM in Blueprint Scripting
Follow this question
Once you sign in you will be able to subscribe for any updates here