The 3DNes emulator doesn't just automagically convert 2D games into 3D. It's got some algorithms behind it that attempt to partition a given scene into regions, then assign the region to a layer (front/back) and extrusion method (box, horizontal/vertical cylinder, character). Someone then needs to play through the game, and if they see anything that the algorithm has guessed wrong, they can pull up an editor window, click on the region in the emulator, and edit layer/extrusion/etc on the fly. Once that's all done, the collected data can be uploaded so that other people playing the same game can play it with everything looking correct.
I'm not entirely clear on whether the partitioning/assignment/settings memorization works by detecting the actual sprites or graphics tiles that the emulated NES is drawing to the screen, or whether it's just calculating some sort of signature for that clump of pixels and looking it up in a table. My guess is the latter.
7 comments
[ 3.7 ms ] story [ 27.2 ms ] threadIf you'll notice, there's a windows version for the same price. The free release appears to be a 1.2.x release, while you pay for the 1.3.x releases.
The 3DNes emulator doesn't just automagically convert 2D games into 3D. It's got some algorithms behind it that attempt to partition a given scene into regions, then assign the region to a layer (front/back) and extrusion method (box, horizontal/vertical cylinder, character). Someone then needs to play through the game, and if they see anything that the algorithm has guessed wrong, they can pull up an editor window, click on the region in the emulator, and edit layer/extrusion/etc on the fly. Once that's all done, the collected data can be uploaded so that other people playing the same game can play it with everything looking correct.
I'm not entirely clear on whether the partitioning/assignment/settings memorization works by detecting the actual sprites or graphics tiles that the emulated NES is drawing to the screen, or whether it's just calculating some sort of signature for that clump of pixels and looking it up in a table. My guess is the latter.
It's a very nifty piece of tech :)