Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Rebel Engine API MIT 11% 9,947 223,065 1,516,953 9,337 72 0 0
Glossary Rebel Toolbox MIT 0 0 0 0 0 0 0

Overview

Project website rebeltoolbox.com
Project maintainers User avatar Rebel
Translation license MIT Rebel Engine API Rebel Toolbox
3 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 11,271 236,674 1,606,266
Translated 11% 1,324 5% 13,609 5% 89,313
Needs editing 5% 610 3% 8,369 4% 65,103
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 72 1% 3,062 1% 21,990
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 82% 9,337 90% 214,696 90% 1,451,850
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 11,274 changes 0 changes 28 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

0
Hosted words
0
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+11%
—
Contributors
+100%
User avatar None

Resource updated

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
The “translations/de.po” file was changed. 2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
WebXR is an open standard that allows creating VR and AR applications that run in the web browser.
As such, this interface is only available when running in an HTML5 export.
WebXR supports a wide range of devices, from the very capable (like Valve Index, HTC Vive, Oculus Rift and Quest) down to the much less capable (like Google Cardboard, Oculus Go, GearVR, or plain smartphones).
Since WebXR is based on Javascript, it makes extensive use of callbacks, which means that [WebXRInterface] is forced to use signals, where other AR/VR interfaces would instead use functions that return a result immediately. This makes [WebXRInterface] quite a bit more complicated to initialize than other AR/VR interfaces.
Here's the minimum code required to start an immersive VR session:
[codeblock]
extends Spatial

var webxr_interface
var vr_supported = false

func _ready():
# We assume this node has a button as a child.
# This button is for the user to consent to entering immersive VR mode.
$Button.connect("pressed", self, "_on_Button_pressed")

webxr_interface = ARVRServer.find_interface("WebXR")
if webxr_interface:
# WebXR uses a lot of asynchronous callbacks, so we connect to various
# signals in order to receive them.
webxr_interface.connect("session_supported", self, "_webxr_session_supported")
webxr_interface.connect("session_started", self, "_webxr_session_started")
webxr_interface.connect("session_ended", self, "_webxr_session_ended")
webxr_interface.connect("session_failed", self, "_webxr_session_failed")

# This returns immediately - our _webxr_session_supported() method
# (which we connected to the "session_supported" signal above) will
# be called sometime later to let us know if it's supported or not.
webxr_interface.is_session_supported("immersive-vr")

func _webxr_session_supported(session_mode, supported):
if session_mode == 'immersive-vr':
vr_supported = supported

func _on_Button_pressed():
if not vr_supported:
OS.alert("Your browser doesn't support VR")
return

# We want an immersive VR session, as opposed to AR ('immersive-ar') or a
# simple 3DoF viewer ('viewer').
webxr_interface.session_mode = 'immersive-vr'
# 'bounded-floor' is room scale, 'local-floor' is a standing or sitting
# experience (it puts you 1.6m above the ground if you have 3DoF headset),
# whereas as 'local' puts you down at the ARVROrigin.
# This list means it'll first try to request 'bounded-floor', then
# fallback on 'local-floor' and ultimately 'local', if nothing else is
# supported.
webxr_interface.requested_reference_space_types = 'bounded-floor, local-floor, local'
# In order to use 'local-floor' or 'bounded-floor' we must also
# mark the features as required or optional.
webxr_interface.required_features = 'local-floor'
webxr_interface.optional_features = 'bounded-floor'

# This will return false if we're unable to even request the session,
# however, it can still fail asynchronously later in the process, so we
# only know if it's really succeeded or failed when our
# _webxr_session_started() or _webxr_session_failed() methods are called.
if not webxr_interface.initialize():
OS.alert("Failed to initialize")
return

func _webxr_session_started():
$Button.visible = false
# This tells Rebel Engine to start rendering to the headset.
get_viewport().arvr = true
# This will be the reference space type you ultimately got, out of the
# types that you requested above. This is useful if you want the game to
# work a little differently in 'bounded-floor' versus 'local-floor'.
print ("Reference space type: " + webxr_interface.reference_space_type)

func _webxr_session_ended():
$Button.visible = true
# If the user exits immersive mode, then we tell Rebel Engine to render to the web
# page again.
get_viewport().arvr = false

func _webxr_session_failed(message):
OS.alert("Failed to initialize: " + message)
[/codeblock]
There are several ways to handle "controller" input:
- Using [ARVRController] nodes and their [signal ARVRController.button_pressed] and [signal ARVRController.button_release] signals. This is how controllers are typically handled in AR/VR apps in Rebel Engine, however, this will only work with advanced VR controllers like the Oculus Touch or Index controllers, for example. The buttons codes are defined by [url=https://immersive-web.github.io/webxr-gamepads-module/#xr-standard-gamepad-mapping]Section 3.3 of the WebXR Gamepads Module[/url].
- Using [method Node._unhandled_input] and [InputEventJoypadButton] or [InputEventJoypadMotion]. This works the same as normal joypads, except the [member InputEvent.device] starts at 100, so the left controller is 100 and the right controller is 101, and the button codes are also defined by [url=https://immersive-web.github.io/webxr-gamepads-module/#xr-standard-gamepad-mapping]Section 3.3 of the WebXR Gamepads Module[/url].
- Using the [signal select], [signal squeeze] and related signals. This method will work for both advanced VR controllers, and non-traditional "controllers" like a tap on the screen, a spoken voice command or a button press on the device itself. The [code]controller_id[/code] passed to these signals is the same id as used in [member ARVRController.controller_id].
You can use one or all of these methods to allow your game or app to support a wider or narrower set of devices and input methods, or to allow more advanced interactions with more advanced devices.
 
2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
Returns the angle between the line connecting the two points and the X axis, in radians.
[img caption="Illustration of the returned angle"]/img/vector2_angle_to_point.png[/img]
 
2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
Returns this vector's angle with respect to the positive X axis, or [code](1, 0)[/code] vector, in radians.
For example, [code]Vector2.RIGHT.angle()[/code] will return zero, [code]Vector2.DOWN.angle()[/code] will return [code]PI / 2[/code] (a quarter turn, or 90 degrees), and [code]Vector2(1, -1).angle()[/code] will return [code]-PI / 4[/code] (a negative eighth turn, or -45 degrees).
[img caption="Illustration of the returned angle"]/img/vector2_angle.png[/img]
Equivalent to the result of [method @GDScript.atan2] when called with the vector's [member y] and [member x] as parameters: [code]atan2(y, x)[/code].
 
2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
Tweens are useful for animations requiring a numerical property to be interpolated over a range of values. The name [i]tween[/i] comes from [i]in-betweening[/i], an animation technique where you specify [i]keyframes[/i] and the computer interpolates the frames that appear between them.
[Tween] is more suited than [AnimationPlayer] for animations where you don't know the final values in advance. For example, interpolating a dynamically-chosen camera zoom value is best done with a [Tween] node; it would be difficult to do the same thing with an [AnimationPlayer] node.
Here is a brief usage example that makes a 2D node move smoothly between two positions:
[codeblock]
var tween = get_node("Tween")
tween.interpolate_property($Node2D, "position",
Vector2(0, 0), Vector2(100, 100), 1,
Tween.TRANS_LINEAR, Tween.EASE_IN_OUT)
tween.start()
[/codeblock]
Many methods require a property name, such as [code]"position"[/code] above. You can find the correct property name by hovering over the property in the Inspector. You can also provide the components of a property directly by using [code]"property:component"[/code] (e.g. [code]position:x[/code]), where it would only apply to that particular component.
Many of the methods accept [code]trans_type[/code] and [code]ease_type[/code]. The first accepts an [enum TransitionType] constant, and refers to the way the timing of the animation is handled (see [url=https://easings.net/]easings.net[/url] for some examples). The second accepts an [enum EaseType] constant, and controls where the [code]trans_type[/code] is applied to the interpolation (in the beginning, the end, or both). If you don't know which transition and easing to pick, you can try different [enum TransitionType] constants with [constant EASE_IN_OUT], and use the one that looks best.
[img caption="Tween easing and transition types cheatsheet"]/img/tween_cheatsheet.png[/img]
[b]Note:[/b] Tween methods will return [code]false[/code] if the requested operation cannot be completed.
Tweens sind nützlich für Animationen, bei denen eine numerische Eigenschaft über einen Bereich von Werten interpoliert werden muss. Der Name [i]tween[/i] kommt von [i]in-betweening[/i], einer Animationstechnik, bei der Sie [i]Keyframes[/i] angeben und der Computer die Frames interpoliert, die dazwischen erscheinen.
[Tween] eignet sich besser als [AnimationPlayer] für Animationen, bei denen Sie die Endwerte nicht im Voraus kennen. Das Interpolieren eines dynamisch gewählten Kamerazoomwerts lässt sich z. B. am besten mit einem [Tween]-Knoten durchführen; mit einem [AnimationPlayer]-Knoten wäre es schwierig, dasselbe zu tun.
Hier ist ein kurzes Anwendungsbeispiel, das einen 2D-Knoten dazu bringt, sich fließend zwischen zwei Positionen zu bewegen:
[codeblock]
var tween = get_node("Tween")
tween.interpolate_property($Node2D, "position",
Vector2(0, 0), Vector2(100, 100), 1,
Tween.TRANS_LINEAR, Tween.EASE_IN_OUT)
tween.start()
[/codeblock]
Viele Methoden erfordern einen Eigenschaftsnamen, wie z. B. [code]"position"[/code] oben. Sie können den richtigen Eigenschaftsnamen finden, indem Sie den Mauszeiger über die Eigenschaft im Inspektor bewegen. Sie können auch die Komponenten einer Eigenschaft direkt angeben, indem Sie [code]"property:component"[/code] verwenden (z. B. [code]position:x[/code]), wobei die Eigenschaft nur für diese bestimmte Komponente gelten würde.
Viele der Methoden akzeptieren [code]trans_type[/code] und [code]ease_type[/code]. Die erste akzeptiert eine [enum TransitionType]-Konstante und bezieht sich auf die Art und Weise, wie das Timing der Animation behandelt wird (siehe [url=https://easings.net/]easings.net[/url] für einige Beispiele). Die zweite akzeptiert eine [enum EaseType]-Konstante und steuert, wo der [code]trans_type[/code] auf die Interpolation angewendet wird (am Anfang, am Ende oder beides). Wenn Sie nicht wissen, welchen Übergang und welches Easing Sie wählen sollen, können Sie verschiedene [enum TransitionType]-Konstanten mit der [constant EASE_IN_OUT] ausprobieren und diejenige verwenden, die am besten aussieht.
[url=https://raw.githubusercontent.com/godotengine/godot-docs/master/img/tween_cheatsheet.png]Tween-Easing und Übergangstypen Cheatsheet[/url]
2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
Sets the drawing index of the sub-tile from an atlas/autotile given its coordinates.
 
2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
Sets the priority of the sub-tile from an autotile given its coordinates.
When more than one sub-tile has the same bitmask value, one of them will be picked randomly for drawing. Its priority will define how often it will be picked.
 
2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
Sets the spacing between sub-tiles of the atlas/autotile.
 
2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
Sets the size of the sub-tiles in an atlas/autotile.
 
2 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. German
Sets the navigation polygon of the sub-tile from an atlas/autotile given its coordinates.
 
2 months ago
Browse all changes for this language