stan220/godot-docs
1
0
Fork 0
mirror of https://github.com/stan220/godot-docs.git synced 2026-09-08 18:29:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Various grammar and spelling fixes

Browse Source
This commit is contained in:
A Thousand Ships
2025-06-23 16:37:26 +02:00
parent b2de954be7
commit 92cd36b50e
49 changed files with 84 additions and 84 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tutorials/physics/interpolation/2d_and_3d_physics_interpolation.rst
+1 -1
View File
@@ -34,7 +34,7 @@ This has some implications:
Controlling the on / off behavior of 2D nodes therefore requires a little more
thought and planning.
- On the positive side, pivot behavior in the scene tree is perfectly preserved
during interpolation in 2D, which gives super smooth behaviour.
during interpolation in 2D, which gives super smooth behavior.
Resetting physics interpolation
-------------------------------
tutorials/physics/interpolation/physics_interpolation_introduction.rst
+2 -2
View File
@@ -60,7 +60,7 @@ Adapt the tick rate?
~~~~~~~~~~~~~~~~~~~~
Instead of designing the game at a fixed physics tick rate, we could allow the tick
rate to scale according to the end users hardware. We could for example use a fixed
rate to scale according to the end user's hardware. We could for example use a fixed
tick rate that works for that hardware, or even vary the duration of each physics
tick to match a particular frame duration.
@@ -70,7 +70,7 @@ run in the ``_physics_process``) work best and most consistently when run at a
that has been designed for 60 TPS (ticks per second) at e.g. 10 TPS, the physics
will behave completely differently. Controls may be less responsive, collisions /
trajectories can be completely different. You may test your game thoroughly at 60
TPS, then find it breaks on end users machines when it runs at a different tick
TPS, then find it breaks on end users' machines when it runs at a different tick
rate.
This can make quality assurance difficult with hard to reproduce bugs, especially
tutorials/physics/using_jolt_physics.rst
+1 -1
View File
@@ -8,7 +8,7 @@ Introduction
The Jolt physics engine was added as an alternative to the existing Godot Physics
physics engine in 4.4. Jolt is developed by Jorrit Rouwe with a focus on games and
VR applications. Previously it was available as a extension but is now built into
VR applications. Previously it was available as an extension but is now built into
Godot.
It is important to note that the built-in Jolt Physics module is considered