Use for 4.13

[20tab]

Use for 4.13

[rdeioris]

the error is harmless, on startup the plugin tries to import the ue_site.py file where you could place initialization code. If you want to silence it, just create an empty ue_site.py into /Content/Scripts. Soon we will change it to a warning or a simple info message

[rdeioris]

This is the version we are currently using for development (albeit we continue to support 4.12). So you should not have problems

[LarsGroh]

Thanks!

[LarsGroh]

Hi,
I'm getting this error message in the output log when opening the editor after having set up and compiled everything:

LogPython: Python VM initialized: 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit (AMD64)]
LogPython: Python Scripts search path: ../../../../../../workspace/UE4/XXX/XXX/Content/Scripts
LogPython:Error: No module named 'ue_site'

[RonFischer]

Me too

On Sep 13, 2016 5:14 PM, "LarsGroh" [email protected] wrote:

Hi,
I'm getting this error message in the output log when opening the editor
after having set up and compiled everything:

LogPython: Python VM initialized: 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit (AMD64)]
LogPython: Python Scripts search path: ../../../../../../workspace/UE4/staud/GT_VIS/Content/Scripts
LogPython:Error: No module named 'ue_site'

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#20 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK2vQpnaSQfq4YvcMuRo-3aFl6_eJwx6ks5qpmmIgaJpZM4J7Wr1
.

[LarsGroh]

Thanks - good to know where to put init-stuff!