Under the old system homebrew projects that used read/write commands (FAT access) only worked on the flashcarts they were specifically coded for. This is a big hassle for developers and flash cart owners a like. That would mean to get your game working on four different flashcarts you’d need to code it with all four different read/write methods. Every flash cart uses different read/write commands. This forms the read/write commands which are essentially what libfat is. And if you wanted to read the image so you can edit it again you’d need access to the read capabilities of the flash cart. To save this image on the flash cart the developer would have to know the specific piece of code that allows you to write things to the cart. Let’s say a homebrew developer makes a DS game where you can draw a picture and save the image to your flash cart. I’ll break it down to more understandable terms. It is an interface for libfat that homebrew developers attached to their projects. 4 How do I patch my homebrew games/apps?ĭLDI stands for ‘Dynamically Linked Device Interface’.3 What Homebrew games/apps do I need to patch?.1 What is DLDI? (how did it come about?).
0 Comments
Leave a Reply. |