DualShock 4 Controller Integration into "Stellarium Remote Control" Plugin #4785
Replies: 3 comments 5 replies
-
|
Can this be generalized to any kind of joysticks/gamepads? Particularly, so that the tab in the UI wasn't just dedicated to a particular model. |
Beta Was this translation helpful? Give feedback.
-
Re: Can this be generalized to any kind of joysticks/gamepads?Thank you for this excellent and timely question, 10110111! 🎮 You've hit on exactly the right direction for this feature. The answer is YES – and I've already been researching the best approach to achieve universal controller support. The Current Implementation: A FoundationFirst, let me clarify that my current DualShock 4 implementation was designed with generalization in mind. The code structure already separates:
This means the architectural foundation is ready for expansion. The PS4-specific parts are primarily the default button mappings and the controller diagram – everything else can be adapted. Research Findings: Universal Controller LibrariesAfter investigating the landscape of gamepad libraries, I've identified several promising candidates that could provide a truly universal solution:
The Most Promising Candidate: Controller SDKAfter thorough evaluation, I believe the Controller SDK (also called Controller SDK) deserves special attention . Here's why: Dual Connection Modes:
Universal Controller Support:
Why this matters for Stellarium: // Current approach (PS4-specific):
if (id.includes('dualshock') || id.includes('ps4')) { ... }
// With Controller SDK:
const manager = ControllerManager.getInstance();
await manager.connect();
manager.on('button-press', ({ button, state }) => {
// Works with ANY connected controller!
executeStellariumAction(mapButtonToAction(button));
});A Staged Approach for ImplementationI propose a three-phase roadmap to achieve universal controller support: Phase 1: Library Evaluation (Current Stage)
Phase 2: Universal Controller ModuleReplace the current PS4-specific module with a new // Proposed architecture
define(["jquery", "settings", "gamecontroller"], function($, settings, GameController) {
const UniversalController = {
init: function() {
GameController.on('connect', (gamepad) => {
// Detect controller type automatically
const type = detectControllerType(gamepad);
loadAppropriateMapping(type);
showControllerDiagram(type);
});
},
// Dynamic button mapping
mapButton: function(buttonEvent, gamepadType) {
// Use community-sourced mappings
return getActionFromDatabase(buttonEvent, gamepadType);
}
};
});Phase 3: Community Mapping Database
Addressing Your Specific QuestionTo directly answer: Yes, the tab UI should absolutely NOT be dedicated to a single model. The new universal tab would:
Future-Proofing with WebHIDThe Controller SDK library's use of WebHID is particularly exciting . While the Gamepad API is great for basic input, WebHID opens up possibilities for:
Next Steps for DiscussionI'd love to get community input on:
A Note on Existing WorkI should mention that there is already a Stellarium Joystick Plugin by Bogdan Marinov that uses SDL2 for controller support . While that's a C++ plugin, we could potentially:
ConclusionThe path to universal controller support is clear and achievable. My DualShock 4 implementation was always intended as a proof of concept and a foundation for something bigger. With the right library choice and community input, we can create a controller system that:
I'm particularly leaning toward the Controller SDK approach because of its dual-mode support and future-proofing with WebHID, but I'm eager to hear what the community thinks! What are your thoughts on these options? Have you or others worked with any of these libraries before? |
Beta Was this translation helpful? Give feedback.
-
|
Whoa, that looks really interesting, thanks a lot! We had multiple requests for gamepad support. There was a gamepad module that would have had to be connected to MainController for Qt5 but not Qt6, so my motivation was limited. But this is a quite different approach. I have no physical game controller to test, but a little Bluetooth keyboard with gaming buttons which I at some time wanted to play with. A generalized solution (maybe with user-configurable key map?) would be great! It's maybe a bit late for 26.1 inclusion without testing (and we still have a few PRs to process!), but let's schedule this for 26.2. |
Beta Was this translation helpful? Give feedback.
-
Re: Gamepad Support for Stellarium Remote ControlThank you, gzotti! I really appreciate your positive feedback! 🎮 Quick Response to Your PointsYes, a generalized solution with user-configurable key mapping is exactly what I have in mind! My DualShock 4 implementation was always meant as a proof-of-concept for something much bigger. The Qt5 → Qt6 ChallengeI completely understand why the C++ gamepad module lost momentum – Qt transitions are painful. This is precisely why the web-based approach through Remote Control makes sense:
The SDL_GameControllerDB DiscoveryI've been exploring the SDL_GameControllerDB and it's perfect for our needs:
// One parser = support for thousands of controllers!
fetch('https://raw.githubusercontent.com/mdqinc/SDL_GameControllerDB/master/gamecontrollerdb.txt')
.then(response => response.text())
.then(data => {
const controllers = parseSDLDatabase(data);
// Now any connected controller Just Works™
});Proposed Path Forward for 26.2
My Question to YouSince you mentioned scheduling for 26.2, would you prefer:
I'm happy to adapt to whatever fits best with your release planning! Best regards, P.S. – I'm comfortable with JavaScript but still learning C++/Qt. Focusing on the Remote Control plugin lets me contribute where I can add real value! 😊 |
Beta Was this translation helpful? Give feedback.
-
|
I think a general solution (1): SDL database with PS4 and hopefully some other example within SDL would be best. Compare wit the telescope control plugin: we have two "native" solutions and three "general" frameworks (ASCOM, INDI, RTS2). If we only said INDI/ASCOM, we won't have to maintain the "native" supports. I have not checked the actual code, so I don't know why (3) would be considered. What is very important: documentation for total beginners; How to configure my XY controller. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @gzotti, thank you for your patience and your valuable feedback. I apologize for the delay in providing the code; I have now prepared the files for review. You are absolutely right about the importance of a general solution. The current To help clarify the current state, here is an explanation of the modified and added files, and where they belong in the
Regarding your point (3) in the previous discussion, the As a next step, I will be researching how to integrate an SDL-based approach or a universal library like Thank you again for your guidance. Please let me know if you have any specific questions about the code once you have had a chance to review it. index.html |
Beta Was this translation helpful? Give feedback.
-
|
Can you please create a pull request? As said, we should schedule it for 26.2. Sorry, I don't have time for thorough review for 26.1. (Or anyone else? If it does not disturb the other operation, we can have it in 26.1, including 1-2 pages of explanation in the User Guide. (If it's only PS4, maybe 1/2 page is enough, if users are open to configure their own gear by some form of text file (.ini, .json, ...), this must be explained.) |
Beta Was this translation helpful? Give feedback.
-
|
+1 for pull request. I have a Defender gamepad - so, I can test it, probably partially |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🎮 DualShock 4 Controller Support for Stellarium Remote Control
Hello Stellarium community!
I'm excited to share a new enhancement I've been working on for the Remote Control plugin - full DualShock 4 (PS4) controller support with a dedicated tab in the web interface, customizable button mappings, and smooth analog control for Stellarium.
What Has Been Achieved
I've successfully integrated PlayStation 4 controller functionality directly into the existing Remote Control plugin's web interface. The implementation is built on the solid foundation created by Florian Schaukowitsch and Georg Zotti (ESA Summer of Code in Space 2015) and extends it with modern gamepad API support.
Key Features Implemented:
Right stick: continuous zoom control (push up/down)
🎮 Default Button Mapping (Intuitive Layout):
Technical Implementation Details
The integration is built using:
The code is structured as a new module (
ps4controller.js) that integrates seamlessly with the existing Remote Control plugin architecture. It uses the same action system (api/actions) and property system (api/properties) as the rest of the plugin.Future Development Ideas & Possibilities
While the current implementation focuses on DualShock 4, I believe there's tremendous potential for broader controller support. Here are some ideas I'd love to discuss with the community:
Short-term Enhancements:
Long-term Vision: Universal Game Controller Framework
I've been researching a promising project that could revolutionize how we handle game controllers in Stellarium: gamecontroller.js by Alvaro Montoro.
Why this is exciting:
This library provides a universal abstraction layer for game controllers that could:
Key advantages of integrating gamecontroller.js:
Proposed Integration Architecture:
Benefits of Universal Approach:
Discussion Questions for the Community:
What's your experience with game controllers in Stellarium? Have you tried using one before?
Which controllers would you like to see supported?
What features would make controller usage more appealing?
Should we pursue the universal approach via gamecontroller.js, or maintain individual controller modules?
Any astronomers here using Stellarium for outreach? Would a simple controller make demonstrations easier for the public?
Code & Testing
The current implementation is fully functional and ready for testing. I'd love feedback from anyone who:
To test:
Acknowledgments
This work builds upon the excellent foundation of the Remote Control plugin by Florian Schaukowitsch and Georg Zotti (ESA Summer of Code in Space 2015). Their clean architecture made this integration straightforward and maintainable.
I'm also grateful to the Stellarium team for creating such an amazing open-source planetarium that welcomes community contributions.
What are your thoughts? I'm particularly interested in hearing opinions on the universal controller framework idea versus maintaining individual controller support. Also, if anyone has experience with gamecontroller.js or similar libraries, your input would be invaluable!
Looking forward to a productive discussion!
P.S. - I've attached screenshots showing the new controller tab, customization interface, and live joystick preview. Let me know if you'd like to see them!
kutaiba akraa - Aleppo Syria
Beta Was this translation helpful? Give feedback.
All reactions