It seems like the decompiled scripts causing the settings menu to break also happens on the original decomp as well, so you'll have to take that up with them on their repo.
As for vsync, I haven't tried disabling it before because there's no point. There's no way to disable vsync in Citro3D (the graphics API used), thus vsync is always left on by default in the ini file. Are you getting slowdowns? The main game should maintain 60fps, unless there's some resource-heavy mods out there?
I believe the awkward binds are just the original behaviour of the mobile version of the game. The decompiled scripts should remedy this by binding pause back to the START button, and jumping/spindashing back to A/B/Y. You also have the option to rebind controls in the ini file using bit values taken from libctru. Are these not working at all?
Off the top of my head, the intro movie option in the main menu is gone, the help & options menu is broken (as you mentioned) and reverts to its normal options without the option to open the dev menu (which is present without the decompiled scripts), and the in-game pause menu is reverted to its original form (again missing the dev menu option that the base port contains). There may be more that I missed, though.What unique menu elements disappear? And what do you mean by functionality breaking?
Yes, without using the decompiled scripts this is all true. I didn't take note of the rest of the controls until after I had removed the decompiled scripts and set TxtScripts=false, so whatever I'm saying doesn't apply to the port + decompiled scripts. The port runs just fine for me without the decompiled scripts and maintains more functionality so I'm content with that for now.But, I'd assume if you don't use the Scripts like EnergyFocus is doing with not putting TxtScripts=true the controls are going to revert back to B pauses and A and Y jumping.
I had no reason for disabling vsync, just did so out of habit. I didn't notice any slowdown, only minor hitching when power-ups begin and end which i didn't find disruptive.As for vsync, I haven't tried disabling it before because there's no point. There's no way to disable vsync in Citro3D (the graphics API used), thus vsync is always left on by default in the ini file. Are you getting slowdowns? The main game should maintain 60fps, unless there's some resource-heavy mods out there?
I didn't try to mess with the controls in the ini file since I didn't recognize any of the values. But this is very useful information. I'll give this a try sometime soon and report back.You also have the option to rebind controls in the ini file using bit values taken from libctru. Are these not working at all?