https://www.reddit.com/r/destiny2/comments/js2xsf/beyond_light_buttons_not_working_on_ps_remote_play/?utm_medium=android_app&utm_source=share
Seriously, I have tried long enough. It is frustrating as hell not being able to do shit. Fix this right now or give me my damn money back.
-
1 ReplyI have the same issue - was working fine before beyond light update. I have tried multiple controllers and using bluetooth/ wired with PC through remote play app.
-
The controls have basically been reset to those you would use when using a PS Vita, which is fine if you have a Vita but very annoying if you don’t! The Vita only has L1 and R1 which are used for ADS and shoot, and when playing D2 you need to use the touchscreen for grenades and melee. This works currently on Remote Play if you are using a touchscreen device, e.g. mobile phone or tablet. If you touch the screen near the top just left of centre you will get a grenade, and just right of centre for melee. Touch both together for your super. To sprint on the Vita you need to hold the “down” button on the D pad whilst moving the left thumb stick. This is fine on the Vita as the thumb sticks are very small and close to the D pad so you can easily do both at the same time with your left thumb. However this is not so easy on a controller and virtually impossible on a touch screen device. So basically the game is currently unplayable via PS remote play unless you have a PS Vita. Dear Bungie - please fix this ASAP for the sanity of all remote players!
-
Please like this post https://www.bungie.net/en/Forum/Post/257510223/0/0
-
ok so glad others are seeing the same thing. my controllers work just fine on my ps4 at home and trying to use it at work lol on my laptop to play while working.. lets see.. fire button layout hasn't changed yet its r1 not r2, melee is the big huge square that usually brings up the ghost.. which means I can't bring up my ghost. I can't run etc.. seriously WTF. sigh..guess I will have to work lol
-
Yup, glad it's not just me.
-
1 ReplySame Problem.
-
Hello. This is still a problem. Hard to understand how something like this was missed. Even harder to understand how it hasnt been abruptly migrated back to old behavior. Thank you.
-
2 RepliesSame issue - there are 2-3 other posts with the same info