Can I really depend on Live Coding?
#Does Epic themselves use Live Coding?
snow yew
tight patio
Can I really depend on Live Coding?
It Depends™️
There's things it's safe for, provided you turn reinstancing off in the editor preferences, and under no circumstances ever disable live coding, even if you don't want to use it.
However, there's a lot that isn't safe
#cpp message
snow yew
If things does get corrupted due to livecoding , can it be rescued?
tight patio
the corruption is permanent if it's been saved into the asset. Following the above steps guarantees it will only be temporary.
Only use it for the specified things, disable reinstancing, and do not under and circumstance turn live coding off, and you'll be safe.
Oh, while you're at it, disable compilation on creating a new class. Creating a C++ class in editor triggers a hot reload by default which is a questionable design decision, but hey it exists.
snow yew
Argh, any UFUNCTION cannot be live coded? The problem seems to stem from the reflection to blueprint part....
Im pretty sure ill live code something i shouldnt when im in heavy production + tired
tight patio
Argh, any UFUNCTION cannot be live coded? The problem seems to stem from the ref...
Adding/removing/changing parameters, no it cannot.
Editing the function body, yes it can.
snow yew
How was your experience? How do you discipline yourself not to press live code when you have made a param change
tight patio
I don't live code, aside from working with Slate everything else that needs that level of frequent change I do through BP or parameterization.
It's very easy to learn not to press the button for things that you can't do it for as well
The threat of corruption tends to be a pretty big motivator :P