As of today then entire 4J repository for source code from 360, PS3, Vita and a partial version of PS4 has been leaked. People have already gotten builds running on windows using debug compiler flags for debug builds and scrubbing out the DRM checks for release builds. But the interesting part is the memory usage, a fresh world with release build flags only eats up 230mb of ram. Let's say the worst case is 450mb, around the limit of the PS3 and 360's ram.
Now, that means that what we have on our hands is a portable C++ officially sanctioned engine for Minecraft with a low memory footprint. See where I'm going?
If someone, nutty and good enough at math in this community would step up, with a deep knowledge of the PICA200's architecture, we could very well have a version of MC3DS many, many people have wanted since childhood. In fact, if a team was to be assembled to get this done I'd gladly put a bounty on it in cash. It's too interesting to pass up, it's like porting SM64 to the PS1.
Personally this is a childhood dream come true, you wouldn't wish being stuck with bedrock on your worst enemy, hence why I'm posting. MC3DS, the real version was done by a shovelware company in Canada and is based off of a bedrock fork, back when it was PE. The stability is shit, the memory optimizations are hanging on for dear life and if you build too much the game turns into Google slides. Oh and no 3D. I hope the homebrew community takes a good look at this cause it's feasible, ignoring Microsoft ninjas but considering this is over a decade old code for outdated versions being ported to an obsolete console I'd say it's fine. Some things of note are the menus, seem to be SFWs so that's some ram to chop off if they're redone without flash player, networking ain't been figured out yet, naturally since the leak is fresh, but later down the line you could probably slot it into pretendo. That's an afterthought though.
The main problem is gonna be graphics, Nintendo as we know is physically incapable of using anything that isn't in-house so you'd have to translate the entire rendering backend into PICA code, AND optimize it like you're Kaze Emanuar after five doses of crack because the New 3DS has the processing power of a citrus fruit.
Now, what do y'all think?
Now, that means that what we have on our hands is a portable C++ officially sanctioned engine for Minecraft with a low memory footprint. See where I'm going?
If someone, nutty and good enough at math in this community would step up, with a deep knowledge of the PICA200's architecture, we could very well have a version of MC3DS many, many people have wanted since childhood. In fact, if a team was to be assembled to get this done I'd gladly put a bounty on it in cash. It's too interesting to pass up, it's like porting SM64 to the PS1.
Personally this is a childhood dream come true, you wouldn't wish being stuck with bedrock on your worst enemy, hence why I'm posting. MC3DS, the real version was done by a shovelware company in Canada and is based off of a bedrock fork, back when it was PE. The stability is shit, the memory optimizations are hanging on for dear life and if you build too much the game turns into Google slides. Oh and no 3D. I hope the homebrew community takes a good look at this cause it's feasible, ignoring Microsoft ninjas but considering this is over a decade old code for outdated versions being ported to an obsolete console I'd say it's fine. Some things of note are the menus, seem to be SFWs so that's some ram to chop off if they're redone without flash player, networking ain't been figured out yet, naturally since the leak is fresh, but later down the line you could probably slot it into pretendo. That's an afterthought though.
The main problem is gonna be graphics, Nintendo as we know is physically incapable of using anything that isn't in-house so you'd have to translate the entire rendering backend into PICA code, AND optimize it like you're Kaze Emanuar after five doses of crack because the New 3DS has the processing power of a citrus fruit.
Now, what do y'all think?
