the DBI author has threatened to put brick code into DBI. Has anyone actually been bricked by it? I can deal with the Russian text but restoring a NAND backup is a fucking pain in the ass.
No, it's a myth. Use it with peace.brick code into DBI

he is just a drama queen asking for attention and make that menace but never put it.the DBI author has threatened to put brick code into DBI. Has anyone actually been bricked by it? I can deal with the Russian text but restoring a NAND backup is a fucking pain in the ass.
)
I did it and no problem yet.Just do not try to edit the DBI .nro file and you are OK.
You will be bricked as soon as the dev is un-drafted and has free time.I did it and no problem yet.

He honestly should've taken a different approach instead of making a threat to brick consoles, and now Switch owners are afraid to run DBI because of it. And all because of demands for additional languages, mind you.i assume the dev just got fed up of the constant demands from entitled westerners which honestly is so valid… not knowing Russian - simply a skill issue.

nah, is just a drama queen asking for attention.You will be bricked as soon as the dev is un-drafted and has free time.
Definitely not the best approach but I can’t not respect the decision when it’s their work.He honestly should've taken a different approach instead of making a threat to brick consoles, and now Switch owners are afraid to run DBI because of it. And all because of demands for additional languages, mind you.
Not to be political, but Russia is known to not take too kindly to Western values. Either that, or simply out of grabbing attention and to stir up more controversy.
He honestly should've taken a different approach instead of making a threat to brick consoles, and now Switch owners are afraid to run DBI because of it. And all because of demands for additional languages, mind you.
Not to be political, but Russia is known to not take too kindly to Western values. Either that, or simply out of grabbing attention and to stir up more controversy.

Nothing. Absolutely nothing at all. I cannot fathom how the dev can get upset over something like a kind suggestion. From the DBI thread I've been reading, he felt as if he got treated badly by some English speakers. I don't know what the context is, or how it all started, but there's nothing politically motivated about this tool. He wanted the attention and he got it.Things escalated quickly, but I still don’t understand how people managed to forget all the work he did just to create drama based on… what, exactly?

NO, WAS NOT ANY MISINTERPRETATION NOR TRANSLATION ISSUE, THE THREAT WAS SIMPLE AND PLAIN, HE TOLD «IF SOMEBODY START TO EDITING THE NRO HE COULD PUT A BRICK CODE ON IT». THAT IS A THREAT NOT A MISUNDERSTANDING.I’m still 99% sure that the messages some interpreted as “threats” were simply misread. He was translating from Russian to English, and cultural differences likely played a role as well. In my homecountry (Morocco), we tend to take people’s statements very seriously, even in casual conversation, and especially when it comes to professional projects.
Things escalated quickly, but I still don’t understand how people managed to forget all the work he did just to create drama based on… what, exactly?
Someone should tell him that he's a shit coder because USB 3.0 doesn't work half the timeI seriously doubt he will complaint because he craves the attention and people telling he is a great coder.


Someone Already did, and then he blamed Atmosphère!Someone should tell him that he's a shit coder because USB 3.0 doesn't work half the time![]()
The following was changed since the last release:
- USB 3.0 support force-enable was fixed for 20.1.0+.

That is because the official release of 1.9.1 didn't included the patches for USB3.0 they where added on a commit of the next day, SciresM commented «I don't know why I overlooked this» but taking in account the rush for 1.9.1 release is understandable. the version with the patches was post on the Atmosphère's thread here on GBATemp the very next dayIt's interesting that SciresM fixed the USB 3.0 force-enable in the latest AMS 1.9.2 that was released 2 days ago:
https://github.com/Atmosphere-NX/Atmosphere/pull/2556