Be careful with long with long path names.

[bernhardrieder]

I've encountered a very annoying issue where my project couldn't ever find the TensorFlowComponent after moving my project in some new folders. After a few hours, I found your suggestion on https://github.com/getnamo/tensorflow-ue4-examples/issues/12 about the long path names in Windows 10 which I tried but wouldn't help. So, I decided to move my project some hierachies down and there you go! It works again.... I don't know if that's a common issue because I've encountered it the first time but maybe you could add that to the known issues section :) Or, do you know a solution to this problem? After a little research, it seems like that it is an issue with UE4 itself rather than Windows 10.

[getnamo]

I don't know how to get around long path names unfortunately, only mitigating option I can think of is moving the python folder down to the project level instead of binaries/win64, but I haven't investigated changing directories that way in the python plugin yet.

I'll mark this as an enhancement with help wanted.

[bernhardrieder]

Renaming the unreal engine python plugin folder also seemed to cause an error during startup. Because I was renaming this folder and then I encountered an omnious error that something can't be found. Renaming it back to the original name solved that but I'm not sure if it was just a coincidence.

[getnamo]

note to self:

• There needs to be a way to warn the user based on project location that things might not work due to path being too long.
• Ideally add support for https://github.com/getnamo/tensorflow-ue4/issues/36 so that external programs may install the python dependencies to shorter paths, potentially mitigating this issue