Audioboxer
Member
so , with Rei there is no 3D bug ? or because you downgrade to 2.1 ?
It's because arm9loaderhax runs prior to boot in a sense. Code is locked in before Nintendos boot code kicks in. The way we've had it so far is code running after Nintendos boot code, which produces the 3D bug as well as longer load times, and the occasional boot fail.
Using arm9 with any FW will have 3D working okay.
I'm in a pickle still though from the point of view that there is currently no way for me to create a new emunand or even run emunand9 to restore a sysnand/emunand backup. The only two public payloads are for rei on sysnand or rei on emunand. I'm forced to having to use the sysnand one and while it means my 3DS is working, I cannot run certain homebrew apps right now (mainly just the two apps that can restore backups - they kick you back to HBL as the rei payload runs 10.4 native firm, but I'm on 9.2).
Will be fixed soon enough. Basically, in terms of what we can do with arm9 right now there isn't much as devs need to catchup. If anyone goes to get their OTP file just go back to where you were before with emunand and menuhax until devs release more payloads. Payloads are the .bin files arm9loaderhax will load on boot. Privately there is a lot of progress made, but not so much publicly right now.
OTP has to be gotten on 2.x though, and it will remain this way. So when the scene catches up everyone is still going to need to downgrade. Good news though is everyone including noobs like me have been downgrading fine. Seems like a very low brick risk if you just read correctly.