CP2077 pc showing controller icons/keys

[SenorRagequit]

Dunno what the hell happened, suddenly every icon/key showing is for controller while I dont even have any controller connected.
Restart, reload etc. doesnt help at all.

Anyone else?

[T3X4S_4SS4SSIN]

Dealing with the same issue now. Was not a problem yesterday but just now started out of nowhere. Not sure what the fix is.

[Zeitkrieg]

Same issue here.

[Type 2 Diabetes]

Same, just installed it. Even disabled controllers in the game settings in Steam and still get them. But only after I load a game, it's showing keyboard buttons in the menus before that.

[★REM★]

Some reported disabling controller input in steam fix the issue

[Uraael]

Yep. Same since 2.0 installed. You can't avoid it either:

Press the Keyboard - it changes to Joypad HUD
Move the mouse - it changes to Joypad HUD

Not only this but certain commands don't work either now, like the Toggle Crouch.

Game is Broken.

[Uraael]

Originally posted by ★REM★:

Some reported disabling controller input in steam fix the issue

It does nothing.

[CephalopodDarius]

CDPR are aware of the issue, and have acknowledged they're looking into it on their support page: https://support.cdprojektred.com/en/cyberpunk/pc/sp-technical/issue/2491/update-2-0-known-issues

The majority of reports of this issue seem to be on Linux. It's probably some unexpected interaction between Proton and the control scheme detection logic, though a couple people in another thread mentioned they had the issue on Windows, so probably not unique to Proton, I'm on Linux and have the issue.

[Alfigue]

same here :(

[CephalopodDarius]

Found a workaround in another thread: https://steamcommunity.com/app/1091500/discussions/7/3878218563598783920/?ctp=11#c3878218962819954974

There's only one byte that needs to be replaced, but it's safer to find it by looking for it and its adjacent bytes to make sure you're not overwriting something else when they update the exe. I went to the bin/x64 directory and did the following:

> perl -pi -e 's/\x74\x09\xe8\xc7\xa8\x75\x00/\xEB\x09\xe8\xc7\xa8\x75\x00/g' Cyberpunk2077.exe

After that the prompts show up correctly for me and all the controls have worked fine.

[Tarnished Tom Snooze]

Originally posted by CephalopodDarius:

CDPR are aware of the issue, and have acknowledged they're looking into it on their support page: https://support.cdprojektred.com/en/cyberpunk/pc/sp-technical/issue/2491/update-2-0-known-issues

The majority of reports of this issue seem to be on Linux. It's probably some unexpected interaction between Proton and the control scheme detection logic, though a couple people in another thread mentioned they had the issue on Windows, so probably not unique to Proton, I'm on Linux and have the issue.

CDPR solution is "restart the game" yeah that's their solution to everything w cyberpunk xD

[jarpe]

Restarting game helped me.

[T0b1maru]

Originally posted by CephalopodDarius:

Found a workaround in another thread: https://steamcommunity.com/app/1091500/discussions/7/3878218563598783920/?ctp=11#c3878218962819954974

There's only one byte that needs to be replaced, but it's safer to find it by looking for it and its adjacent bytes to make sure you're not overwriting something else when they update the exe. I went to the bin/x64 directory and did the following:

> perl -pi -e 's/\x74\x09\xe8\xc7\xa8\x75\x00/\xEB\x09\xe8\xc7\xa8\x75\x00/g' Cyberpunk2077.exe

After that the prompts show up correctly for me and all the controls have worked fine.

Thank god for an easy fix. The idiots still have not patched this..

[Greggio]

Having the same problem too. it shows me first the pc icons and suddently changes to console ones. so infuriating

[Sumeragi]

Have the same issue on my steam deck. On my Windows 10 PC not until now.

[Shotgun Solutions]

Originally posted by SenorRagequit:

Dunno what the hell happened, suddenly every icon/key showing is for controller while I dont even have any controller connected.
Restart, reload etc. doesnt help at all.

Anyone else?

I've had the bug a few times. usually restarting fixes it.