- Reorder instructions to mention ARM64 builds first in macOS,
as this is the primary architecture in use now (with all new Macs
since 2023 being sold with Apple Silicon only). The `lipo` command still
works as before, as it infers the architecture from the input files.
- Remove the manual bundle generation steps to make the page shorter
(similar to Compiling for Android).
- Remove references to the master branch (this was only relevant when
4.0 was still in development).
Revised JetBrains Rider setup steps and clarified debug configurations. Replaced outdated .webp images with new .png files for newer and clearer screenshots.
Add a note clarifying that this documentation is intended for contributing to the game engine, not for using JetBrains Rider as a C# or GDScript editor. Include reference to the C# guide for configuring an external editor.
Fixed duplicate link based on the Sphinx format. This should fix the warning/error on the page.
---------
Co-authored-by: Max Hilbrunner <mhilbrunner@users.noreply.github.com>
* Added notes on bit depth for ints and floats
Added a small note about the bit depth of integers and floats in Godot's shading language as it is not explicitly stated anywhere.
The bit depth of integer and floats in GDscript and Godot's shading language are different, which can cause problems with lost precision in calculations when integers are set from GDscript as floats/ints in GDscript are 64 bits instead of 32 bits (the standard in GLSL ES 3.0).
While most are unlikely to run into problems due to this difference in bit depth, it can cause mathematical errors in edge cases. As stated by previous contributors, no error will be thrown if types do not match while setting a shader uniform. This includes GDscript floats being set as Godot shader floats (which may not be intuitive).
* Fix incorrect notice about XDG paths working on all platforms in Data paths
They are only effective on Linux/*BSD. (For reference, in most other apps,
it's rare for XDG environment variables to have an effect on other platforms.)
---------
Co-authored-by: Max Hilbrunner <mhilbrunner@users.noreply.github.com>
The space in "some times" is a mistake and should be removed as it should be one word, not two (as can be seen when it is used correctly further down the page at the start of the, "Running one-off scripts using EditorScript" section).
The phrase, "This useful for smoothing camera movement..." appears to be missing a word. It should be, "This is useful for smoothing camera movement..." instead.
