mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-04-25 14:16:10 +03:00
[GH-ISSUE #1096] Linux Build Trigger Mapping #329
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#329
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 @willyvvu on GitHub (Mar 29, 2013).
Original GitHub issue: https://github.com/hrydgard/ppsspp/issues/1096
On the Linux build of PPSSPP (The one with the executable called PPSSPPSDL, by @angelXwind) Q maps to the right trigger and W maps to the left. They are inverted!
@unknownbrackets commented on GitHub (Mar 29, 2013):
Heh, nice catch. This actually needs to be changed in native. I guess it may be affecting some phones too.
-[Unknown]
@willyvvu commented on GitHub (Mar 29, 2013):
Thanks! Maybe since the directional pad is on the left side with the buttons on the right, could WASD be the digital pad and UIJK be square, triangle, X, and O, respectively, with triggers Q and E? Just an idea.
@unknownbrackets commented on GitHub (Apr 7, 2013):
Well, I think that's basically #116.
-[Unknown]
@willyvvu commented on GitHub (Apr 8, 2013):
Hmm... I downloaded the latest version 7-518 I believe, and the triggers still haven't been fixed... Tested on Linux x64.
@unknownbrackets commented on GitHub (Apr 8, 2013):
Darn. Is this SDL or Qt?
-[Unknown]
@willyvvu commented on GitHub (Apr 8, 2013):
It's SDL. I think that I should wait a while for the source to rebuild, and try again.
@willyvvu commented on GitHub (Apr 8, 2013):
Sorry for the false heart attack. It's fixed in the newest one I checked, 7-532. Thanks!