I have a older blueprint that I made in previous versions of the engine that gives me some warnings that can be ignored but the problem is that I now lost some work on a crash because I thought it would save on compile.
Save on Compile is: On success only. It compiled successfully, it just had warnings, it worked, yet it never saved.
Either it is a bug or the setting needs to be named differently.
Hi Davision,
I am unable to recreate this issue as shown in the image below. If I create a blueprint that generates warnings, it is not “successfully compiled” and thus not saved:
However, you say your Blueprint “compiled successfully, it just had warnings.” So it had a green check in the “Compile” box? If so, could you send me some simple repro steps I can follow to recreate the issue here?
So what you are saying is:
BP gets compiled (without errors), BP fully works at runtime and BP gives out warnings = Not successfully compiled?
Makes no sense to me, it compiled successfully after all and all the warnings are nothing that impact the result.
Hi Davision,
Upon further examination, and taking your point that the compile could be considered successful if it compiles and only gives warnings, not ultimately failing, I have entered the following bug report: JIRA: UE-19713. If this issue is addressed at some point in the future we will update this post.
However, I did notice that (in my repro at least) upon compiling, there is an asterisk present in the tab, prompting you to save. Also, if you try to close the project without saving, you will be prompted to save the unsaved blueprint that contains the warning. So this only seems to be an issue if the editor crashes before you have a chance to save after compiling a blueprint that contains one or more warnings.
Let me know if that is accurate, or if you are experiencing this under different circumstances.
Thanks for the feedback.
