Possible Bug With Blueprint Editing in 4.7?

Hi Rudy,

Yes, it happens to me with other assets:

  • Characters from Couch Knight and Strategy projects, even within those projects when I convert them to 4.7.
  • An fbx model imported directly into a brand new 4.7 project.

The issue is more general since it happens for many properties: the steps I mentioned just illustrate it graphically, using a sample project.

Say, if:

  • I defined an “int32” UPROPERTY in a ACharacter class
  • Set a default value in a Blueprint
  • Dropped an instance of the blueprint in a map
  • then changed the default value in the Blueprint,

, then I when I run the map I would see that the instance’s property value didn’t get the new value I set in the Blueprint (as well as occasional crashes).