Skip to content

Conversation

@Feddockh
Copy link

@Feddockh Feddockh commented Oct 7, 2025

…or orchard generation.

Updated gazebo.py to remove <script> tags (believed to be incompatible with gazebo ignition) and updated sdf with compatible pbr materials. Other minor improvements include clarifying the way files are found for gazebo and corrected sdf tag which error in Gazebo Ignition.

The apple tree asset was made by me with resources from
https://polyhaven.com/a/japanese_sycamore
https://polyhaven.com/a/food_apple_01

Included a script which was used to update the obj and texture jpg for compatibility with this package (as only one texture file per plant is allowed here at the moment).

If there is anything that is incorrect or strange please let me know! I did use genAI for assistance since most of this is out of my area of expertise.

@CyrillePierre
Copy link
Contributor

This PR should be at least 3 differents PR:

  • adapt gazebo to allow exporting for Gazebo Ignition
  • add a script to convert multi object/material into a unique one
  • add an apple tree model

I've tested some of the examples in gazebo classic (with ignition_mode: false) and ignition (with ignition_mode: true) and it seems to work well.

For the script build_texture_atlas.py, it should be placed somewhere other than the apple tree model. Maybe in a scripts directory at the root of the project. But I’m not sure if this script is really specific to CropCraft. It could be a separate project on its own.

Regarding the model of the apple tree, I’d like to avoid adding too many assets. This GitHub project is mainly intended to host the code for the agricultural plot generator. The few assets already included are minimalist models that only serve as examples. Users can create or obtain models from other sources and store them in a dedicated directory (as explained in the documentation). At most, since there’s currently no example for horticulture, we could add the apple tree model, but it needs to be much lighter. Its directory is currently 80 MB. I could accept it if it were under 3 MB.

I will close this PR. You can create new, more specific ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants