Console controller no response bug noted (repeatable)

[SpaceAce73]

Good day.

Issue details:

It has been noted when viewing another car on track besides one of your own (1x trackside view) that ALL button operations on the controller become non-responsive except for the switch to Home Screen/close the game. This includes the ‘options’ button, so game cannot be saved even after the session fully completes and moves to the summary screen. This has been noted both recent times in Q2 of the S1 first race. It happens when I switch from one of my drivers to watch a competitors run using and switching to them via the leaderboard interface on screen and having it set to watching the sectional status updates. It appears to occur once the driver being viewed completes their lap and it updates the last section color bar.

Platform details:

• PlayStation 5 console
• Using PlayStation 4 version of game (due to having other PS4 console so as to move saves between them when desired as PS4/5 saves appear to be incompatible with each other)
• PlayStation 5 controller
• Latest update applied as on Nov 26, 2022 (v1,10 I believe it is)

I will update if I discover this happens in all race sections of any race weekend. I will also try to report back if it is noted on the PS5 native version of the game running on the PS5 and/or if it also happens using the PS4 console and it’s controller on that platform.

Thanks

 

[SpaceAce73]

I have not had this happen as yet on my Aston Martin starting career on the PS5/PS5 version. But, none of my drivers made it to Q2 either like in the above PS4 version on PS5 console report… That was with Alfa Romeo but unclear if the team would be relevant really. I will continue to test and also curious if same save does it on the actual PS4 console as well.

 

[SpaceAce73]

So it appears to happen using the PS4 version on the PS5 console at least nearly 100% repeatable by this method:

• open standings ‘tower’ using the center button on PS5 controller
• (I toggle over to the ‘sector’ tab, but not sure this is required)
• using the d-pad down, if you go to bottom/last driver and attempt to go “down” one more (which normally would cycle back up to top driver), the control inputs lock and you are done at that point. You will never regain any control of any buttons or options via the controller.
• the only thing you can do at this point using the controller is tap the center button and close the game.

So far this does not seem to an issue using the PS5 version on the PS5 console. I haven’t tried the PS4 version on the PS4 console to verify but I will.

Hope this aids in any possible troubleshooting that may be explored. Naturally the ‘workaround’ would be to attempt to remember NOT to d-pad past the last listed driver on the leaderboard.

 

[SpaceAce73]

So I can now confirm that all controller input response will stop working on the PS4 version regardless of the console being played on. This again occurs if you happen scroll past the bottom driver using the on screen leaderboard.

 

[SpaceAce73]

This appears to have been fixed for me after last patch deploy to the PS4 versions. Not sure if it was just a glitch with my installs or it was actually patched… either way, good to have corrected.

 

[DeVip]

This absolutely happens on PS5, becaue that's where I'm playing. Last it happened was yesterday. One of the patches introduced the issue a while back. It happens only during Qualifying. If you select the leaderboard and try to move past the top driver -- because the wrap-around scroll feature is often quicker than moving all the way down the list -- the controls freeze. And waiting for quali to end doesn't unfreeze them. Everything stays frozen. I thought these latest patches must surely fix this, but nope. It's annoying as hell. The game keeps running but you can't do a thing. The amount of times I've had to press PS button and close the game mid-session is ridiculous, because I keep forgetting this is a thing. Because, y'know, it shouldn't be there, and doesn't happen at any other time in the game. Only during qualifying.

 

[DeVip]

I should add that this issue happens across all qualifying sessions; however, if your drivers have done one qualifying run, in any of the sessions they make it to, the issue ceases to be a thing. It's very strange.

 

[SpaceAce73]

Thanks for the update… possibly I was not in qualifying when I thought it was now gone… I’ll definitely be aware of this and keep an eye on that.