You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: automated_updates_data.json
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -80,6 +80,10 @@
80
80
{
81
81
"date": "2026-03-15",
82
82
"summary": "Improved string-instructions (added StrReplaceOne/StrReplaceAll), common-conversions (added LargeNumberToString, ToJSON/ObjectVarToJSON), timers (added TimeScale and Time() format selectors), and gamepad docs (added analog triggers, deadzone, StickForceX/Y, controller type detection)"
83
+
},
84
+
{
85
+
"date": "2026-03-24",
86
+
"summary": "Fixed device-sensors docs (typo in gamma rotation description, wrong units deg/s vs m/s² for rotation values, clarified Is Absolute expression, added gravity note to acceleration) and fixed broken wiki URL in advanced-conditions OR condition"
Copy file name to clipboardExpand all lines: docs/gdevelop5/all-features/advanced-conditions/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ If the "**OR**" condition is used in an event, the actions are performed when on
19
19
20
20
!!! warning
21
21
22
-
The OR condition has a special behavior regarding the [object filtering logic of GDevelop](http://wiki.compilgames.net/doku.php/gdevelop5/tutorials/basic-game-making-concepts#events_and_how_objects_are_selected_by_these_events). The objects listed under it are _unselected_ by GDevelop if their condition is not met, so actions specific to these objects may not work. In some cases, using "Pick all instances" on the action side will fix things. In other cases, replacing the OR will be necessary.
22
+
The OR condition has a special behavior regarding the [object filtering logic of GDevelop](/gdevelop5/events/object-picking). The objects listed under it are _unselected_ by GDevelop if their condition is not met, so actions specific to these objects may not work. In some cases, using "Pick all instances" on the action side will fix things. In other cases, replacing the OR will be necessary.
Copy file name to clipboardExpand all lines: docs/gdevelop5/all-features/device-sensors/index.md
+15-11Lines changed: 15 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,24 +67,28 @@ This action deactivates the orientation sensor so that it stops delivering alpha
67
67
68
68
**Is Absolute**
69
69
70
-
This value indicates that the orientation data is in absolute values. In reference to the Earth's coordinates (value 1) or using an arbitrary frame, is determined by the device (value 0).
70
+
Returns 1 if the orientation data is referenced to the Earth's coordinate frame (compass-based), or 0 if it uses an arbitrary framedetermined by the device.
71
71
72
72
**Alpha Value**
73
73
74
-
The "alpha" rotation.
74
+
The "alpha" rotation angle, in degrees (range: 0 to 360).
75
75
76
76
**Beta Value**
77
77
78
-
The "beta" rotation.
78
+
The "beta" rotation angle, in degrees (range: -180 to 180).
79
79
80
80
**Gamma Value**
81
81
82
-
The "gamma" rotation.
82
+
The "gamma" rotation angle, in degrees (range: -90 to 90).
83
83
84
84
## Motion sensor
85
85
86
86
In contrast to the orientation sensor which returns absolute values, the motion sensor delivers relative ones. This sensor only returns values while the device is moving. If you hold it still, no matter its orientation, the sensor will return 0. You can access the motion data along an axis via the "x", "y", "z" values and the rotation data around an axis via "alpha", "beta" and "gamma" which are explained in the next section.
87
87
88
+
!!! note
89
+
90
+
The acceleration values include the effect of gravity (approximately 9.81 m/s² on Earth), so a device lying flat on a table will still show a non-zero Z acceleration.
91
+
88
92
!!! note
89
93
90
94
The motion sensor rotation values (alpha, beta, gamma) are currently badly supported on mobile devices. It would currently be better to calculate the value from the orientation data
@@ -125,7 +129,7 @@ This value shows the acceleration around the x-axis. If you hold your device in
125
129
126
130

127
131
128
-
This value shows the acceleration around the y-axis. If you hold your device in portrait mode with a hand on each side, you can turn your device around the y-axis and the beta value will increase.
132
+
This value shows the acceleration around the y-axis. If you hold your device in portrait mode with a hand on each side, you can turn your device around the y-axis and the gamma value will increase.
129
133
130
134
### Conditions
131
135
@@ -147,15 +151,15 @@ This condition lets you compare the value of z-acceleration to a number or varia
147
151
148
152
**Motion Alpha**
149
153
150
-
This condition lets you compare the value of alpha to a number or variable. (m/s²)
154
+
This condition lets you compare the value of alpha to a number or variable. (deg/s)
151
155
152
156
**Motion Beta**
153
157
154
-
This condition lets you compare the value of beta to a number or variable. (m/s²)
158
+
This condition lets you compare the value of beta to a number or variable. (deg/s)
155
159
156
160
**Motion Gamma**
157
161
158
-
This condition lets you compare the value of gamma to a number or variable. (m/s²)
162
+
This condition lets you compare the value of gamma to a number or variable. (deg/s)
159
163
160
164
### Actions
161
165
@@ -183,14 +187,14 @@ The "z" acceleration. (m/s²)
0 commit comments