Possum / LumaLocaleSwitcher

Front end to Luma3DS compatible locale system.
MIT License
130 stars 11 forks source link

Region Not Changing Permanently? #12

Closed PolarPeridot closed 7 years ago

PolarPeridot commented 7 years ago

Hi! So I'm trying to change the region Yo-Kai Watch 3 Sukiyaki is so that way my DLC will work, but no matter how many times I change it, whenever I refresh LLS, the region goes back to being the system default. I don't know what to do and it's really frustrating. Please help me?

Possum commented 7 years ago

Which version of LLS and also what version of Luma?

PolarPeridot commented 7 years ago

The latest version of LLS, and I'm not sure how to check which version of Luma.

PolarPeridot commented 7 years ago

I updated Luma and it's still not staying changed. It keeps saying System Default, but when I select the region the language changes too. Does that mean it DID change but it isn't showing that it is?

PolarPeridot commented 7 years ago

Nevermind, the DLC still won't load. I'm on the latest version of LLS and the latest version of Luma.

PolarPeridot commented 7 years ago

What do I do????

PolarPeridot commented 7 years ago

I have the "Enable Region/language emu. and ext. .code" enabled and all of the text files are in the locales folder. Please help me figure out why it isn't wanting to work!

Possum commented 7 years ago

I confirmed, it's definitely a bug.

If you are on stable Luma (6.6) try the 0.02 release.

PolarPeridot commented 7 years ago

OK, I'll try that version and post what happens.

PolarPeridot commented 7 years ago

When I try to open it, FBI says "Failed to acquire kernel access"

PolarPeridot commented 7 years ago

I'll try opening FBI itself then install it

PolarPeridot commented 7 years ago

Hooray, it finally worked!!! Thank you!

Possum commented 7 years ago

Reopened because there is a bug that needs to be fixed. Thanks for the report!

PolarPeridot commented 7 years ago

No problem! :) Glad I was able to help you find the bug.

Possum commented 7 years ago

This was a display issue as far as I can tell, and should be fixed in the latest release.