b12194, on Windows.
1) One actor with one behavior with non-hidden attributes. The attribute values were configured in the actor type's behavior page.
2) Place the actor on the scene designer, turn on instance customization for it and change the values. Everything works fine so far, including in the game.
3) If I turn off instance customization and back on again, the customized values on the scene designer are kept. This makes sense in case I turn it off by mistake, so I don't lose the customizations made.
4) The issue happens if I turn it off, reload the scene and turn it back on again. In this case the values configured on 2) are loaded again. I've seen a case where the user switched values in the actor type's behavior tab, turned off customization and reloaded the scene in order to get the new values onto the actor instance, then turned it back on again to further customize it for that scene. Took a while to figure out the instance customization was using older values.
Removing and replacing the actor on the scene designer does the trick. I'm unsure how this scenario was handled in previous versions.
Sample game attached. The behavior draws values on screen.
1) One actor with one behavior with non-hidden attributes. The attribute values were configured in the actor type's behavior page.
2) Place the actor on the scene designer, turn on instance customization for it and change the values. Everything works fine so far, including in the game.
3) If I turn off instance customization and back on again, the customized values on the scene designer are kept. This makes sense in case I turn it off by mistake, so I don't lose the customizations made.
4) The issue happens if I turn it off, reload the scene and turn it back on again. In this case the values configured on 2) are loaded again. I've seen a case where the user switched values in the actor type's behavior tab, turned off customization and reloaded the scene in order to get the new values onto the actor instance, then turned it back on again to further customize it for that scene. Took a while to figure out the instance customization was using older values.
Removing and replacing the actor on the scene designer does the trick. I'm unsure how this scenario was handled in previous versions.
Sample game attached. The behavior draws values on screen.