Thanks guys for taking the time.
On Pushing changes (3) it is more aimed at certain actions in UEFN that cause a desync with live edit, like editing devices through UEFN, or changing a component (Verse updating is the fastest one so far, but good to know it’s getting even faster)
In regards to Verse API, I am just an artist at heart trying to make my logic work, so even the slightest quirk of functional programming gets to me because I am used to interfaces and UIs to do things. Having to type an if statement to do anything except check for a condition is a crazy concept to me (maybe that part can be omitted when/if an interface were to be built) and we desperately need VS studio to provide some context-sensitive code and help a bit more with errors (errors are not indicative of the fault at all atm, the same error pops up on three different cases, like forgetting the “:=” or “set”).
On sequencer reset state, the cinematic sequencer device has a setting “keep state” but that breaks after a sequencer completes, it’s a bug and confusing to users that see that setting.
On weird rotation, I just want to rotate to places and have 10 types of easing curves with easing control (constant, linear, ease in, ease out, ease in/out, gravity, elastic in, elastic out, elastic in/out). The sequencer overcomplicates this, and the curve editor makes it even harder to be able to add weighted curves and control the easing because I have to search for the right axis instead of the movement itself.