Grégoire Passault

I noticed the same issue. Using high FOV result in a lot of extra floater gaussians to appear

Quite straightforward to reproduce: https://github.com/user-attachments/assets/9b97f808-9b0c-4ecd-b372-82dbf181f70f In my use case, I would be interested in high FOV to produce distorted images (radial, tangentiels) afterhand

Hello, I believe this is currently not possible. Maybe a syntax similar to `ignore` could be used: https://onshape-to-robot.readthedocs.io/en/latest/config.html#ignore-default However, I'm not sure whether the matching should be done by part...

Hello, I am not sure of the values that should be used, I am checking with Onshape team They give numbers expressed in requests/year (?) here: https://onshape-public.github.io/docs/auth/limits/ In your experience,...

I am still waiting for more feedbacks from OnShape team about this

Hello, Using variables for joint limits should actually work. I just fixed an issue about the way case was handled in variable names that could have causes such issue. Can...

Hello and thanks for this proposition I have another suggestion about that, maybe the path to `config.json` should be included in the `.part` file that is generated with metadata next...

Currently, `assets_directory` allow for assets to be located elsewhere than a subdirectory from where `config.json` is. However, I think it is acceptable to assume that it will, in general, actually...

Hello, I am discussing rate limits actively with Onshape team, with the hope to find a good tradeoff so that it doesn't become a big issue with tools like onshape-to-robot...