this is it the works , hope i have free time on week end to do somethinghey, you should add an emummc.ini swapper so you can swap between emummcs on the fly, i and a lot of other people would appreicate this.
this is it the works , hope i have free time on week end to do somethinghey, you should add an emummc.ini swapper so you can swap between emummcs on the fly, i and a lot of other people would appreicate this.
noone need this, this rip the fps from games like mk11
i need only XCI for Atmo or OC for SXOS !!!
atmo emunand without xci or a mounting option is pointless.
oh lol this fixed long ago im drafting a new release 2.0.0Remember that latest Atmosphere has changed the entry names in the emummc ini file. For example, It is no more "emummc_enabled", but just "enabled".
path is hardcoded in ams, https://github.com/Atmosphere-NX/At...91273/fusee/fusee-secondary/src/nxboot.c#L236Thank you for that tool.
I have a general question, doesn't atmosphere allow emuMMC path to be outside of "emuMMC" folder? can you choose your own folder name? (just to make it less easier to detect by nintendo )
make sure your ini layout is set like this and youll have no problems next, "my ini" (just like NYX set it up)It has various bugs. It truncates the "sector" entry of the ini file, damaging it. This happens also if enabled is at the bottom of the ini, "far away" from the "sector" entry,
make sure your ini layout is set like this and youll have no problems next, "my ini" (just like NYX set it up)
[emummc]
enabled = 0
sector=0xaf9c000
path=emuMMC/RAW1
id=0x0000
nintendo_path=emuMMC/RAW1/Nintendo
well i have incountered this bug only ones and after fixing/replacing the ini . it never accured again, so im not sure.This is exactly how my ini looks like. Other emummc togglers have no issue.
well i have incountered this bug only ones and after replacing the ini . it never accured again, so im not sure.
please check it out
im sure its weird behaviour and i never couldnt replicate it again after the time it happened and as i said i have fixed sector entry manualy and this bug never happened again so im not even sure atm.I believe your ini parser assumes CRLF as the new line in the file. I am not sure about that, but after adding some emtpy new lines between the different entries, it started working.
I just checked. The problem is the way the new line is encoded in the ini file. If it is linux style (known as LF, which is one byte), the tool truncates what comes after "enabled", this because it assumes Windows style new line instead (known as CRLF, which is two bytes instead).im sure its weird behaviour and i never couldnt replicate it again after the time it happened and as i said i have fixed sector entry manualy and this bug never happened again so im not even sure atm.