Some help on hot reload?

Development Programming & Scripting
1

Hi there,

Well, recently I figured out that the majority of the problems regarding editor instability I was facing was due to a probable misuse of the hot reload functionality.

I googled a bit but coudn’t find any text that goes deep in the hot reload system, how to use it properly, etc. All I could find was basically people saying to don’t use hot reload for nothing aside from simple local changes in functions and that isn’t too much meaningful to me.

I would appreciate any links for good texts regarding hot reload and how to use it properly.

Oh, another thing. In some posts here in the forum I found some ppl telling the OP to just disable hot reload and never use it in order to avoid bigger problems and for every time the code should be compile you must close the editor before compiling, and reopen after the compilation have finished. I was wondering how one could never rely on the hot reload? I mean, I have a pretty decent PC and it takes about 1 minute to open the editor here for a small project. If I have to to that every time I need to compile my code the workflow will be pretty damaged by this. So I want to ask how you guys manage this stuff and if maybe there is some setting in my editor that is slowing the initialization down that I could disable to make it faster?

Thanks in advance.

2

Unfortunately my experience applies only to OS X. For me, Hot Reload always crashes if I am adding a BlueprintableEvent, a BlueprintRead or ReadWrite Variable, or a Blueprint accessible function. It never crashes if I’m adding code or non-UPROPERTY variables. Adding classes is much worse and takes me about an hour of messing around to get the editor to even start again, I believe this to be mac-specific but I would use caution on VS too and not attempt to Hot Reload when doing so.

I batch up my inclusion of blueprint accessible variables and function and do them all at once, reloading the editor, then I hot reload code changes for often the entire day and that is less disruptive to my workflow.

I get around the irritant of this by opening the editor from XCode and I presume from VS the same could be done. It is still slow, so I wait about a minute, but since I know what’s going to work and what will fail, I just kill the editor from XCode and then compile it and my changes.

I personally can’t believe it’s supposed to work this way, but it’s been my experience and so I do it.