4.17.1 Blueprint Doesn't 'Dirty' when using Reset to Default

I had a few blueprints that triggered a warning that they were saved without a version. I was going through each one, changing something, saving, compiling, changing it back, saving, and compiling. That got rid of the error.

However, I noticed that if I changed something away from default and saved/compiled, when I went back in and hit the ‘Reset to Default’ next to the item, it would dirty the save but not the compile.

Reproduction steps -

  • Open a blueprint.
  • Change a default setting on something.
  • Save and compile.
  • Hit the ‘Reset to Default’ arrow next to that item.
  • Notice that the asterisk shows up indicating that it needs to be saved.
  • Notice that the compile icon still has a green check mark.
  • Change that same item again and toggle it right back (not using the arrow).
  • Notice that the asterisk is there and the compile icon is now showing that it needs to be compiled.

UMG widgets do not exhibit this behavior. They show dirty when using the arrow…

macOS 10.12.6 - UE 4.17.1

Hello Onildera,

I was able to reproduce this issue on our end. I have written up a report and I have submitted it to the developers for further consideration. I have provided a link to the public tracker. Please feel free to use the link provided for future updates.

Link: Unreal Engine Issues and Bug Tracker (UE-49448)

Make it a great day