I am trying to use remote play to connect with my ps4. However every time I connect it congresses the controls but they are not the right ones. My melee is my touchpad and my aim is L1 and firing is R1. This is the first time I'm encountering the problem so I assume it has something to do with the new update. My controller works fine in other games so I believe the problem is with my game and not the controller. Even when I connect via the mobile app the controllers are messed up. Is there any way to fix this or is destiny 2 simply not compatible with remote play anymore
-
4 RepliesHi there, Bungie is aware of Remote Play control issues and is investigating. [quote]When using PlayStation Remote Play, controller settings reset to default. [/quote] [url]https://www.bungie.net/en/Explore/Detail/News/49833[/url] Check the @BungieHelp Twitter frequently and future TWABs for more information on this issue.
-
3 RepliesThe 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!
-
1 ReplyEdited by swordlogic: 11/14/2020 4:22:35 AMBeen a very annoying bug I've been dealing with since Beyond Light launched. Bungie's acknowledged it but no other information besides this.