The game runs full speed for the most part, but there are slowdowns in certain areas. Note that if you do this, you won't be able to use saves. For some reason there are issues launching the game from TWiLightMenu with libfat enabled if you have no other way of launching homebrew, it can be disabled in the makefile by removing -DLIBFAT.
The game uses libfat to save to a file just like the PC port. Once you've compiled the game, you can load it through unlaunch, memory pit, or whatever DSi homebrew method you prefer.
It's already configured to build the DSi port, so just follow the build instructions included in the readme and you should be good to go. I can't provide compiled binaries, so don't ask for them or share them. Just like the original decompilation and the PC port, this requires you to provide your own legally dumped Super Mario 64 ROM file in order to compile it. The results were better than I expected the game runs full speed in most cases, and the graphics don't look too bad, either! I decided to scrap it and start from scratch, writing a new graphics interpreter designed to work directly with the DS hardware for maximum performance.
The initial version was based on the PC port of the game, but that port is designed with modern hardware in mind, and its graphics abstraction layer is slow. It originally started out as a joke idea that I didn't think would go very far, but once I actually got the game running on the DSi, I saw potential. Continued abuse of our services will cause your IP address to be blocked indefinitely.Yes, you read that right! This is a port of the original Super Mario 64 from 1996 to the Nintendo DSi, based on the open-source decompilation of the game. Please fill out the CAPTCHA below and then click the button to indicate that you agree to these terms. If you wish to be unblocked, you must agree that you will take immediate steps to rectify this issue. If you do not understand what is causing this behavior, please contact us here. If you promise to stop (by clicking the Agree button below), we'll unblock your connection for now, but we will immediately re-block it if we detect additional bad behavior. Overusing our search engine with a very large number of searches in a very short amount of time.Using a badly configured (or badly written) browser add-on for blocking content.Running a "scraper" or "downloader" program that either does not identify itself or uses fake headers to elude detection.Using a script or add-on that scans GameFAQs for box and screen images (such as an emulator front-end), while overloading our search engine.There is no official GameFAQs app, and we do not support nor have any contact with the makers of these unofficial apps. Continued use of these apps may cause your IP to be blocked indefinitely. This triggers our anti-spambot measures, which are designed to stop automated systems from flooding the site with traffic. Some unofficial phone apps appear to be using GameFAQs as a back-end, but they do not behave like a real web browser does.Using GameFAQs regularly with these browsers can cause temporary and even permanent IP blocks due to these additional requests. If you are using Maxthon or Brave as a browser, or have installed the Ghostery add-on, you should know that these programs send extra traffic to our servers for every page on the site that you browse.The most common causes of this issue are: Your IP address has been temporarily blocked due to a large number of HTTP requests.