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

[JaredTherriault]

@Veovis Muad'dib;149985

I don’t use the default folder structure. I organize my assets by author:

• If I created something it goes in ./Veo/
• If I commissioned something from someone else it goes in ./Author/ with a license file as well as details of the transaction.
• If something is open-source/public domain/etc it goes in ./Third Party/Author/Project/, with a license file and a link to the original.

Makes it far easier to keep track of what I’m allowed to distribute, what I’m using for prototyping but have to replace before I sell, etc… After that I typically use the default folder structure for my own stuff and whatever the author used for anything third party.

Basically what I’m trying to say is: Please don’t force directory structures if you don’t absolutely need to, and make it easily configurable if you do need to.

Veo, thank you for this valuable feedback! This is definitely something we’ll have to consider and try to find a new approach for. Blueprints are, by nature, a closed beast so I’m not sure if this is something we can conceivably make happen with the content-only release; when we have the C++ implementation ready we’ll have a lot more flexibility on that.

At this time I’d like to formally request some input from Unreal devs - What’s the deal with blueprints and file references?

EDIT: Brain lapse, you can easily move the package after you import it to the engine the first time. Put it in Contents\Blueprints first, then open up the iTween.uasset blueprint. If there are no compile errors then you can simply use the content browser to move the iTween folder using "Move "