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

profile compatible with v1.26.0 #34

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SB3NDER
Copy link

@SB3NDER SB3NDER commented Feb 11, 2022

vJoy controller profile compatible with cemu v1.26.0,
the uuid need to be replaced with the correct one from a saved profile

vJoy controller profile compatible with cemu v1.26.0,
the uuid need to be replaced with the correct one from a saved profile
@sripadks
Copy link

sripadks commented Feb 15, 2022

At least for Cemu 1.26.2 using the controller profile .txt files provided with v0.4.1.4 works. Loading the profile, and closing the input settings page and reopening it will have properly converted the profile to the newer version.

EDIT: The import/conversion is not perfect. As of now, the mapping for up/down on both left and right sticks are reversed. That is to say pressing W/S for up/down is taken as down/up with the default import mapping for example.

All this to say this PR should probably be tested and expanded to other profiles.

@SB3NDER
Copy link
Author

SB3NDER commented Feb 16, 2022

this just a workaround for the v1.26.0 and v1.26.1 which I tested, it has the problem than it needs the correct uuid which i think differ for every machine, so it isn't portable without some edit.
if the .txt files work with v1.26.2, we can just edit that.

@sripadks
Copy link

sripadks commented Feb 17, 2022

Well you are not wrong in that newer Cemu require uuid to work. But I don't think the profiles need them though. From what I have seen, the profiles can be uuid agnostic. We can just set the uuid to 0. Cemu will automatically assign the correct uuid upon loading the profile and create a controllerX profile where X is the controller number 0 indexed. This is the general behavior I have noticed.

So I think it is best to use the xml profiles as they are more readable and are required by Cemu.

Also, after some fiddling around, I fixed the reversed issue for the vJoy devices. The fix was quite simple but required a bit of banging head to wall as the OG profiles are a bit unreadable (that is to say it isn't obvious what number refers to which emulated key). Now I am looking to fix vXbox (if it presents any issues that is).

EDIT: After a brief moment of thought, I do agree that we can let the sleeping dogs lay and let the profiles be txt files. We can just fix the button mapping in the text files and let Cemu handle the conversion. But I don't know how long term this solution is as Cemu can switch to XML only profiles (which I don't think will happen for at least the .26 and .27 minor versions as they would want to ensure some sort of back compat). That being said, one can always load up the Cemu that does the conversion and that use that XML file if Cemu ever stops the conversion. So the jury is up in the air and depends on what (if anything) cemuuser8 wants I suppose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants