You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to visualize different robots outside of the default in Lively Studio? I had tried using a new URDF that was referencing STLs to no success. Would it require converting the files to DAE format? Since Lively uses RelaxedIK would I also need to do any additional configuration on that end to get another robot to work with it? Thanks.
The text was updated successfully, but these errors were encountered:
Sorry for the delay. Yeah, the software currently doesn't allow us to import arbitrary STL or DAE files for visualization purposes from the front-end. Adding new meshes requires updating the source code of LivelyStudio itself. In short, you can find a file here:
This imports all the meshes we have on file, and makes them available in the MeshLookupTable. That lookup would use whatever mesh path is specified in the URDF (e.g. "package://nao_meshes/meshes/V40/RFinger11.dae"), and return up the corresponding parsed mesh file. The caveat here is that we actually have to write loaders for each of them, which you can find in that folder. So you should find both a .glb file and a .js file, e.g.
Right now we parse those files, and return a specific data structure so we know how to render those in the scene, but it is heavily based on the code generated here. Right now we have converted all the files to .glb format for consistency, but presumably as long as you got the data format correct, it should be able to read it. Happy to discuss with you if you have any specifics. Also, let me know of you have any questions!
Is it possible to visualize different robots outside of the default in Lively Studio? I had tried using a new URDF that was referencing STLs to no success. Would it require converting the files to DAE format? Since Lively uses RelaxedIK would I also need to do any additional configuration on that end to get another robot to work with it? Thanks.
The text was updated successfully, but these errors were encountered: