pyremoteplay icon indicating copy to clipboard operation
pyremoteplay copied to clipboard

Python API for using PlayStation Remote Play

Results 11 pyremoteplay issues
Sort by recently updated
recently updated
newest added

Why I cant use usb connected controller in `pyremoteplay` ? Only weird keyboard mapping. Help me please :(

Hi there! Would it be possibel to add support for game controllers in the command line version? Thus, it would be also good if one could have an option to...

![image](https://github.com/ktnrg45/pyremoteplay/assets/14042413/297c1703-9934-49ac-abed-cddd2f9440a2) I have 2 PS5. I update one , this error happend:Version not accepted! another one with old firmware works well. And i update another one firmware. the error also...

My code: ``` mybot.Device.device.controller.stick("left", point=(0.7, 0.7)) print("left! 07 07") time.sleep(0.1) mybot.Device.device.controller.button('CROSS', 'tap') print("JUMP!") time.sleep(1) mybot.Device.device.controller.stick("left", point=(0.7, 0.7)) mybot.Device.device.controller.button('CROSS', 'tap') ``` after `mybot.Device.device.controller.stick("left", point=(0.7, 0.7)) mybot.Device.device.controller.button('CROSS', 'tap')` I get an error:...

Otherwise we enter a persistent error state where we keep on trying to pack numbers greater than 63335 into an unsigned int16 My controller polling rate must be much higher...

Keep getting this error when I try to use this prompt pyremoteplay {192.168.4.194} --register pyremoteplay: error: unrecognized arguments: -encodedCommand -inputFormat xml -outputFormat text and when i try to open pyremoteplay...

2023-04-05 16:08:00.490 Python[5022:102501] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'nextEventMatchingMask should only be called from the Main Thread!' *** First throw call stack: ( 0 CoreFoundation 0x000000019fda4418...

general Q with this package I will can control my dual sense on ps5 with python code ? issue 1 url = oauth.get_login_url() -- not a method, needed to be...

I've been noticing the controller event history being quite flaky, with spontaneous events being triggered in some scenarios, and controller buttons entering a "stuck" state until hit again in others....

The current mode callout causes "no such ……attribute" errors on recent PySide6 installs (At least a fresh PySide6 install on Ubuntu 22.04)