- 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.
Previously, it displayed as "Introduction" under the 3D tab, making it incredibly unclear what the page was actually about. If I understand ReadTheDocs generation of the menu correctly, this will give it a much clearer and more descriptive name of "3D text" in the navigation menu.
I based my exact title on the format of the "3D lights and shadows" documentation title, figuring it was the closest in content type to what is included in the 3D Text documentation.
Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
When a user is seeing transform.basis for the first time, it's
very important to label all the inputs. People reading this are
being presented with several values at once and must understand
all of them to understand what is happening in the example. The
reader is likely unfamiliar with what `transform.basis` actually
does. They are also given a Vector3 without explanation that it
is the axis, they are given PI without explanation that that is
the amount of rotation, they are multiplying by the value of the
transform.basis again hinging on them understanding what that is.
Finally, they are creating a Basis object and it's not made clear
that the two values this receives are actually an axis and an
amount.
Rotating by PI makes the rotation direction very unclear.
I'm introducing the changes above to hopefully rectify a lot of
these issues and make things easier for the next person.
Thanks to Aaron Franke for:
- Adds types to the C# code
- Fixes a misnamed variable
- Clearing up some of the code comments
- Changes vectors so they are consistent with the GDScript examples
- fixing float values so they are correct and consistent
Co-authored-by: Aaron Franke <arnfranke@yahoo.com>
This PR gives a little more details on how ARRAY_BONES and ARRAY_WEIGHTS are used on an ArrayMesh. This is based on @pycbouh 's explanation in #5434, and fixes that issue.
- Mention new behavior of the CPU lightmapper, such as lights with the
All bake mode not affecting baked objects anymore.
- List common usage scenarios for bake modes (Disabled, Indirect, All).
- Add a section on balancing bake times with quality.
- Update list of properties to match the new CPU lightmapper.
- Remove references to cone tracing since this is no longer available
in the new CPU lightmapper.
