the menu does not respond to analogue input ,

[rye-74]

Acknowledgements

• I have searched for duplicate or closed bug reports
• I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug

seems not able to naviage the menu with the analogue stick,. this is a prob for me becayse i dont have a dpad.,

How To Reproduce

start game try to use stick

Does this problem occur on original hardware or PCSX2?

Yes, it's unique to OpenGOAL

Expected Behavior

the menu shgould be able to be controlled by the dpad and and left analogue stick

Environment Information

win11

Game Version

NTSC 1.0 (black label)

Have you set the game to something other than 60fps?

No

[dallmeyer]

It's not supposed to. You can enable keyboard inputs if needed, press left Alt and a gray bar will show at the top of the window, you can enable keyboard inputs from somewhere in that menu.

[xTVaser]

I'm ok with tackling this one, this is a change they made to their menu code in jak 2/3 and I intend to refactor the jak 1 progress code and fix a handful of related issues at the same time anyway within the next month (kill me now)

But yeah the workaround for now would be to use your keyboard.

[rye-74]

thanks, i did figure that out as a workaround, thanks for the attention.

…

On Tue, Jul 30, 2024 at 1:22 PM Tyler Wilding ***@***.***> wrote: I'm ok with tackling this one, this is a change they made to their menu code in jak 2/3 and I intend to refactor the jak 1 progress code and fix a handful of related issues at the same time anyway within the next month (kill me now) But yeah the workaround for now would be to use your keyboard. image.png (view on web) <https://github.com/user-attachments/assets/322ecf6a-167f-4fce-bc4f-66f9fd4f15c9> — Reply to this email directly, view it on GitHub <#3617 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANQ6XPXQYYLMI3XINM3NZC3ZO7DUFAVCNFSM6AAAAABLWXKMCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJYHA2DINJUHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>