mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-04-24 21:56:10 +03:00
[GH-ISSUE #5018] IOS - iCade button mapping not 100% working - No triangle mapping possible #2104
Labels
No labels
Atrac3+
Audio
CPU emulation
D3D11
D3D9 (removed)
Depth / Z
Feature Request
Font Atlas
GE emulation
Guardband / Range Culling
HLE/Kernel
I/O
Input/Controller
MP3
Multithreading
Needs hardware testing
Networking/adhoc/infrastructure
No Feedback / Outdated?
OpenGL
PGF / sceFont
PSMF / MPEG
Platform-specific (Android)
Platform-specific (Windows)
Platform-specific (iOS)
PowerVR GPU
SDL2
Saving issue
User Interface
Vulkan
arm64jit
armjit
armv6
x86jit
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ppsspp#2104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @URBANsUNITED on GitHub (Jan 5, 2014).
Original GitHub issue: https://github.com/hrydgard/ppsspp/issues/5018
in the latest stable and unstable versions of ppsspp is the iCade support not 100% working for me.
I can map all buttons except button 9 (triangle)
Tested with two iCade controllers, both do work in other situations/emus.
Modifying the ini doesn't bring the result. Button stays dead.
Not 100% it's Button C (iCadeButtonC = 0x040) aka Y Button
What about the others? Does anybody have similar probe? or is it only me?
Using iPad mini retina 7.04 jb
@ufdada commented on GitHub (Jan 5, 2014):
I don´t have one, but afaik if the keylayout isn´t set English (US) it leads to several errors in other applications too.
It would be interessting to see how the other keys are mapped, could you provide a screenshot of the mapping in ppsspp?
@URBANsUNITED commented on GitHub (Jan 5, 2014):
Here is the proper mapping screen

Button 9 is problematic one, which I can't map. I did this by manually editing the ini file
I've just checked it against the english key layout and bans, it is working 👍
In Retroarch I don't have any issues with the german layout. Maybe you can look into this as the rest of the keys are proper mappable even with german layout ;)
@ufdada commented on GitHub (Jan 5, 2014):
Just saw it in a review-video in youtube and thought it might be helpful ;). Maybe there is already a fix for it out there on another application...
@ufdada commented on GitHub (Jan 5, 2014):
Just looked into Common/KeyMap.cpp, doesn´t look like there is any IOS Support at all for this. Was your default mapping some keyboard-mapping? As far as i can tell this should be done if RestoreDefault() gets called.
@yanthey commented on GitHub (Jan 5, 2014):
Ohh , rare issue. .
@URBANsUNITED commented on GitHub (Jan 13, 2014):
After some more tests. I can confirm that it works with english keyboard settings and qwertz layout.
But it doesn't with German layout or keyboard settings.
I tried icade and keyboard mappings. The result is always the same. Only with english keyboard it does work.
@unknownbrackets commented on GitHub (Nov 10, 2018):
Has anything improved here with latest versions? Perhaps this was a driver issue?
-[Unknown]