Inherited By: AudioServer, CameraServer, ClassDB, DisplayServer, EditorFileSystemDirectory, EditorInterface, EditorPaths, EditorSelection, EditorUndoRedoManager, EditorVCSInterface, Engine, EngineD...

Inherited By: AudioServer, CameraServer, ClassDB, DisplayServer, EditorFileSystemDirectory, EditorInterface, EditorPaths, EditorSelection, EditorUndoRedoManager, EditorVCSInterface, Engine, EngineD...

Inherited By: AudioServer, CameraServer, ClassDB, DisplayServer, EditorFileSystemDirectory, EditorInterface, EditorPaths, EditorSelection, EditorUndoRedoManager, EditorVCSInterface, Engine, EngineD...

Inherited By: AudioServer, CameraServer, ClassDB, DisplayServer, EditorFileSystemDirectory, EditorInterface, EditorPaths, EditorSelection, EditorUndoRedoManager, EditorVCSInterface, Engine, EngineD...

Inherited By: AudioServer, CameraServer, ClassDB, DisplayServer, EditorFileSystemDirectory, EditorInterface, EditorPaths, EditorSelection, EditorUndoRedoManager, EditorVCSInterface, Engine, EngineD...

### Godot Version `4.4` ### Question When I unplugged my headset from my computer, leaving only my PS5 controller speakers as the available output device, I was surprised: the 3D game had perfect feedback on the controller haptics. Unfortunetly i’ve been trying to replicate this result but having the audio go both to the default output device and looking for the output device list in the AudioServer with controller in the name, i can find the speaker but i discovered that i cannot set the audio to play at 2 output devices at once. Then I looked at the documentation for the joystick, and I saw that I can send a vibration request to the controller, but it is a general vibration that does not use the controller’s haptic capabilities. I’ve been wondering if there is any way to replicate my original result.

mechTigerhawk: > a tutorial on Godot it’s a bad tutorial from that code you posted. mechTigerhawk: > I’m never a fan of strings you don’t use strings with signals, not in godot 4. Godot Engine documentation ### Object Inherited By: AudioServer, CameraServer, ClassDB, DisplayServer, EditorFileSystemDirectory, EditorInterface, EditorPaths, EditorSelection, EditorUndoRedoManager, EditorVCSInterface, Engine, EngineD... > As seen above, the recommended method to `connect` signals is not connect. The code block below shows the four options for connecting signals, using either this legacy method or the recommended `Signal.connect`, and using either an implicit `Callable` or a manually defined one. > > > func _ready(): > var button = Button.new() > # Option 1: Object.connect() with an implicit Callable for the defined function. > button.connect("button_down", _on_button_down) > # Option 2: Object.connect() with a constructed Callable using a target object and method name. > button.connect("button_down", Callable(self, "_on_button_down")) > # Option 3: Signal.connect() with an implicit Callable for the defined function. > button.button_down.connect(_on_button_down) > # Option 4: Signal.connect() with a constructed Callable using a target object and method name. > button.button_down.connect(Callable(self, "_on_button_down")) > > func _on_button_down(): > print("Button down!") > > > While all options have the same outcome (**button** ’s `BaseButton.button_down` signal will be connected to **_on_button_down**), option 3 offers the best validation: it will print a compile-time error if either the **button_down** `Signal` or the **_on_button_down** `Callable` are not defined. On the other hand, option 2 only relies on string names and will only be able to validate either names at runtime: it will print a runtime error if **“button_down”** doesn’t correspond to a signal, or if **“_on_button_down”** is not a registered method in the object **self**. The main reason for using options 1, 2, or 4 would be if you actually need to use strings (e.g. to connect signals programmatically based on strings read from a configuration file). Otherwise, option 3 is the recommended (and fastest) method.

The audioserver is a builtin singleton and can be accessed with the global scope AudioServer. Although it doesn’t give you much to work with. Godot Engine documentation ### AudioServer Inherits: Object Server interface for low-level audio access. Description: AudioServer is a low-level server interface for audio access. It is in charge of creating sample data (playable audio) as ... If you want to debug the audioserver source code you can use a native debugger.