Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
doc:faq [2013/12/04 14:26] – admin | doc:faq [2022/02/17 13:38] (current) – First FAQ entry yay. gkazhoya | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== FAQ ====== | ====== FAQ ====== | ||
+ | **Q: How can I add a mesh in bullet having the full mesh path and not using the mesh folder?** | ||
+ | |||
+ | A: The mesh paths are stored here: https:// | ||
+ | |||
+ | To add new entries into the variable you use this function: https:// | ||
+ | |||
+ | Here is an example. These are two meshes that we use for the shopping scenario: https:// | ||
+ | |||
+ | In order to register them, we call the add-objects-to-mesh-list function in the init-projection function, which is called upon ROS node startup: https:// | ||
+ | |||
+ | To register any function as a callback upon node startup we use this macro https:// | ||
+ | |||
+ | Once you have the paths stored in the btr:: | ||
+ | |||
+ | You can, of course, just populate the mesh variable manually to hack something quickly, but I'd suggest using the add-objects-to-mesh list function. | ||
+ | |||
+ | Important: the meshes should be located in a ROS package that the system is able to find with '' | ||
+ | |||
+ | ------------------ |