Is it a me thing or a ps5 console thing?

+
Just want to confirm whether this is a me thing or not.

I have experienced 3 technical issues related to console before

1. The sprint button is a bit .. off.. sometimes it doesn’t even trigger a sprint. Googling tells me I’m not exactly alone but is this something that they have fixed and I just continue have issue or has the issue never been fixed? It unfortunately makes many perks related to sprinting and gliding etc fairly useless since they’re unreliable.

2. Pressing the touchpad to open the menu UI with map and inventory etc can be a bit weird with the cursor. Usually it is centered in the middle but I have the cursor appearing on the sides of the screen.

3. Some sections such as the map, you always have to press back twice to leave the map view. Unsure if this is intentional behavior and if so not sure why.
 
Hm. All control/controller things. You can definitely send that into CDPR Support as a single ticket.

Do you have another controller that will work on your Playstation that you can try? See if it's the same there.
 
Hm. All control/controller things. You can definitely send that into CDPR Support as a single ticket.

Do you have another controller that will work on your Playstation that you can try? See if it's the same there.
Yeah I have an extra I have never used before and it’s same. Thought maybe it was some issue w controller but don’t have stick drifts or nothing in other games :/ I did find some people with similar issues but not enough answered that it can be considered a pattern if that makes sense. So kinda thought maybe more people knew here.
 
I have similar issues with sprinting, also sometimes that perk that allows optic camo to activate while sneaking simply stops working and I have to remove the perk point and re-apply and then it works again. Easy fix, but still annoying.
 
Definitely sounds like it's an issue, though I have no idea what could be causing this, especially on a console. Send the reports in here:

If possible, try to briefly explain how to recreate the issue and the situations where it seems most likely to occur. (I know that may be hard, as it doesn't sound as if it happens in any particular place. Maybe focus on the specific commands that seem not to register, while other inputs are read normally.)

Speculating:
I don't own a console, but if this were on PC, my first hunch would be that it would be related to input lag created by frame generation. Those frames are "false frames", created by the AI to smooth performance, and not frames that can be used as key frames by the game for the purpose of running scripts. This can often create the feeling of input lag if the game's FPS drops below a certain point (even if the performance feels smooth enough because of the frame generation.) It's possible that something similar is happening here. The PS5 does support frame gen, so hopefully it will be as simple as that.
 
Last edited:
Top Bottom