will it be able to output native resolution video for non-extended memory games with at least 14-16 FPS? Games of interest for me are RE:R and MH3U...
sadly I can't do estimates as I didn't finish hand-crafting all the required assembly yet, but if you have understood my previous post correcly then you should already know that HzModEx will ALWAYS output 200x120 images, no matter what, but there will be two modes to compensate for that; one averages the pixels for true downscale, and one will rotate the pixels, so you'd get a full frame every 4th frame, this way it'll give the illusion of 4x FPS even though in reality it can't put out this much due to CPU and wifi speed limitations
as for extended and non-extended, it shouldn't make a rat's ass difference, the only thing matters is how much RAM the game requires on startup (softlock on Nintendo 3DS logo screen or not)
if the output is dumbed down, about how many more FPS is it estimated to get compared to native?
sadly I can't calculate an estimate (as I stated in my previous answer), but the best possible FPS can be approximated using the
FPS = (268111856 * max possible CPU usage of network thread) / (const amount of CPU cycles + (200 * 120 * clock cycles needed per pixel)) formula once I finish hand-crafting the assembly code for all the screen modes. this means that in the worst case (15% max possible CPU time and *very* unoptimized code) it equates to
FPS = (268111856 * 0.15) / (50000 + (200 * 120 * 120)) ~= 13.72FPS if not counting the slow wifi card speed. again, don't count this as a response, count this as the worst possible scenario
though if you were really only asking about the difference between 400x240 and 200x120, it's almost 4th processing and/or wifi power required than with 400x240... I said almost, because the downscaling/memory copying requires CPU cycles, so in reality it might only be a 2x gain at worst... but it's *not* possible to reach 4x performance due to the mentioned CPU downscaling algorhythms
...as for new3DS, it's a simple 3x multiplier because the CPU is clocked at 3x, and that surprisingly also makes wifi 3x faster
meaning the nwm sysmodule itself is limiting the wifi speed due to how awfully written it is