Still confused about GARLICPLUS/RG35XXPLUS builds

[purelygrey]

Relates to #100.

Recently I've been running the latest dev build on RG35XX H using Knulli, and it works great. At the same time the GARLICPLUS build (1.4.2 release) which seems like it should be used for non-stock OSes doesn't work, and RG35XXPLUS has wrong mappings out of the box, so I feel mildly confused. Given that RG35XXPLUS build also works great on MuOS, it begs the question what is the use case for the GARLICPLUS build? Does it work in GarlicOS 2.0? Maybe it is kind of unneccessary at this point (Garlic 2.0 doesn't seem to be a viable option for now)?

I now have working RG35XX Plus and RG35XX H on hand, can test anything and everything if needed

[muldvar]

hi @purelygrey i noticed the wrong bindings on RG35XXPLUS too when i installed it on MuOS, i have not been able to figure out the correct bindings though, is it possible you can share these with me? or maybee put them here for future refference?

[purelygrey]

hi @purelygrey i noticed the wrong bindings on RG35XXPLUS too when i installed it on MuOS, i have not been able to figure out the correct bindings though, is it possible you can share these with me? or maybee put them here for future refference?

GARLICPLUS build has the correct bindings for MuOS, you can grab the correct ones from there

In case you'll ever need to figure out the buttons yourself:

1. Set <DUMPEVENT value="YES" /> in config.xml
2. Run lgpt, press the buttons you need the codes for (I usually press one I want to look at many times, let's say about 20)
3. Check lgpt.log, should be in the lgpt folder. Look for many consecutive button press logs -- they would be the keycodes you need. Adjust config.xml/mapping.xml accordingly