[Open Beta] Procedural On-the-Fly Animation in UE4: iTween!

[ttv_seblovely]

@;645275

So your blueprint is referencing a script from C++; you’re going to have to replace every single instance of iTween with the new blueprint-only calls. Then compile and save, it should be fine as long as there are no traces of C++ iTween calls whatsoever.

Hot reload is going to take ages the first time or if you edit any iTween source files, but after it’s been compiled it shouldn’t take long if never changed - at least that’s the case for me. I know it’s super unhelpful to say “hey, works on my system” but that’s pretty much the size of it. I think your best bet is to remove the plugin and go back to the C++ version. Give the engine a little time to acclimate, hot reload times shouldn’t be a problem for long. If they continue to be, if you’re comfortable with it I’m glad to take a look at your project and try to figure out the stopgap.

Thanks so much for your help - I really appreciate you not only offering this free plugin but helping scrubs like myself out. I removed all the references and we’re back in working order! However, in reference to the hot reload times with the c++ version, I was noticing painfully long hot reload times even with simple changes to classes unrelated to itween. I realize this makes no sense because the compiler has no reason to rebuild the itween classes if they remain unchanged, and I’m running a fairly strong overclocked 3770k on an ssd which averages ~4 second hot reload times before adding the plugin.

So you’re suggesting it may need an adjustment period and that if working properly my hot reload times should remain the same unless fiddling with the itween classes, correct?