Adds documentation for NavigationServer with focus on topics not explained in the class documentation.
Adds documentation for NavigationAgent node use and caveats.
Adds documentation for RVO agent avoidance.
Adds documentation how to create navigationmesh / navpolygons for 2D and 3D both with editor tools as well with scripts + some technical background stuff.
- Add more FFmpeg tips such as `-preset veryslow`.
- Fix `-r` usage in FFmpeg commands.
- Remove leftover `-preset veryfast` (it wasn't meant to be here).
* [Instancing with signals] Updated to 4.0
Basically started with changing `instance()` to `instantiate()`
Was a good chance to also upgrade the badly named `b` variables into proper intuitive names.
It's a good tutorial, short and to the point, though kinda abstract so I don't think there is anything more to add (if I put an image above the final codeblock, on how to add a signal via UI, it would ruin the abstraction imo)
* Made the signal location a bit more obvious
* Updated signal emission to 4.0 syntax
Interesting that emit_signal did work, backwards compatibility ftw!
`emit_signal()` its less intuitive as you must know a "magical function" of Godot instead of using the obvious variable, and also takes string argument lmao
* Clearification of what an action actually is.
There was no definition of an action itself. I also simplified the sentence, "An InputEvent may or may not represent a predefined action" to say that actions are not required but useful (combining with the next sentence).
Without the definition, I had thought actions were pre-defined input *conditions* (input states, rather than the input itself, since an action must have it's input defined). That mess of inquiry can be read here: https://www.reddit.com/r/godot/comments/xfvmg8/can_we_define_our_own_inputanalysis_for_inputmap/ Skip to first part of my last post to see the wording that corrected my understanding of what actions were.
This is my first-ever proposal. Thank you for the opportunity to contribute to the docs and help everyone understand things a little easier.
-- Kevin
It is impossible to instantiate a Light2D node, and a DirectionalLight2D node has no texture (so this tutorial doesn't work with it at all)
Feel free to deny this commit, because I am a newbie and don't know if it was possible to instantiate a Light2D node in 3.x either (if it was possible, the tutorial should stay as is, and this pull request should be closed)
get_editor_interface().get_editor_main_control() no longer exists. `get_editor_main_control()` has been replaced with `get_editor_main_screen()`.
I changed all the occurrences in code, as well as adapted the text describing this accordingly.
- Add section on input lag, containing project and hardware/OS
configuration recommendations.
- Remove outdated advice about graphics drivers on Linux.
- Mention that compositing can sometimes be disabled on Linux for
better performance.
- Wrap to 80 characters.
- Describe Label3D and TextMesh in more detail.
- Add a section on projected Control node, which is a worthwhile
alternative in many cases.
- Add a summary that gives some recommendations on which method to use.
