cannot find files when Open Unreal and use it to open DeepDrive.uproject

[ybxbupt]

[ 0]LogLinker:Warning: Asset 'H:/deepdrive-sim-master/deepdrive-sim-master/Content/TuningCars/Textures/NUMBER.uasset' has been saved with empty engine version. The asset will be loaded but may be incompatible. [2018.11.20-05.53.30:821][ 0]LogLinker:Warning: 无法寻找到文件'/Game/TuningCars/Maps/Demonstration_BuiltData' [2018.11.20-05.53.30:821][ 0]LogLinker:Warning: 无法在加载H:/deepdrive-sim-master/deepdrive-sim-master/Content/TuningCars/Maps/Demonstration.umap时寻找到资源'/Game/TuningCars/Maps/Demonstration_BuiltData'的文件。 [2018.11.20-05.53.30:822][ 0]LoadErrors:Error: 错误 /Game/TuningCars/Maps/Demonstration : 无法寻找到资源的文件。 /Game/TuningCars/Maps/Demonstration_BuiltData [2018.11.20-05.53.30:822][ 0]LogLinker:Warning: 无法寻找到文件'/Game/TuningCars/Maps/Demonstration_BuiltData' [2018.11.20-05.53.30:822][ 0]LogLinker:Warning: 无法在加载H:/deepdrive-sim-master/deepdrive-sim-master/Content/TuningCars/Maps/Demonstration.umap时寻找到资源'/Game/TuningCars/Maps/Demonstration_BuiltData'的文件。 [2018.11.20-05.53.30:822][ 0]LoadErrors:Error: 错误 /Game/TuningCars/Maps/Demonstration : 无法寻找到资源的文件。 /Game/TuningCars/Maps/Demonstration_BuiltData [2018.11.20-05.53.30:823][ 0]LogLinker:Warning: 无法寻找到文件'/Game/TuningCars/Maps/Demonstration_BuiltData' [2018.11.20-05.53.30:823][ 0]LogLinker:Warning: 无法在加载NULL时寻找到资源'/Game/TuningCars/Maps/Demonstration_BuiltData'的文件。 [2018.11.20-05.53.30:823][ 0]LogLinker:Warning: 无法寻找到文件'/Game/TuningCars/Maps/Demonstration_BuiltData' [2018.11.20-05.53.30:823][ 0]LogLinker:Warning: 无法在加载NULL时寻找到资源'/Game/TuningCars/Maps/Demonstration_BuiltData'的文件。 [2018.11.20-05.53.30:930][ 0]LogLinker:Warning: 无法寻找到文件'/Game/TuningCars/Maps/Demonstration_BuiltData' [2018.11.20-05.53.30:930][ 0]LoadErrors: 信息 加载失败 /Game/TuningCars/Maps/Demonstration_BuiltData.Demonstration_BuiltData 引用者 PersistentLevel [2018.11.20-05.53.30:930][ 0]LogLinker:Warning: 无法在加载NULL时寻找到资源'/Game/TuningCars/Maps/Demonstration_BuiltData'的文件。 [2018.11.20-05.53.30:930][ 0]LoadErrors: 信息 加载失败 /Game/TuningCars/Maps/Demonstration_BuiltData.Demonstration_BuiltData 引用者 PersistentLevel

[micmarty]

Ubuntu 16.04
Unreal Engine 4.14.0.7 with Substance (from README.md)
DeepDrive 2.0 (branch master)
commit: a44b0aab45a7518cc54d606c2f0a339d0abdd206

I have similar errors, but somehow I managed to open and edit the project + build shipping binary without any problems :1st_place_medal: (to be honest it took me 2 weeks of struggle - DeepDrive seem to be very sensitive about using different system/software versions than expected)

How to resolve that missing asset error (or can we just ignore it)?

I know you're working on DeepDrive 2.1, so maybe that's not relevant anymore. BTW Awesome work, can't wait for 2.1 (unable to build it by myself, yet)

[crizCraig]

Hi @micmarty, @ybxbupt - yes you should be able to ignore this. Glad you got it working. Please let us know anything we can do to make the process easier. Unreal on Linux seemed to get much better from 4.14 to 4.18, so maybe some of the problems you encountered with 4.14 will be gone once we release Deepdrive 2.1 which is on Unreal 4.18.

[micmarty]

DeepDrive 2.0 - master branch

Building Unreal 4.14.3 from official sources, then adding Substance (official forum) and rebuilding everything did not work for me (but it should, theoretically). I had to build the code from your link in README.md (git@github.com:Allegorithmic/UnrealEngine --branch 4.14.0.17)

DeepDrive 2.1 - deepdrive_sim branch

For the next couple of weeks I'll dig down deeper into your codebase in order to get more comfortable with both repos.

As of now I noticed two weird hacks:

1. Non-obvious thing is that the project must be a git repository (unpacked zip from github won't work) - requires executing git status

2. Path to python binary is stored inside ~/.deepdrive/python_bin text file. When someone wants to have multiple versions of DeepDrive (quite unusual) he must be very careful while reading logs (like me) and find out that he must edit this file.

My error

1. Opening the project for the first time (UE 4.18 + Substance from README.md): There's an error which is very mysterious... (no clue what's wrong)

(click to fullscreen) BTW If anyone knows the solution for this problem, I'll be grateful :)

Alternative view:

@crizCraig Could you describe your current development environment for working on deepdrive_sim/deepdrive_sim and deepdrive/bootstrap branches? IMO Getting DeepDrive up and running is not as seamless as AirSim or Carla (+ they have quite awesome docs), but they don't have a few thing that DD has out-of-the-box :medal_sports:

P.S.

I love the direction DD is heading :heart:

[crizCraig]

Thanks @micmarty. For Deepdrive 2.0, the recommended way is cloning Allegorithmic's repo as you mentioned. Fortunately in 2.1 we no longer need this as the newer versions of Unreal we are using (4.18 now but 4.20 or 4.21 by release) work much better in Linux!

re: 1. Can you please provide a stack trace? I've removed the git dependency in build.py as well as in in get_package_version.py - unless you call build.py with --type linux_bdist or --type win_bdist which is solely for publishing to PyPi from the CI servers and no one should be calling this directly.

re: 2. ~/.deepdrive/python_bin is managed automatically by the deepdrive project. i.e. it gets set to the python you run main.py with. I've added some instructions for setting it up manually so that others won't run into the same issue you did.

Regarding the error with not finding the specified file. It looks like the Unreal build script is not finding the your python bin in /home/miczi/miniconda3/envs/ddrive-4.18/bin/python. What is the output of

ls -la /home/miczi/miniconda3/envs/ddrive-4.18/bin/python

Doing ls -la on my python_bin resolves to

lrwxrwxrwx 1 b b 10 Jul  1 14:31 /home/b/.local/share/virtualenvs/tf-1.7.1-py3-StrHcfk-/bin/python -> python3.5m*

So symbolic links seem to be fine, but it might be worth trying the full binary path (not a symbolic link).

Sorry for the setup issues. v2.1 is definitely beta still, so I very much appreciate your feedback here!

Thanks for the :heart: We are excited as well!