-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to build archive, exception follows: #1460
Comments
Any idea if Linux needs something for FBX converter? @kamkolak |
thanks for the images. It seems you have a few extra modules. On linux you only need windows support, not UWP and I'm not sure what the center one is, webGL? As for the folder, can you show the output folder with the bundles. When it fails it lists the files and we can tell sometimes from the leftover files. I want to see if it is saving the gltf but naming it something wrong. |
Here are modules that I've installed, didn't have Linux build support (mono) Here is the player.log After the build completed, there is only one file in the AssetBundles/Vehicles, and that file's size is 0kb, so I couldn't upload it to webUI As one of the error that I've captured above said, the .glb file was missing. |
@EricBoiseLGSVL Autodesk FBX package requires some shared objects to be present, but I think they should be included with default Ubuntu 18.04 installation. Here's the list:
@duongtran11 the player log you attached does not contain any of the exceptions or errors you listed. Are you sure it was the same session? Also, since I can see you're running this in editor - you should probably look into editor log instead. |
@kamkolak-lge thanks for the reply! Are you saying I need to install all those libraries? |
@duongtran11 The most likely reason for this issue is FBX converter failing to launch. Please check if you have all the dependencies available on your system, and add any that are missing. |
@kamkolak-lge Or maybe because I don't have Simulator.Vehicles.asmdef file in External/Vehicles? |
@duongtran11 Assembly definition file should not be a problem, unless you're including some custom code in your vehicle bundle. Since you were able to build on newer version, you have all required dependencies on your system. Looking at all the new information, I think the most likely cause for the problem is race condition. If it's possible and won't cause compilation issues, please try cherry-picking commit After the line 262:
try adding:
Please let me know if this solved your issue. |
The reason why I have to build vehicles in 2021.1.1 is because my environment is in com.svlsimulator.2 version and the vehicles built by newer simulator versions are in com.svlsimultor.5 version. So it got a version mismatch when I ran simulation. |
So the issue is with the glb library on your machine so you have to build assets with the latest version, right? |
@EricBoiseLGSVL well, I made an environment on 2021.1.1 first, then proceeded to build a vehicle, then got the error. I tried to switch to newer version of simulator but got other problems with version mismatch. |
Sorry, about these issues with the release. |
I'm getting the same error as #1566 |
The issue is being fixed now, it only effects users that are building binaries locally. Sorry for the confusion. |
I've successfully build the vehicle, thank you! |
@EricBoiseLGSVL What is the fix for this? I'm seeing the exact same problem trying to build a vehicle (Jaguar, unmodified from github) on Windows with 2021.2:
|
We are looking into this. Looks like our fix couldn't go to linux so it was rolled back. We will follow up. |
I got errors when building a custom ego vehicle

I got the same errors when building a JaguarXE2015 downloaded from github

What could be the problem?
The text was updated successfully, but these errors were encountered: