Correct
And yeah that's the catch, it apply the changes globally, since tyrquake quick menu doesn't allow configure sticks :c
- Thread starter aliaspider
- Start date
- Views 2,005,176
- Replies 14,143
- Likes 86
And yeah that's the catch, it apply the changes globally, since tyrquake quick menu doesn't allow configure sticks :c
So the Quick Menu for TyrQuake doesn't have these options?
Only the global Settings?
Do I have to reinstall the channel everytime I delete and re-add that Retroarch folder or does it work like a Wiis forwarder just pointing the system to the retroarch folder?
Nah once you install that channel thats it, no need to mess or reinstall it. Yes. it points to SD:/retroarch/cores
- Joined
- Apr 19, 2015
- Messages
- 1,023
- Trophies
- 1
- Location
- Stuck in the PowerPC
- Website
- heyquark.com
- XP
- 3,909
- Country
Keep in mind that's for x86/ARM; the one we need for Wii U is a different bounty entirely which will likely get done once this is complete
So, I was messing around with tyrquake code and found out the lines of code that invert the right stick y axis, compiled and it works! I only tested a few minutes but seems to work fine.
Changed the y axis for gamepad, wii classic controller, wii u pro, maybe hid?
.rpx is in my sig, funny thing the file is actually about 1/4 smaller than the real one
@ShadowOne333 @Warwick
Changed the y axis for gamepad, wii classic controller, wii u pro, maybe hid?
.rpx is in my sig, funny thing the file is actually about 1/4 smaller than the real one
@ShadowOne333 @Warwick
How about sending a PR to GitHub?So, I was messing around with tyrquake code and found out the lines of code that invert the right stick y axis, compiled and it works! I only tested a few minutes but seems to work fine.
Changed the y axis for gamepad, wii classic controller, wii u pro, maybe hid?
.rpx is in my sig, funny thing the file is actually about 1/4 smaller than the real one
@ShadowOne333 @Warwick
Or maybe that would let the LibRetro guys that an option to invert the axis is missing from TyrQuake (and that it is desired lol)
Nah, it's hardcoded for every Wii U input controller, means that there's no way to invert the Y axis again, there are people that prefer inverted Y controls I guess the tyrquake guy from github was one of them
- Joined
- Apr 19, 2015
- Messages
- 1,023
- Trophies
- 1
- Location
- Stuck in the PowerPC
- Website
- heyquark.com
- XP
- 3,909
- Country
Isn't there a way to change the axis inversion from RetroArch's input settings?Nah, it's hardcoded for every Wii U input controller, means that there's no way to invert the Y axis again, there are people that prefer inverted Y controls I guess the tyrquake guy from github was one of them
- Joined
- Apr 19, 2015
- Messages
- 1,023
- Trophies
- 1
- Location
- Stuck in the PowerPC
- Website
- heyquark.com
- XP
- 3,909
- Country
I'm fairly sure you can do per-core config overrides. You'd definitely want to figure out a way of doing this from the frontend; it's unlikely that you'll get any changes through to the core.
So, I was messing around with tyrquake code and found out the lines of code that invert the right stick y axis, compiled and it works! I only tested a few minutes but seems to work fine.
Changed the y axis for gamepad, wii classic controller, wii u pro, maybe hid?
.rpx is in my sig, funny thing the file is actually about 1/4 smaller than the real one
@ShadowOne333 @Warwick
Genius! Thanks so much cucholix! I am definitely going to use your file.
Cheers!
When you say frontend you mean settings > input > user 1 > etc... ? Because that are global changes and affect other cores.
The quick menu reflect only per-core changes, that's what we'll looking for invert the y axis only for quake.
Anyway, I tried editing TyrQuake.rmp that's loaded per-core and it didn't change the y axis, also tried editing internal game config and nothing, it seems to me that if the quick menu controller/options don't have a due setting the core will not parse any "fake" (forced) parameter.
Editing the .rpx directly worked though
, of course is not the more convenient "elegant" way since you are stuck to a specific version that will not available when you update the core.
