-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open up Inputs for Hardware IO #7
Comments
Amazing device! :) What's the idea? To interface with PS2/PS3 consoles? I know that there are some projects for a diy ffb wheel. But they are for PC usage only and won't work on consoles. |
Hey! Thx for the quick answhere and compliment :) Beeing compatible with consoles would be the ultimative goal. So far its PC only and running on FFBoard. |
It's mostly how it works. Just making it work on ps2/ps3 should be trivial. It's a matter of having the correct vid:pid and usb descriptors. I would not add support for hardware IO on this project as it's heavily tied to it's usb input. But forking it into another project would be ideal. Btw check out the Santroller adapter. It can do two picos wireless and it can do "auth" on the modern consoles. |
That gives Hope! :D I tryed to make sense from what im reading while scrolling through the code, for some days now. Long story short: Maybe some weeks before you start... I may have to beg my wife for permission for such a donation :D And thx for the link! |
We can talk more about the project :) |
Sure, got a link? |
Hi Sonik,
ive no idea, if this is even possible.
From my bare understanding of coding, this firmware presents itselve as device XY and passes through inputs from another device.
So... Is there a way, to "jump" in between that "conversation" and use the hardware IO of the PICO instead?
In short: Create an FFB device.
For sure, its a lot of work, but it would be awesome, if you could have a quick look, if this would even be possible.
And here is the reason, why im asking for it:
https://m.youtube.com/watch?v=QXPe65nvXwo&t=30s
The text was updated successfully, but these errors were encountered: