Tutorials and Walkthrough

[JacopoPan]

I tried tor write a couple of extremely simple, self-contained (Linux/Ubuntu) tutorials on

• Using AirSim's Python APIs with pre-compiled envs / Compiling UE4 and AirSim to use the C++ APIs and ROS nodes
• Modifying and recompiling AirSim's Unreal plugin when using custom UE4 projects and meshes

If anyone wants to check them out/correct me on anything I did wrong

I was motivated in part by the fact that I found the documentation on https://microsoft.github.io/AirSim/ to be a bit scattered but, more importantly, some of it is as old as 5 years, while some was updated as recently last month: is there any plan to re-factor/simplify/make current the existing body of documentation?

[jonyMarino]

@JacopoPan excellent initiative! We are very interested in these types of contributions. I will be looking at it and coming back to you soon.

[JacopoPan]

@jonyMarino I was happy to see this had positive feedback: if you think there are certain parts I should/could polish and make into a PR, please let me know

[jonyMarino]

@JacopoPan It seems to us that this documentation corresponds to different sections of the current documentation. We will see it well and return to you

[JacopoPan]

@jonyMarino yes, of course: there are some additional terminal snippets, information I learned from open and closed Issues, and the custom pawn instructions and RLlib integration are new) but, as I wrote in the first message, one of the (I believe) limits of the existing documentation is how scattered across pages it currently is (and that's something I think it would be useful for the community to address)

[jonyMarino]

@JacopoPan Sorry for the delays in incorporating your contribution. We are making efforts so that the contributions of the community are incorporated more quickly. Could you make a pull request for this and we continue there? It will get more attention if you do that

[stale]

This issue has been automatically marked as stale because it has not had activity from the community in the last year. It will be closed if no further activity occurs within 20 days.