-
Notifications
You must be signed in to change notification settings - Fork 25
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
Error at startup #16
Comments
That error message is probably coming from the static mesh generator. It probably means that you are trying to read in a mesh in "manual" mode, but haven't actually generated the mesh yet. The doc you want is this one. Most likely, you will need to change from "manual" to "VHACD" mesh generation somewhere in your URDF file. |
I'm using the example URDF: LunabotFromMesh.xml. I'm not sure where I should change this. Can you explain shortly how to set up the lunabot example correctly. I copied the generated Plugin folder from UrdfSim in my unreal project folder. Pasted the content from settings-lunabot.json in the settings.json file. Changed the paths in the settings.json file to the location of the LunabotFromMesh.xml. Furthermore, I changed the paths from LunabotFromMesh.xml to the location of the STL files. I tested it with Visual Studio 2017. Switchted the Game Mode to AirSimGameMode. My uproject file looks like that: { Is there something wrong or missing? any tip will be appreciated, thank you |
Can you show your full LunabotMesh? It's likely that the problem is there. |
I have the same error. Do you have any solution for this? |
Hi,
I try to set up your plugin. I got this error when I run the unreal simulation:
Error at startup: Unable to open file F:/vhacd/header.txt.
I haven't found the folder vhacd. I have only found this one: C:\Users\Administrator\UrdfSim\Examples\UrdfBot\LunabotParts\vhacd_bucket\header.txt.
I have changed the paths in settings-lunabot.json file and LunabotFromMesh.xml. Should I change paths somewhere else?
best, Michael
The text was updated successfully, but these errors were encountered: