Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to enter shift key for some games #15010

Closed
2 of 4 tasks
Panderner opened this issue Oct 11, 2021 · 8 comments
Closed
2 of 4 tasks

Unable to enter shift key for some games #15010

Panderner opened this issue Oct 11, 2021 · 8 comments
Labels
Needs hardware testing Testing on a real device needed to determine correct behavior.
Milestone

Comments

@Panderner
Copy link
Contributor

What happens?

In All Kamen Rider: Rider Generation 2 the final option is listed in title screen and select enter password button. and there is no select button to shift keys
Screenshot (46)
Captital letters are required in order to unlock Kamen Rider Wizard in All Kamen Rider: Rider Generation 2.

What should happen?

In other games like Monster Hunter has select button to shift keys.
Screenshot (45)

What are you using?

What hardware / device and operating system?

Windows 10 Pro

What graphics card (GPU) or mobile phone model?

NVIDIA GeForce GTX 1050Ti

What PPSSPP version (standalone/official), and did it work before?

V1.12.2

Which game or games?

NPJH50617 - All Kamen Rider: Rider Generation 2

Checklist

  • Test in the latest git build in case it's already fixed.
  • Search for other reports of the same issue.
  • Try resetting settings or older versions and include if the issue is related.
  • Include logs or screenshots of issue.
@unknownbrackets
Copy link
Collaborator

Games can specify what keys should be allowed, and we intend to limit the same way a real PSP would. We must be getting it wrong here, if it's supposed to only show uppercase characters for example...

There's no demo or anything that shows this behavior, right? I'd really want to see what the inputtype is, and if any of the other values in the struct are set...

-[Unknown]

@Panderner
Copy link
Contributor Author

Here's a video for All Kamen Rider: Rider Generation 2:
https://youtu.be/yEZ9J2PZY9w

@unknownbrackets
Copy link
Collaborator

Can you try the test build here? This will write the parameters for the OSK to the log. That's what I'm after:

https://github.com/unknownbrackets/ppsspp/actions/runs/1350677194

Please paste (ideally) the log lines starting with "OSK params:" or "OSK fields:" here, or screenshot them.

-[Unknown]

@Panderner
Copy link
Contributor Author

Here's a log for OSK using unknownbrackets's artifact build:

50:48:263 user_main    I[SCEUTIL]: Dialog\PSPOskDialog.cpp:332 OSK params: sz=64, fields=1, state=0, unk=00000000
50:48:263 user_main    I[SCEUTIL]: Dialog\PSPOskDialog.cpp:333 OSK fields: unk00=00000000, unk04=00000000, lang=0, unk_12=00000000
50:48:263 user_main    I[SCEUTIL]: Dialog\PSPOskDialog.cpp:334 OSK fields: type=4, lines=1, unk_24=00000001, outlen=18/0
50:48:265 user_main    I[SCEUTIL]: HLE\sceUtility.cpp:594 00000000=sceUtilityOskInitStart(09d05df0)

and Here's a screenshot using a same build above:
Screenshot (47)

@unknownbrackets
Copy link
Collaborator

So, inputtype is indeed PSP_UTILITY_OSK_INPUTTYPE_LATIN_LOWERCASE. However, an unexpected field unk_24 is 1.

It's possible this field could mean to allow uppercase or force uppercase in some way.

-[Unknown]

@unknownbrackets unknownbrackets added the Needs hardware testing Testing on a real device needed to determine correct behavior. label Nov 14, 2021
@hrydgard hrydgard modified the milestones: Future, Future-Prio Nov 15, 2021
unknownbrackets added a commit to unknownbrackets/ppsspp that referenced this issue Jul 17, 2022
In previous tests, this seemed to be limited, but now I can't reproduce.
Instead, let's just use it as the hint for the default case.
See hrydgard#15010.
@unknownbrackets
Copy link
Collaborator

I'm having trouble testing the unk_24 field - it just locks up my PSP because the OSK never comes up, and there's no way to exit. Have to hard reset. Maybe it's a flag to hide the OSK display or something, but it's annoying to test with hard resets...

-[Unknown]

@hrydgard
Copy link
Owner

This should be better now with #15698.

@Panderner
Copy link
Contributor Author

Now it worked.
Screenshot (58)

@hrydgard hrydgard modified the milestones: Future-Prio, v1.13.0 Jul 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs hardware testing Testing on a real device needed to determine correct behavior.
Projects
None yet
Development

No branches or pull requests

3 participants