The code example demonstrating the usage of the "or_greater" and "or_less" hints for the export_range annotation does not declare a variable after the annotation, which is inconsistent with the previous three code examples in the section.
Also, giving the export_range a step of 1 does not create a slider for the property in the editor, like the text suggests, but it instead creates a spin box. The step should be changed to a float so the property can appear as a slider.
Converts all headers in tutorials\3d\particles\index.rst to fake rubric headers.
Note that in this case we can't have any real subheaders on the page due to
the order of the sections.
Adds a warning note to shading_language.rst. GDShader does not
initialize local variables to 0, and an uninitialized local variable can
contain an arbitrary value.
* Update physics_introduction.rst
The docs page for raycasting provides a link to the physics introduction page for how to set a collision mask on a raycast created in code. The physics introduction page does not mention export annotations for exporting a collision mask. This pull request adds a brief bit about exporting layer masks, and links to the export annotation docs.
---------
Co-authored-by: tetrapod <145553014+tetrapod00@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).
