-
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
Did not detect 3 elements #13
Comments
The error means what it says, that it tried to parse a 3-vector from your config file, but couldn't for some reason. 99% of the time, this means that there's a typo somewhere (e.g. separating them by comma instead of space). Here are the two spots it can be thrown from: If you can share the UrdfFile, I can take a look. |
I have modified my URDF and no longer get that error. However, when I try to add at least 1 roller to the wheel, I get an exception:
My URDF looks like this (only base_link, 4 wheels and 1 roller):
|
I actually spotted the problem, it was because I did not define the "limit" for the roller joint. I also want to ask whether there is an option to view the URDF first before pressing Play on UE4? Because with so many rollers, I cannot view properly how everything looks like and whenever I tick "Use controlRotation" everything collapses |
Hi, I am still actively looking into this issue. I have uploaded my URDF (with Mesh included) and settings.json files. If you do not mind, can you try them? My STL has origin in the middle of my wheel but when I include that in URDF it does not seem to be centered. Here is my AirSim folder (the one in Documents folder): |
I have updated my folder: Now I am able to get all 4 wheels in a correct position but having troubles with the rollers... |
To answer your first question: your best bet on viewing it before importing it into UE4 is to use something like rvis. There isn't a great way to "preview" it via UrdfSim. I'm not going to have much time this weekend, but may have a few hours during the week next week if you are still having trouble. If you are having issues with orientation, enabling debug mode may help you see the coordinate transformations. |
I have noticed that the angles in URDF are different than in ROS. All angles go positive clockwise while in ROS it is anticlockwise and the Y direction is opposite to ROS. Can you point where can I change that in the code? I remember seeing this but can't remember where exactly |
Probably UrdfBotPawn.cpp |
urdfxml.docx |
Btw how could you fix your issue? |
So, if it works for the other four wheels, and not for the roller, I'm betting the problem is with the stl ascii file. STL importing is always a bit rough. The issue is that the engine has to dynamically compute the collision bounds, which can be a bit dicey, especially if the mesh isn't convex. There are a few things you can try:
If you can get a better stack trace, then it would be easier to debug further. |
I don't know if I was clear about the problem. My problem is that I get "did not detect 3 elements" error. I am sorry if I was not clear. Thanks |
Try swapping "rpy" and "xyz" in the tag of the link. There was a report earlier that this caused a crash for some reason. If UE4 doesn't support STL, try importing to blender and exporting in .fbx. That should definitely work. |
I transformed my .stl files to .fbx and dragged into unreal. Now, I use them as unreal mesh type. However, I still get the same error although I also decimated the meshes. How can I track the error and find out what actually causes this problem? The final xml code is appended. |
If you're running from within visual studio, you should get a stack trace in the output when it fails. That should point to where the problem is. If you're trying to use precompiled binaries, try building from source and including it in a project. |
try to add rpy="0 0 0" to the axis at the joint section |
Hi,
When I tried to import my URDF, I get an error when starting UE:
Error at startup: Error parsing 3-d vector from string , did not detect 3 elements.
Do you have any idea what that could be?
Debug message:
The text was updated successfully, but these errors were encountered: