Hey Rudy,
Sorry for not getting back to you sooner, we were at a conference which unfortunately consumed most of our time. In regards to the first issue reported, it turns out the problem was on our end, and we have since been able to resolve it. As for the device we are using, we primarily use the HTC Pre for our in editor testing.
Regarding our second issue, we were unable to easily replicate the problem in a clean project. However, during our attempts to do so we managed to isolate the source of the problem. We are passing a fair amount of data through a BlueprintImplementableEvent so that we can edit UMG Widgets at runtime. The blueprint that handles this works just fine, however it seems to also be the source of the problem. On the first run, it works fine, but upon pressing play again, editing any values in editor, or even transitioning between levels, it fails. It may be a garbage collection or memory issue, but at some point the editor stops referencing it properly or something. We have found that simply opening the blueprint and hitting the compile button causes it to work flawlessly every time until we either close the engine or perform a hot compile. I’m including a screenshot of the blueprint in question for clarity, but I am not sure why it fails in this way. Perhaps you guys can gain some insight from this that we can’t. At least we’ve found a workaround, and it works fine in a packaged game.
